On Tuesday 05 September 2006 19:07, Marc Haber wrote: > Package: wpasupplicant > Version: 0.5.4-5 > Severity: normal > > Hi, > > with the following wpa_supplicant.conf.local, wpasupplicant does not > associate to unencrypted networks, such as public Hot-Spots: > > network={ > id_str="wlan-open" > ssid="" > key_mgmt=NONE > } > > network={ > id_str="wlan-l21" > ssid="my-home-network" > key_mgmt=WPA-PSK > psk=<snip> > } > > network={ > id_str="wlan-sandra" > ssid="girlfriends-home-network" > key_mgmt=NONE > wep_key0=<snip> > scan_ssid=1 > } > > Looks like the supplicant does not properly handle the empty ssid > string as "ANY".
That is your conf file, but how is wpa_supplicant initiated? In other bug reports you mention wpa_action, do you use wpa-roam? You use 'id_str' so I assume you do, but please give more information about your setup. You show network blocks, does you conf also contain ap_scan or other non-network wpa_supplicant options? I can think of two things that may be the problem here, but will require some more info about your setup, and will try to set up a test case myself. Quite possibly, having 'id_str' in the "connect-any" block is causing issues. Try removing id_str="wlan-open", and allow wpa-roam to fallback to the "default" logical mapping. Take some info from 'wpa_cli -i eth1 status' or 'iwconfig eth1' during and after attempted association. Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]