Bug#386090: [pkg-wpa-devel] Bug#386090: wpasupplicant: no association to unencrypted network
On Sat, Sep 09, 2006 at 10:59:05AM +1000, Kel Modderman wrote: Take some info from 'wpa_cli -i eth1 status' or 'iwconfig eth1' during and after attempted association. I do not have auto eth1 in my /e/n/i. Thus, the default replies are: $ sudo wpa_cli -i eth1 status Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory $ sudo iwconfig eth1 eth1 unassociated ESSID:off/any Mode:Managed Channel=0 Access Point: Not-Associated Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:21 Missed beacon:0 When the train came in range of the station, my interface associated with the Hotspot without wpa_supplicant interfering: $ sudo iwconfig eth1 eth1 IEEE 802.11g ESSID:T-Mobile_T-Com Mode:Managed Frequency:2.412 GHz Access Point: 00:14:F2:7E:25:00 Bit Rate=54 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=58/100 Signal level=-67 dBm Noise level=-84 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:83 Missed beacon:9 $ I then started up the interface, and the interface immediately lost association: $ sudo ifup eth1 $ sudo iwconfig eth1 eth1 unassociated ESSID:off/any Mode:Managed Channel=0 Access Point: Not-Associated Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:84 Missed beacon:0 $ sudo wpa_cli -i eth1 status wpa_state=DISCONNECTED A minute later, wpa_supplicant tried to associate to my home network: $ sudo wpa_cli -i eth1 status wpa_state=ASSOCIATING $ sudo iwconfig eth1 eth1 unassociated ESSID:my-home-network Mode:Managed Channel=0 Access Point: Not-Associated Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:84 Missed beacon:0 This, of course, timed out. Next network on list is girlfriends-home-network: $ sudo wpa_cli -i eth1 status wpa_state=ASSOCIATING $ sudo iwconfig eth1 eth1 unassociated ESSID:girlfriends-home-network Mode:Managed Channel=0 Access Point: Not-Associated Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:D119-901E-8776-3016-3324-7E0E-49 Security mode:open Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:84 Missed beacon:0 This timed out, as well, and wpa_state changed to SCANNING: $ sudo wpa_cli -i eth1 status wpa_state=SCANNING $ sudo iwconfig eth1 eth1 unassociated ESSID:girlfriends-home-network Mode:Managed Channel=0 Access Point: Not-Associated Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:84 Missed beacon:0 I then decided to shut down the interface: $ sudo wpa_action eth1 stop Stopped wpa_cli (pid 4249). ifdown eth1 $ sudo wpa_cli -i eth1 status Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory $ sudo wpaiwconfig eth1 eth1 unassociated ESSID:girlfriends-home-network Mode:Managed Channel=0 Access Point: Not-Associated Bit Rate=0 kb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:84 Missed beacon:0 I would have expected wpa_supplicant to deconfigure the interface before shutting down. So I decided to deconfigure it manually, and it immediately associated to the Hotspot again:
Bug#386090: [pkg-wpa-devel] Bug#386090: wpasupplicant: no association to unencrypted network
On Sat, Sep 09, 2006 at 10:59:05AM +1000, Kel Modderman wrote: 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. Yes, I have auto eth1 iface eth1 inet manual wpa-driver wext wpa-roam /etc/wpa_supplicant.conf.local and one stanza per network: iface wlan-l21 inet dhcp wpa-driver wext wpa-ssid snip wpa-key-mgmt WPA-PSK wpa-psk snip I am not sure whether the network stanzas are still used. You show network blocks, does you conf also contain ap_scan or other non-network wpa_supplicant options? ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=0 dot11RSNAConfigSATimeout=10 eapol_version=1 ap_scan=2 fast_reauth=1 Besides that, I only have network stanzas in my wpa_supplicant.conf.local. 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. So I need to remove the id_str statement, and an iface default inet dhcp stanza in /e/n/i? Take some info from 'wpa_cli -i eth1 status' or 'iwconfig eth1' during and after attempted association. I will do so when I encounter the hotspot for the next time. It's a railroad station I am usually only passing through, so I'll either need to disembark from the train next time I am there or am limited to the like ten-minute stop of the train en route to my girlfriend's site. Greetings Marc -- - Marc Haber | I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things.Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386090: [pkg-wpa-devel] Bug#386090: wpasupplicant: no association to unencrypted network
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]
