Package: wpasupplicant
Followup-For: Bug #294909
I just updated from wpasupplicant-0.3.2 to wpasupplicant-0.3.8 and it
failed to communicate with my WEP enabled access point.
# wpa_supplicant -d -Dmadwifi -i ath0
...
1: xx:xx:xx:xx:xx:xx ssid='xxxxxx' wpa_ie_len=0 rsn_ie_len=0
skip - no WPA/RSN IE
selected non-WPA AP xx:xx:xx:xx:xx:xx ssid='xxxxxx'
Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxxxxx' freq=2412 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=WEP key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
wpa_driver_madwifi_associate
wpa_driver_madwifi_set_wpa: enabled=0
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
At this point all encryption keys have been cleared and it fails to exchange
any data with the accesspoint.
# iwlist ath0 key
ath0 3 key sizes : 40, 104, 128bits
4 keys available :
[1]: off
[2]: off
[3]: off
[4]: off
Current Transmit Key: [0]
Security mode:restricted
Reverting 11_madwifi_open_aps.dpatch made everything work again.
# wpa_supplicant -d -Dmadwifi -iath0
....
1: xx:xx:xx:xx:xx:xx ssid='xxxxxx' wpa_ie_len=0 rsn_ie_len=0
skip - no WPA/RSN IE
selected non-WPA AP xx:xx:xx:xx:xx:xx ssid='xxxxxx'
Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxxxxx' freq=2412 MHz)
Cancelling scan request
Automatic auth_alg selection: 0x1
No keys have been configured - skip key clearing
wpa_driver_madwifi_set_key: alg=WEP key_idx=0 set_tx=1 seq_len=0 key_len=5
wpa_driver_madwifi_set_drop_unencrypted: enabled=1
wpa_driver_madwifi_associate
Setting authentication timeout: 5 sec 0 usec
EAPOL: External notification - portControl=ForceAuthorized
# iwlist ath0 key
ath0 3 key sizes : 40, 104, 128bits
4 keys available :
[1]: xxxx-xxxx-xx (40 bits)
[2]: off
[3]: off
[4]: off
Current Transmit Key: [1]
Security mode:restricted
I guess the test for KEY_MGMT_NONE is too generic since simple WEP encryption
falls under the same category. Also completely disabling wpa in the driver
(which is what the patch is doing) might not be the right thing, since it is
only (re)enabled in one other place in the code in wpa_supplicant_driver_init.
So my guess is that once it associates with an open AP, it won't ever allow
reassociating with a WPA enabled AP until the interface has been removed and
reinserted.
Jan
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-rc3
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
