From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Ath9k stations not authenticating in -rc6 ?
Date: Thu, 05 May 2011 10:02:33 -0700 [thread overview]
Message-ID: <4DC2D829.6000706@candelatech.com> (raw)
Has anyone successfully associated a wpa station in -rc6
using ath9k?
I haven't done much debugging yet, but it appears something broke
between .38 and .39-rc6.
I'm seeing events like this in .39-rc6:
2011-05-05 08:55:15.080 wlan0 (phy #0): scan started
2011-05-05 08:55:15.135 wlan0 (phy #0): scan finished: 5200, ""
2011-05-05 08:55:15.139 wlan0 (phy #0): auth 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 status: 0: Successful
2011-05-05 08:55:15.140 wlan0: new station 30:46:9a:10:0b:9c
2011-05-05 08:55:15.205 wlan0 (phy #0): assoc 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 status: 0: Successful
2011-05-05 08:55:15.205 wlan0 (phy #0): connected to 30:46:9a:10:0b:9c
2011-05-05 08:55:19.236 wlan0: unknown event 20
2011-05-05 08:55:19.236 wlan0 (phy #0): deauth 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 reason 2: Previous authentication no longer valid
2011-05-05 08:55:19.236 wlan0 (phy #0): disconnected (by AP) reason: 2: Previous authentication no longer valid
2011-05-05 08:55:19.276 phy #0: regulatory domain change: set to world roaming by the wireless core upon initialization request
2011-05-05 08:55:19.363 regulatory domain change: set to US by a user request
2011-05-05 08:55:24.284 wlan0 (phy #0): scan started
2011-05-05 08:55:24.374 wlan0 (phy #0): scan finished: 5200, ""
2011-05-05 08:55:24.379 wlan0 (phy #0): auth 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 status: 0: Successful
2011-05-05 08:55:24.379 wlan0: new station 30:46:9a:10:0b:9c
2011-05-05 08:55:24.389 wlan0 (phy #0): assoc 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 status: 0: Successful
2011-05-05 08:55:24.444 wlan0 (phy #0): connected to 30:46:9a:10:0b:9c
2011-05-05 08:55:28.410 wlan0: unknown event 20
2011-05-05 08:55:28.426 wlan0 (phy #0): deauth 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 reason 2: Previous authentication no longer valid
2011-05-05 08:55:28.426 wlan0 (phy #0): disconnected (by AP) reason: 2: Previous authentication no longer valid
2011-05-05 08:55:28.506 phy #0: regulatory domain change: set to world roaming by the wireless core upon initialization request
2011-05-05 08:55:28.608 regulatory domain change: set to US by a user request
...
In .38-wl, it just works (all I did was reboot to a different kernel):
2011-05-05 08:58:27.385 wlan0 (phy #0): scan finished: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 5180 5200 5220 5240 5260 5280 5300 5320 5500 5520
5540 5560 5580 5660 5680 5700 5745 5765 5785 5805 5825, ""
2011-05-05 08:58:27.385 wlan0 (phy #0): auth 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 status: 0: Successful
2011-05-05 08:58:27.385 wlan0: new station 30:46:9a:10:0b:9c
2011-05-05 08:58:27.385 wlan0 (phy #0): assoc 30:46:9a:10:0b:9c -> 00:0c:42:61:cf:85 status: 0: Successful
2011-05-05 08:58:27.385 wlan0 (phy #0): connected to 30:46:9a:10:0b:9c
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2011-05-05 17:02 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=4DC2D829.6000706@candelatech.com \
--to=greearb@candelatech.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 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).