[Gllug] wicd manager

Tue Nov 3 00:39:40 UTC 2009

> Ah, so the laptop
was plugged in to one of the four ports of the wifi
> router
physically. You should probably double check it had a
>
192.168.x.x IP address at this point.
> 

ping -n 192.168.0.1

PING 192.168.0.1
(192.168.0.1) 56(84) bytes of data.

64 bytes from
192.168.0.1: icmp_seq=1 ttl=127 time=0.408 ms

64 bytes from
192.168.0.1: icmp_seq=2 ttl=127 time=0.417 ms

64 bytes from
192.168.0.1: icmp_seq=3 ttl=127 time=0.412 ms

64 bytes from
192.168.0.1: icmp_seq=4 ttl=127 time=0.414 ms

64 bytes from
192.168.0.1: icmp_seq=5 ttl=127 time=0.438 ms

64 bytes from
192.168.0.1: icmp_seq=6 ttl=127 time=0.419 ms

64 bytes from
192.168.0.1: icmp_seq=7 ttl=127 time=0.414 ms

^C

--- 192.168.0.1 ping
statistics ---

7 packets transmitted,
7 received, 0% packet loss, time 5999ms

rtt min/avg/max/mdev =
0.408/0.417/0.438/0.020 ms

traceroute -n
80.87.128.36

traceroute to
80.87.128.36 (80.87.128.36), 30 hops max, 60 byte packets

 1  192.168.0.1  0.356
ms  0.340 ms  0.315 ms

 2  10.219.60.1  16.922
ms  16.954 ms  16.862 ms

 3  81.100.0.61  16.702
ms * *

 4  * * *

 5  * * *

 6  * * *

 7  * 212.43.163.89 
9.953 ms  9.553 ms

 8  213.152.245.49 
21.289 ms  21.312 ms  17.733 ms

 9  64.125.28.197 
32.123 ms  30.871 ms  30.874 ms

10  213.152.252.220 
32.162 ms  51.736 ms  52.209 ms

11  80.87.128.36 
52.065 ms  44.928 ms  35.390 ms

$ cat /etc/resolv.conf

nameserver 192.168.0.1

> The problem is
that your wifi router might have been having a whale of a
>
time remaining connected to the Internet, but you'd not have known
this
> whilst your laptop was unable to connect to it.
>

> How long did you give it? Your laptop would need to forget
its eth0
> config, and decide to go back to wireless, after
which it would need to
> re-dhcp eth1 and pick up and IP
(possibly the same one) and def.gw
> automatically to get going
again.
> 
> Did it work immediately on plugging the
network cable back in to the
> wifi router?
> 

The wicd manager
immediately trying to connect my wireless connection after I
unplugged the cable from the laptop.

> When you
unplugged the network cable, and let wicd do its stuff, could
>
you ping 192.168.0.1 over the wireless link ? This was the part
that
> you had working last time. If you can ping that but the
Internet
> connection isn't working (traceroute -n
80.87.128.36), then we have to
> assume some weird MAC address
complaining from your cable router. If
> you can no longer ping
192.168.0.1, then we've somehow regressed from
> what you had
working at the start of this thread.
> 

after I unplugged the
cable from the laptop 

ping -n 192.168.0.1

connect: Network is
unreachable

traceroute -n
80.87.128.36

traceroute to
80.87.128.36 (80.87.128.36), 30 hops max, 60 byte packets

connect: Network is
unreachable

Lucy 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.lug.org.uk/pipermail/gllug/attachments/20091102/8ca95171/attachment.html>
-------------- next part --------------
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug