8.2.1 wireless testing results #2

[Daniel Drake]

Comparing staging-25 against 8.2-767, I have 2 more APs to play with:

1. D-Link DWL-7100AP
Open and WEP work fine. I also confirmed that connection is
automatically reestablished on reboot.

WPA(TKIP): 8.2.0 connects every time. 8.2.1 always fails to connect,
bringing up the password request dialog. Here are the NM logs, showing
that association completes but it fails before DHCP (very likely
during WPA handshake):

NetworkManager: <info>  Activation (eth0) New wireless user key for
network '821testwpa' received.
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) started...
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) complete.
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) starting...
NetworkManager: <info>  Activation (eth0/wireless): access point
'821testwpa' is encrypted, and a key exists.  No new key needed.
NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD
eth0#011#011wext#011/var/run/wpa_supplicant#011'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'AP_SCAN 1'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'ADD_NETWORK'
NetworkManager: <info>  SUP: response was '0'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid
38323174657374777061'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 proto WPA'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 psk <key>'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) complete.
avahi-daemon[1122]: Withdrawing address record for
fe80::217:c4ff:fe3c:c8a1 on eth0.
NetworkManager: <info>  msh0: Got association; scheduling association handler
NetworkManager: <info>  msh0: got association event from driver.
NetworkManager: <info>  Activation (eth0/wireless): disconnected
during association, asking for new key.


I had limited success connecting by disabling NM, writing a
wpa_supplicant config file, and connecting with wpa_supplicant spewing
debug messages onto the console.

WPA2: not supported by AP (wtf? not a cheap AP!!)


2. D-Link DWL-2100AP
Open and WEP work fine. I also confirmed that connection is
automatically reestablished on reboot.

WPA: works fine on 8.2.0
Generally works the first time you try and connect on 8.2.1, but not
after you disconnect and reconnect.
On reboot, it also fails, bringing up the password input dialog.

WPA2: works fine on 8.2.0
Also works well on 8.2.1. However, upon reboot, connection is not
automatically reestablished. NM logs indicate the same bug that Hal
Murray reported, which is a very strange one. It seems that
association and handshake completes, but it receives no response to
DHCP requests. Manually clicking on the AP icon soon after boot works
around this problem. NM logs:

NetworkManager: <info>  Will activate connection 'eth0/dlinkwpa2'.
NetworkManager: <info>  Device eth0 activation scheduled...
NetworkManager: <info>  Activation (eth0) started...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) started...
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) scheduled...
NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device
Prepare) complete.
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) starting...
NetworkManager: <info>  Activation (eth0/wireless): access point
'dlinkwpa2' is encrypted, and a key exists.  No new key needed.
NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD
eth0#011#011wext#011/var/run/wpa_supplicant#011'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'AP_SCAN 1'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'ADD_NETWORK'
NetworkManager: <info>  SUP: response was '0'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid
646c696e6b77706132'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 proto WPA2'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 psk <key>'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0'
NetworkManager: <info>  SUP: response was 'OK'
NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device
Configure) complete.
NetworkManager: <info>  msh0: Got association; scheduling association handler
NetworkManager: <info>  msh0: got association event from driver.
NetworkManager: <info>  Activation (eth0/wireless) Stage 2 of 5
(Device Configure) successful.  Connected to access point 'dlinkwpa2'.
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) scheduled.
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) started...
NetworkManager: <info>  nm_dhcp_manager_cancel_transaction_real(): enter, pid 0
NetworkManager: <info>  nm_dhcp_manager_cancel_transaction_real():
returning, zero pid 0
NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
NetworkManager: <info>  eth0: nm_dhcp_manager_begin_transaction():661
started timeout source 0x8925180
dhclient: Internet Systems Consortium DHCP Client 4.0.0
NetworkManager: <info>  dhclient started with pid 1316
NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure
Start) complete.
dhclient: Copyright 2004-2007 Internet Systems Consortium.
dhclient: All rights reserved.
dhclient: For info, please visit http://www.isc.org/sw/dhcp/
dhclient:
NetworkManager: <info>  DHCP: device eth0 state changed (null) -> preinit
dhclient: Listening on LPF/eth0/00:17:c4:3c:c8:a1
dhclient: Sending on   LPF/eth0/00:17:c4:3c:c8:a1
dhclient: Sending on   Socket/fallback
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
NetworkManager: <info>  Old device 'eth0' activating, won't change.
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
NetworkManager: <info>  eth0: link timed out.
NetworkManager: <info>  Old device 'eth0' activating, won't change.
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
NetworkManager: <info>  Device 'eth0' DHCP transaction took too long
(>45s), stopping it.



Conclusion: testing with these 2 APs both indiciate 8.2.1 regressions
since 8.2.0 when connecting to WPA or WPA2 networks.

Daniel