On Mon, Nov 02, 2009 at 07:07:16PM -0500, CSights wrote: > Hello, > I'm having a problem with the ath5k module found in kernel 2.6.31.5 and > accessing ".local" addresses on the network. > What I've observed so far is that when I first boot the computer I can > successfully access (e.g. ping) other .local computers. If the computer with > the ath5k card sits for a few minutes I can no longer access .local > computers. (Trying to ping, ping returns "ping: unknown host") Also, other > computers on the network can no longer ping the ath5k computer (also "ping: > unknown host") > Pinging the .local computers by their IP address (e.g. 192.168.1.3) does > work. > Access to computers "on the internet" (e.g. www.case.edu) also works. Curious...if you ping a .local address before the failure, it is still accessible after other .local addresses become unavailable? I'm wondering if mdns results might be cached... The .local address relationship suggests multicast DNS, which suggests that ath5k might have a problem where it stops receiving multicast frames. Does this "ring any bells" for anyone? John -- John W. Linville Someday the world will need a hero, and you linville@xxxxxxxxxxxxx might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
