Bug#368770: [pkg-wpa-devel] Bug#368770: wpasupplicant: takes a long time to associate to WEP protected hidden-SSID network

[Kel Modderman]

Kel Modderman wrote:
> Marc Haber wrote:
>> On Fri, Jun 30, 2006 at 08:37:40PM +1000, Kel Modderman wrote:
>>  
>>> Marc Haber wrote:
>>>    
>>>> On Mon, May 29, 2006 at 07:05:22AM +1000, Kel Modderman wrote:
>>>>  
>>>>      
>>>>> Have you attempted using different ap_scan and scan_ssid values as 
>>>>> described in 
>>>>> /usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf.gz ?
>>>>>            
>>>> As I am not using wpa_supplicant.conf but /etc/network/interfaces,
>>>> ap_scan=2 won't work here.
>>>>  
>>>>       
>>> 'wpa-ap-scan 2' does not work? It _seems_ to work for me, although I 
>>> cannot reproduce the exact problem with the hardware I have 
>>> available to me.
>>>     
>>
>> Which configuration file does wpa_supplicant parse for the network
>> definitions if wpa-ap-scan 2 is written to /etc/network/interfaces?
>> There is none that contains the required network definitions. Or does
>> the script generate a configuration file on the fly?
>>
>>   
>
> Basically, wpa_supplicant is launched with an absolutely blank 
> configuration (ctrl_interface). The /etc/wpa_supplicant/ifupdown.sh 
> script's job is to read the options given in /etc/network/interfaces 
> (described briefly in  /usr/share/doc/wpasupplicant/README.modes.gz) 
> for the given interface and create a single network configuration, 
> just as if it was defined in a wpa_supplicant.conf file.
>
>

That is of course the case only when wpa-{conf,roam} is *not* used, as 
these modes require a (wpa_supplicant.conf) configuration file.

Kel.