From: Pavel Roskin <proski@gnu.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k in wireless-testing won't work in AP mode
Date: Fri, 29 Jan 2010 18:05:15 -0500 [thread overview]
Message-ID: <1264806315.23248.22.camel@mj> (raw)
Hello
ath9k in wireless-testing won't work in AP mode. Stations fail to
associate:
# hostapd /etc/hostapd/wlan13.conf
Configuration file: /etc/hostapd/wlan13.conf
Using interface wlan13 with hwaddr 00:15:6d:84:1f:37 and ssid 'mike2'
wlan13: STA 00:17:c4:3b:fc:88 IEEE 802.11: did not acknowledge
authentication response
AP-STA-DISCONNECTED 00:17:c4:3b:fc:88
Could not set station 00:17:c4:3b:fc:88 flags for kernel driver
(errno=11).
wlan13: STA 00:17:c4:3b:fc:88 IEEE 802.11: disassociated
wlan13: STA 00:17:c4:3b:fc:88 IEEE 802.11: deauthenticated due to
inactivity
Failed to remove interface (ifidx=0).
Everything is fine with rt73usb on the same system with the same client:
# hostapd /etc/hostapd/wlan5.conf
Configuration file: /etc/hostapd/wlan5.conf
Using interface wlan5 with hwaddr 00:11:6b:39:40:19 and ssid 'mike2'
wlan5: STA 00:17:c4:3b:fc:88 IEEE 802.11: authenticated
wlan5: STA 00:17:c4:3b:fc:88 IEEE 802.11: associated (aid 1)
AP-STA-CONNECTED 00:17:c4:3b:fc:88
wlan5: STA 00:17:c4:3b:fc:88 RADIUS: starting accounting session
4B636488-00000000
wlan5: STA 00:17:c4:3b:fc:88 WPA: pairwise key handshake completed (RSN)
The only difference between wlan13.conf and wlan5.conf is the interface
name. The client runs MadWifi. With ath9k on the client side things
look even weirder on the AP side:
# hostapd /etc/hostapd/wlan13.conf
Configuration file: /etc/hostapd/wlan13.conf
Using interface wlan13 with hwaddr 00:15:6d:84:1f:37 and ssid 'mike2'
wlan13: STA 00:17:c4:3b:fc:88 IEEE 802.11: did not acknowledge
authentication response
unknown mgmt cb frame subtype 10
Things are still OK with rt73usb on the AP side if the client uses
ath9k.
hostapd is current from the hostap git (essentially version 0.7.1 with a
few more changes). The AP is an x86_64 PC with the current kernel from
wireless-testing.
I haven't used ath9k in AP mode for a long time if ever, so I don't know
when it broke.
I guess I'll need to look in Wireshark if the authentication response is
indeed acknowledged by the station, but I won't have time for that soon.
--
Regards,
Pavel Roskin
next reply other threads:[~2010-01-29 23:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 23:05 Pavel Roskin [this message]
2010-01-29 23:34 ` [ath9k-devel] ath9k in wireless-testing won't work in AP mode Felix Fietkau
2010-01-30 19:39 ` Pavel Roskin
2010-01-30 20:10 ` Felix Fietkau
2010-01-30 20:37 ` Pavel Roskin
2010-01-30 20:46 ` Felix Fietkau
2010-01-30 21:11 ` Pavel Roskin
2010-02-03 0:08 ` Luis R. Rodriguez
2010-02-03 0:18 ` Felix Fietkau
2010-02-03 0:27 ` Luis R. Rodriguez
2010-02-03 0:35 ` Felix Fietkau
2010-02-03 0:45 ` Luis R. Rodriguez
2010-02-03 3:29 ` Pavel Roskin
2010-02-03 17:16 ` Luis R. Rodriguez
2010-02-03 4:22 ` Sujith
2010-02-10 10:51 ` Jouni Malinen
2010-02-10 17:33 ` Peter Stuge
2010-02-11 9:12 ` Peter Stuge
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=1264806315.23248.22.camel@mj \
--to=proski@gnu.org \
--cc=ath9k-devel@lists.ath9k.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.