Re: 8.2.1 wireless testing results #2

[quozl]

Comparing staging-26 against 8.2-767, using a NetComm NB600W
(purchased 2007-12-13) configured for either open or WPA TKIP. 

Open works fine.  Connection is automatically reestablished on reboot.

WPA(TKIP): 8.2.0 reconnects on boot, staging-26 always fails to
reconnect on boot, bringing up the password request dialog, repeatedly.
On the fourth or fifth dialog retry, the icon for the access point
disappears from view and reappears a minute or two later.  When that
happens, clicking on it successfully connects.

Workaround: after a reboot, cancelling the password request dialog, then
using the Control Panel, Network, Discard network history, allows
immediate connection.

Also, resuming from suspend on 8.2.0 requires connecting again, but
there is no password prompt.  Resuming on staging-26 produces the
password prompt, and generates the same symptom as rebooting ...
repeated prompts solved by Discard.

Conclusion: the regressions reported by Daniel Drake are reproduced.

-- 
James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

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: