Hi, On Fri, Apr 15, 2011 at 6:34 PM, Jouni Malinen <j@xxxxx> wrote: > On Fri, Apr 15, 2011 at 12:54:28PM +0200, Juan Carlos Garza wrote: >> I am having trouble to authenticate a Samsung Galaxy Tab with an AP on >> a rt3070 usb device. The specifics follow... > >> However, I am trying to authenticate with a Samsung Galaxy Tab with >> Android 2.2 on it, and I get the following log: > >> mgmt::auth >> authentication: STA=bc:47:60:93:74:bd auth_alg=0 auth_transaction=1 >> wlan0: STA bc:47:60:93:74:bd IEEE 802.11: authentication OK (open system) >> authentication reply: STA=bc:47:60:93:74:bd auth_alg=0 >> mgmt::assoc_req >> association request: STA=bc:47:60:93:74:bd capab_info=0x431 listen_interval=10 >> unknown vendor specific information element ignored (vendor OUI 00:10:18 len=9) >> new AID 2 >> HT: STA bc:47:60:93:74:bd HT Capabilities Info: 0x182c >> wlan0: STA bc:47:60:93:74:bd IEEE 802.11: association OK (aid 2) >> mgmt::auth cb >> wlan0: STA bc:47:60:93:74:bd IEEE 802.11: authenticated > > Huh... That rt3070 device or driver sure takes long to deliver the TX > status information. > >> Data/PS-poll frame from not associated STA bc:47:60:93:74:bd >> mgmt::assoc_resp cb > > And since the station you are using here seems to send some Data frames > quickly after the association, it happens to hit a race condition > between the association response TX status callback and first Data frame > being received. This in turn makes hostapd disassociate the station > since from its view point, the station tried to send a Data frame while > it had not yet completed association. > > You can now find a workaround for this in the current development branch > for hostapd: > http://w1.fi/gitweb/gitweb.cgi?p=hostap.git;a=commitdiff;h=b8281964afb1df98135418fc22a9fa240968d100 Thanks a lot, I am currently testing the patched 0.7.3 and now authentications are successful. > > -- > Jouni Malinen PGP id EFC895FA > Regards, Juan Carlos Garza Fernández -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
