From: Howard Chu <hyc@symas.com>
To: linux-wireless@vger.kernel.org
Subject: ath9k roaming for no obvious reason
Date: Mon, 20 Apr 2009 07:47:44 -0700 [thread overview]
Message-ID: <49EC8B10.7020006@symas.com> (raw)
I've been seeing this for a couple of months now, and updating to the latest
wireless-testing git hasn't improved things:
>>>
Apr 20 07:31:12 violino NetworkManager: <debug> [1240237872.002673]
periodic_update(): Roamed from BSSID 00:12:17:26:56:10 (HighlandSun) to (none)
((none))
Apr 20 07:31:18 violino NetworkManager: <debug> [1240237878.004208]
periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:26:56:10
(HighlandSun)
Apr 20 07:32:12 violino NetworkManager: <debug> [1240237932.003138]
periodic_update(): Roamed from BSSID 00:12:17:26:56:10 (HighlandSun) to (none)
((none))
Apr 20 07:32:18 violino NetworkManager: <debug> [1240237938.004280]
periodic_update(): Roamed from BSSID (none) ((none)) to 00:12:17:26:56:10
(HighlandSun)
<<<
This is on an HP dv5z laptop, lspci shows
08:00.0 Network controller: Atheros Communications Inc. AR928X Wireless
Network Adapter (PCI-Express) (rev 01)
It's about 10 feet from a Linksys WRT54G and there's nothing blocking the line
of sight. I'm running a 2.6.29.1 kernel at the moment; used the
compat-wireless git to build the wireless stack.
At random intervals (15-20 minutes or so) it loses the association completely
and NetworkManager asks me to re-authenticate. This behavior seems to have
gotten worse in the current snapshot. Has anyone else seen this, any ideas?
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
reply other threads:[~2009-04-20 14:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49EC8B10.7020006@symas.com \
--to=hyc@symas.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.