Re: ipw2200: very slow association with Kernel 2.6.22

François Valenduc a écrit :
> Zhu Yi a écrit :
>   
>> On Sat, 2007-09-01 at 11:16 +0200, François Valenduc wrote:
>>   
>>     
>>> If I use kernel 2.6.21 with the same version of 
>>> wpasupplicant, association occurs instantly. So, the problem seems to
>>> be 
>>> with the ipw2200 or ieee80211 drivers rather than with wpasupplicant.
>>>
>>> Does anybody encounter the same problem ? Is there any solution to
>>> it ? 
>>>     
>>>       
>> Which version of 2200 driver are you using? Did you also use the
>> external ieee80211 module? Note, if you are using 2.6.22 kernel, you can
>> use the in-tree driver and ieee80211 directly.
>>
>> Thanks,
>> -yi
>>
>>   
>>     
> I use in both cases the in-tree driver for ipw2200 and ieee80211. But 
> finally, the problem might be caused by wpa_supplicant since now, it 
> also fails frequently with the 2.6.21 kernel. It seems that when 
> wpasupplicant starts, the ieee80211_crypt_tkip and michael_mic modules 
> are not loaded immediately. But if I run wpa_cli -i eth1 reassociate, 
> these modules are load immediately and association occurs instantly. So, 
> I have add these 2 modules to the /etc/modules file but it doesn't solve 
> the problem.
>
> Thanks for your help,
> François Valenduc
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> ipw2100-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipw2100-devel
>
>   
Finally, the problem was caused by wpa_supplicant and not with the
ipw2200 drivers. I had not noticed until now that there was another WIFI
network in my neighborhood. So, I have changed the configuration of
wpa_supplicant and I set the ap_scan parameter to 0 instead of 2. I
thought the latter was needed to operate with hidden SSID but this
doesn't seem to be the case. I also added a network in the
wpa_supplicant.conf file corresponding to the other network and I
disabled it.

François Valenduc

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/