linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: CSights <csights@fastmail.fm>
To: linux-wireless@vger.kernel.org
Subject: ath5k and ".local" dropout
Date: Mon, 2 Nov 2009 19:07:16 -0500	[thread overview]
Message-ID: <200911021907.16271.csights@fastmail.fm> (raw)

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.

	At first I thought this was a problem with Avahi.  Later I tried a different 
wireless card (one that uses the RT2500pci module) and there was no problem 
with the .local fading away after a few minutes.

02:04.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 
Multiprotocol MAC/baseband processor (rev 01)                                            
        Subsystem: Compaq Computer Corporation Device 00e5                      
        Flags: medium devsel, IRQ 11                                            
        Memory at 90080000 (32-bit, non-prefetchable) [size=64K]                
        Capabilities: [44] Power Management version 2                           
        Kernel modules: ath5k

Anything else to try?  (I'm not subscribed to mailing list, so CC me in 
responses please!)

Thanks for your work!
	C.

             reply	other threads:[~2009-11-03  0:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03  0:07 CSights [this message]
2009-11-03 18:00 ` ath5k and ".local" dropout John W. Linville
2009-11-03 18:54   ` Bob Copeland
2009-11-03 19:01     ` John W. Linville
2009-11-03 19:25       ` Bob Copeland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200911021907.16271.csights@fastmail.fm \
    --to=csights@fastmail.fm \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).