trouble associating in busybox based environment
Mon May 16 12:07:36 PDT 2011
On Fri, May 13, 2011 at 12:49:38PM +0100, Davide wrote:
> I'm having trouble getting hostapd to work correctly in a busybox based system.
> I'm using 2.6.38rc8-kirkwood , BusyBox v1.18.4 and hostapd-0.7.3
hostapd does not use any BusyBox functionality, so I don't think this
has anything to do with BusyBox.
Which driver are you using in this device for the WLAN hardware? The
debug log seems to indicate that the driver could have quite a long
latency in reporting TX status for frames and this can result in a race
condition that prevents the association. A workaround for such driver
behavior was adding in the current development branch, so I would
recommend testing with a snapshot from the 0.8.x branch.
> association request: STA=00:19:d2:bd:96:21 capab_info=0x431 listen_interval=5
> Validating WMM IE: OUI 00:50:f2 OUI type 2 OUI sub-type 0 version 1 QoS info 0x0
> new AID 1
> wlan0: STA 00:19:d2:bd:96:21 IEEE 802.11: association OK (aid 1)
> mgmt::auth cb
> wlan0: STA 00:19:d2:bd:96:21 IEEE 802.11: authenticated
> Data/PS-poll frame from not associated STA 00:19:d2:bd:96:21
> mgmt::assoc_resp cb
> wlan0: STA 00:19:d2:bd:96:21 IEEE 802.11: associated (aid 1)
This shows the race condition. That "frame from not associated STA"
should not be there, i.e., the assoc_resp cb should show before any data
frames are received from the station.
Jouni Malinen PGP id EFC895FA
More information about the Hostap