Some new observations:
If I restart avahi the .local computers are once again accessable
(pingable).
If I ping "nimby.local" (the computer with ath5k wireless card) it will
work
for about 120 seconds (aka 2 minutes). Then "nimby.local" is no longer
resolvable to a IP address. Is 2 minutes or 120 seconds important somewhere
in the ath5k code?
(The amount of time is the same if running ping on nimby.local rather
pinging
nimby.local.)
Output of ping:
64 bytes from nimby.local (192.168.1.6): icmp_seq=113 ttl=64 time=2.78 ms
64 bytes from nimby.local (192.168.1.6): icmp_seq=114 ttl=64 time=3.52 ms
64 bytes from nimby.local (192.168.1.6): icmp_seq=115 ttl=64 time=3.65 ms
64 bytes from nimby.local (192.168.1.6): icmp_seq=116 ttl=64 time=1.79 ms
64 bytes from 192.168.1.6: icmp_seq=117 ttl=64 time=2.17 ms
64 bytes from 192.168.1.6: icmp_seq=118 ttl=64 time=1.56 ms
^C64 bytes from 192.168.1.6: icmp_seq=119 ttl=64 time=1.91 ms
--- nimby.local ping statistics ---
119 packets transmitted, 118 received, 0% packet loss, time 134157ms
rtt min/avg/max/mdev = 1.266/36.055/2297.948/242.227 ms, pipe 3
$ ping nimby.local
ping: unknown host nimby.local
Thanks again!
C.
_______________________________________________
ath5k-devel mailing list
ath5k-devel@lists.ath5k.org
https://lists.ath5k.org/mailman/listinfo/ath5k-devel
