[Desktop-packages] [Bug 1099976] Re: NetworkManager falsely reports WPA network "out of range"
As of today, I see this problem with an old Dell Inspiron 1525. I am running linux mint 15 with network-manager-gnome Version: 0.9.8.0-1ubuntu2 I did not have this problem with linux mint 10 through linux mint 13. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1099976 Title: NetworkManager falsely reports WPA network "out of range" Status in “network-manager” package in Ubuntu: Confirmed Bug description: On boot with amd64 Broadcom BCM43225, Raring NetworkManager correctly detects the network name, then NM falsely reports "out of range". What NM is trying to do is to connect without using the WPA encryption key which it already has. This is similar to bug 1097002 except in 1097002 NM doesn't even see the hidden network name even though it already has the encryption key for that network. In syslog below, says "has security but secrets are required". That's right, has security, but NM already has the secret encryption key; NM is supposed to use the key instead of disconnecting. Obviously NM doesn't even look to see it already has the key which it does. The branch in the NM script that sees "secrets are required" should go right ahead, see that it already has the "secrets", and use them. NetworkManager either doesn't have this path or is refusing to use it. I go on to connect manually with settings > network using the encryption key network manager already had and should have used. In any case, when NetworkManager finally does ask the kernel to connect, the kernel connects just fine. Not a kernel problem. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Auto-activating connection 'LAUREL'. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) starting connection 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): access point 'LAUREL' has security, but secrets are required. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'ssid' value 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'scan_ssid' value '1' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'key_mgmt' value 'WPA-PSK' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'psk' value '' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: set interface ap_scan to 1 Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): supplicant interface state: inactive -> scanning Jan 15 14:14:28 Aspire-5253 kernel: [ 252.465674] wlan0: authenticate with 00:0f:b3:b0:d6:3c Jan 15 14:14:28 Aspire-5253 wpa_supplicant[970]: wlan0: SME: Trying to authenticate with 00:0f:b3:b0:d6:3c (SSID='LAUREL' fre
[Desktop-packages] [Bug 1099976] Re: NetworkManager falsely reports WPA network "out of range"
Raring updated as of 31 January still gets false "out of range" on hidden WPA protected network on both Acer Aspire One netbook with integrated wireless and on Acer Aspire 5253 notebook with Broadcom wireless. Precise no problem. Is there any way to put Precise level Network Manager on Raring for testing purposes? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1099976 Title: NetworkManager falsely reports WPA network "out of range" Status in “network-manager” package in Ubuntu: Confirmed Bug description: On boot with amd64 Broadcom BCM43225, Raring NetworkManager correctly detects the network name, then NM falsely reports "out of range". What NM is trying to do is to connect without using the WPA encryption key which it already has. This is similar to bug 1097002 except in 1097002 NM doesn't even see the hidden network name even though it already has the encryption key for that network. In syslog below, says "has security but secrets are required". That's right, has security, but NM already has the secret encryption key; NM is supposed to use the key instead of disconnecting. Obviously NM doesn't even look to see it already has the key which it does. The branch in the NM script that sees "secrets are required" should go right ahead, see that it already has the "secrets", and use them. NetworkManager either doesn't have this path or is refusing to use it. I go on to connect manually with settings > network using the encryption key network manager already had and should have used. In any case, when NetworkManager finally does ask the kernel to connect, the kernel connects just fine. Not a kernel problem. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Auto-activating connection 'LAUREL'. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) starting connection 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): access point 'LAUREL' has security, but secrets are required. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'ssid' value 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'scan_ssid' value '1' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'key_mgmt' value 'WPA-PSK' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'psk' value '' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: set interface ap_scan to 1 Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): supplicant interface state: inactive -> scanning Jan 15 14:14:28 Aspire-5253 kernel: [ 252.465674] wlan0: authenticate with 00:0f:b3:b0:d6:3c Jan 15 14:14:28 Aspire-52
[Desktop-packages] [Bug 1099976] Re: NetworkManager falsely reports WPA network "out of range"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1099976 Title: NetworkManager falsely reports WPA network "out of range" Status in “network-manager” package in Ubuntu: Confirmed Bug description: On boot with amd64 Broadcom BCM43225, Raring NetworkManager correctly detects the network name, then NM falsely reports "out of range". What NM is trying to do is to connect without using the WPA encryption key which it already has. This is similar to bug 1097002 except in 1097002 NM doesn't even see the hidden network name even though it already has the encryption key for that network. In syslog below, says "has security but secrets are required". That's right, has security, but NM already has the secret encryption key; NM is supposed to use the key instead of disconnecting. Obviously NM doesn't even look to see it already has the key which it does. The branch in the NM script that sees "secrets are required" should go right ahead, see that it already has the "secrets", and use them. NetworkManager either doesn't have this path or is refusing to use it. I go on to connect manually with settings > network using the encryption key network manager already had and should have used. In any case, when NetworkManager finally does ask the kernel to connect, the kernel connects just fine. Not a kernel problem. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Auto-activating connection 'LAUREL'. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) starting connection 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): access point 'LAUREL' has security, but secrets are required. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'ssid' value 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'scan_ssid' value '1' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'key_mgmt' value 'WPA-PSK' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'psk' value '' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: set interface ap_scan to 1 Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): supplicant interface state: inactive -> scanning Jan 15 14:14:28 Aspire-5253 kernel: [ 252.465674] wlan0: authenticate with 00:0f:b3:b0:d6:3c Jan 15 14:14:28 Aspire-5253 wpa_supplicant[970]: wlan0: SME: Trying to authenticate with 00:0f:b3:b0:d6:3c (SSID='LAUREL' freq=2452 MHz) Jan 15 14:14:28 Aspire-5253 wpa_supplicant[970]: wlan0: Tryi
[Desktop-packages] [Bug 1099976] Re: NetworkManager falsely reports WPA network "out of range"
** Summary changed: - Raring network manager msg false out of range WPA network + NetworkManager falsely reports WPA network "out of range" ** Description changed: - On boot, Raring amd64 Broadcom BCM43225 the network manager correctly - detects the network name, then network manager falsely reports "out of - range". What the raring network manager is trying to do is to connect - without using the WPA encryption key which it already has. + On boot with amd64 Broadcom BCM43225, Raring NetworkManager correctly + detects the network name, then NM falsely reports "out of range". What + NM is trying to do is to connect without using the WPA encryption key + which it already has. - This is similar to bug 1097002 except in 1097002 the network manager - doesn't even see the hidden network name even though it already has the - encryption key for that network. + This is similar to bug 1097002 except in 1097002 NM doesn't even see the + hidden network name even though it already has the encryption key for + that network. In syslog below, says "has security but secrets are required". That's - right, has security, but network manager already has the secret - encryption key, network manager is supposed to use the key instead of - disconnecting. + right, has security, but NM already has the secret encryption key; NM is + supposed to use the key instead of disconnecting. - Obviously network manager doesn't even look to see it already has the - key which it does. + Obviously NM doesn't even look to see it already has the key which it + does. - The branch in the network manager script that sees "secrets are - required" should go right ahead, see that it already has the "secrets", - and use them. Network manager either doesn't have this path or is - refusing to use it. + The branch in the NM script that sees "secrets are required" should go + right ahead, see that it already has the "secrets", and use them. + NetworkManager either doesn't have this path or is refusing to use it. I go on to connect manually with settings > network using the encryption key network manager already had and should have used. - In any case, when network manager finally does ask the kernel to - connect, the kernel connects just fine. Not a kernel problem. + In any case, when NetworkManager finally does ask the kernel to connect, + the kernel connects just fine. Not a kernel problem. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Auto-activating connection 'LAUREL'. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) starting connection 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): access point 'LAUREL' has security, but secrets are required. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: (wlan0): device state change: prepare -> config (reason 'none') [40 50 0] Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Activation (wlan0/wireless): connection 'LAUREL' has security, and secrets exist. No new secrets needed. Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'ssid' value 'LAUREL' Jan 15 14:14:10 Aspire-5253 NetworkManager[785]: Config: added 'scan_ssid' value '1'
