wpa_supplicant failed to associate

Dan Williams dcbw
Fri Sep 18 10:23:55 PDT 2009


On Fri, 2009-09-18 at 21:28 +0530, Raghavendra wrote:
> Hi All,
>  
>    
>   I am getting following error while connecting to AP.
>  
> --------------------------------------------------------------------------------------
> Trying to associate with SSID 'testap'      // ap name changed
> 
> Association request to the driver failed
> 
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> 
> Associated with 00:1d:7e:0e:3f:54
> 
> WPA: IE in 3/4 msg does not match with IE in Beacon/ProbeResp
> (src=00:1d:7e:0e:3f:54)
> 
> WPA: WPA IE in Beacon/ProbeResp - hexdump(len=24): dd 16 00 50 f2 01
> 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02
> 
> WPA: WPA IE in 3/4 msg - hexdump(len=24): dd 16 00 50 f2 01 01 00 00
> 50 f2 04 01 00 00 50 f2 04 01 00 00 50 f2 02
> 
> CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> 
> Authentication with 00:00:00:00:00:00 timed out.
> 
> ---------------------------------------------------------------------------------------------------------------------------------------
> 
>  
> 
> scenario:
> 
> 1. connect and disconnect with WPA-TKIP - success
> 
> 2. then try to connect with WPA-CCMP - failed
> 
> or 
> 
> 1. connect and disconnect with WPA-CCMP - success
> 
> 2. then try to connect with WPA-TKIP - failed

It could be many things...  a few questions first:

1) What wifi driver/version, and what kernel version?

2) what version of wpa_supplicant?  Do you have any custom patches?

3) What wpa_supplicant driver are you using, wext, a custom one, ...?

One theory is that the kernel driver itself isn't properly resetting the
state when the new configuration for SIOCSIWENCODEEXT comes in.  The
message "Association request to the driver failed" *could* indicate a
driver bug, but it's also reported when the driver just doesn't support
some of the less-necessary commands.  Giving the details above will help
diagnose that.

Dan




More information about the Hostap mailing list