wpa_supplicant failed to associate

[Raghavendra]

Hi, 
   Please find below answers for your queries. 

1) What wifi driver/version, and what kernel version? 
    Driver: TI driver, Kernel: 2.6.24-16-generic

2) what version of wpa_supplicant?  Do you have any custom patches? 
  I am using wpa_supplicant-0.5.11, I have following modification in supplicant.

  In ctrl_iface.c ----> wpa_supplicant_ctrl_iface_scan_results() ------>

  if(wpa_s->scan_results != NULL)
 {
        os_free(wpa_s->scan_results);
        wpa_s->scan_results = NULL;
        wpa_s->num_scan_results = 0;
  }

  Since I wanted wpa_supplicant to always get latest scan result from driver. I added above check. Also I am not using wpa_supplicant for 'scan'. I am using it only to get 'scan_result'. For scanning I am using WEXT ioctl.

3) What wpa_supplicant driver are you using, wext, a custom one, ...? 
  I am using -Dwext.

Following is my wpa_supplicant config file for WPA-TKIP
-----------------------------------------------------------------------------------------------------
ctrl_interface=/var/run/wpa_supplicant
ap_scan=2
network={
ssid="testap"  //ap name changed
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP  // using pairwise=TKIP CCMP for WPA-CCMP
group=TKIP     // using group=TKIP CCMP for WPA-CCMP
psk="testtest"
}
----------------------------------------------------------------------------------------------------------

Please let me know what is the issue here.


-Raghu


----- Original Message ----- 
From: "Dan Williams" <dcbw at redhat.com>
To: "Raghavendra" <s.raghu at samsung.com>
Cc: <hostap at lists.shmoo.com>
Sent: Friday, September 18, 2009 10:53 PM
Subject: Re: wpa_supplicant failed to associate


> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20090920/d2a495a9/attachment.htm