wpa_supplicant and hidden ssid

Katharina Brandl kathi.brandl at gmx.de
Sun Nov 2 11:14:03 EST 2008

Hello again,

For my laptop the configuration I posted works fine - but the same 
doesn't work with intel pro 3945. Is there another possibility to get 
the card and wpa_supplicant work with hidden ssid?

regards, Kathi

Helmut Schaa wrote:
> Hi,
> Am Samstag, 1. November 2008 schrieb Katharina Brandl:
>> thanks a lot for your help. ap_scan=1 doesn't work, but ap_scan=2 and 
>> pairwise/group ciphers in my config file it works fine.
> Ahhh, missed one thing. If you use ap_scan=1 you have to add scan_ssid=1
> to your network block!
>> So for others having the same problems, my wpa_supplicant.conf:
>> ctrl_interface=/var/run/wpa_supplicant
>> ctrl_interface_group=wheel
>> ap_scan=2
>> network={
>> ssid="mySSID"
>> key_mgmt=WPA-PSK
>> psk="passphrase"
>> priority=5
>> proto=WPA
>> pairwise=TKIP
>> pairwise=TKIP
>> }
>> What exactely is the meaning of proto and priority? Becauce these two 
>> line are the only ones I added and now I works...
> priority is only used if you have multiple network blocks. It just allows
> wpa_supplicant to determine which network to use if multiple configured ones
> are found.
> proto=WPA tells the supplicant to either use WPA or WPA2 (RSN) and in case
> you're using ap_scan=2 you have to provide the driver with that information.
> Helmut
>> Regards,
>> Kathi
>> Helmut Schaa wrote:
>>> Am Samstag, 1. November 2008 schrieb Katharina Brandl:
>>>> is it possible to connect to a network with hidden ssid via 
>>>> wpa_supplicant?
>>> Yes, this is possible ;)
>>>> I have the ipw2200 driver and the network works with  
>>>> WPA-PSK and pairwise/group cipher TKIP.
>>> With a recent ipw2200 you should be able to use either ap_scan=2 or ap_scan=1
>>> in your configuration file. The difference between both approaches is: with
>>> ap_scan=1 you do not need to configure the group/pairwise cipher at all as
>>> wpa_supplicant will see which ciphers are supported in the scan results and
>>> choose the AP it wishes to associate with. With ap_scan=2 the decision is left
>>> to the driver and thus the driver needs to know the used ciphers -> You need
>>> to configure the ciphers in your configuration file. Therefore I'd suggest to
>>> use ap_scan=1.
>>> => Your configuration file should contain at least the following:
>>> ap_scan=1
>>> network={
>>>         ssid="your_networks_name"
>>>         psk="your_password"
>>>         key_mgmt=WPA-PSK
>>>         priority=5
>>>         proto=WPA
>>> }
>>> Regards,
>>> Helmut

More information about the HostAP mailing list