[ILUG] 'arp who has 192.168.1.1 tell 192.168.1.10'

[Paul Jakma]

On Sat, 17 Sep 2005, Rory McCann wrote:

> Actually I mistyped. The desktop's tcpdump output was saying:

> "arp who has 192.168.1.1 tell 192.168.1.10"

> 192.168.1.10 is the IP of the desktop. 192.168.1.100 is the IP of the
> apple laptop.

Ok, then if 192.168.1.10 is the desktop, and the above is what the 
desktop sees, and you see that over and over again it means there's a 
communication failure between 1.1 and 1.10.

Try running tcpdump on 1.1 at the same time. Does it see these ARP 
requests? I'm guessing not.

> Somehow it has started working again. I don't know why.

> Here is the output of those commands:
> ip-address
> 4: ra0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>    link/ether 00:08:a1:85:8a:7e brd ff:ff:ff:ff:ff:ff
>    inet 192.168.1.10/24 brd 192.168.1.255 scope global ra0
>    inet6 fe80::208:a1ff:fe85:8a7e/64 scope link
> ip-neigh
> 192.168.1.1 dev ra0 lladdr 00:12:17:de:50:a8 nud reachable
> ip-route
> 192.168.1.0/24 dev ra0  proto kernel  scope link  src 192.168.1.10
> 169.254.0.0/16 dev ra0  scope link
> default via 192.168.1.1 dev ra0

My bets are on the 'ra0' driver or hardware. :) Never underestimate 
how absolutely crap 802.11 hardware/firmware and drivers can be..

When the problem occurs, does iwspy/iwconfig/iwlist whatever it is 
tell you that it still sees the AP, still happy with the link, etc. 
(I can't remember what you do with the linux wireless commands 
unfortunately - maybe someone else does).

regards,
-- 
Paul Jakma	paul at clubi.ie	paul at jakma.org	Key ID: 64A2FF6A
Fortune:
Time is but the stream I go a-fishing in.
 		-- Henry David Thoreau