Bug 226140

Summary: knetworkmanager fails to associate with insecure network
Product: [Unmaintained] Network Management Reporter: S. Burmeister <sven.burmeister>
Component: generalAssignee: Will Stephenson <wstephenson>
Status: RESOLVED WAITINGFORINFO    
Severity: normal CC: lamarque
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description S. Burmeister 2010-02-10 14:44:48 UTC
Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    openSUSE RPMs

knetworkmanager fails to associate with an insecure network ("WiPS") while nm-applet associates without any issue.

nm-tool:


NetworkManager Tool

State: disconnected

- Device: eth0 -----------------------------------------------------------------
  Type:              Wired
  Driver:            r8169
  State:             unavailable
  Default:           no
  HW Address:        00:21:85:4E:CA:C5

  Capabilities:
    Carrier Detect:  yes
    Speed:           10 Mb/s

  Wired Properties
    Carrier:         off


- Device: wlan0 ----------------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            r8180
  State:             disconnected
  Default:           no
  HW Address:        00:21:85:79:4B:80

  Capabilities:

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points 
    WiPS:            Infra, 00:11:20:68:8C:A1, Freq 2427 MHz, Rate 54 Mb/s, Strength 48
    WiPSecure:       Infra, 00:11:20:68:8C:A2, Freq 2427 MHz, Rate 54 Mb/s, Strength 46
    WLANFB02:        Infra, 00:11:20:68:8C:A0, Freq 2427 MHz, Rate 54 Mb/s, Strength 45
    WiPS:            Infra, 00:11:20:68:89:C1, Freq 2412 MHz, Rate 54 Mb/s, Strength 51
    WLANFB02:        Infra, 00:11:20:68:89:C0, Freq 2412 MHz, Rate 54 Mb/s, Strength 51
    WiPSecure:       Infra, 00:11:20:68:89:C2, Freq 2412 MHz, Rate 54 Mb/s, Strength 51
    WiPS:            Infra, 00:11:20:2A:7D:61, Freq 2437 MHz, Rate 54 Mb/s, Strength 58
    WiPSecure:       Infra, 00:11:20:2A:7D:62, Freq 2437 MHz, Rate 54 Mb/s, Strength 58
    WLANFB02:        Infra, 00:11:20:2A:7D:60, Freq 2437 MHz, Rate 54 Mb/s, Strength 60


------ KNetworkmanager:

NetworkManager
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) starting connection 'WiPS'                              
Feb 10 14:03:42 linux-blam NetworkManager: <info>  (wlan0): device state change: 3 -> 4 (reason 0)                            
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...              
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...                
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...            
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.                 
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...             
Feb 10 14:03:42 linux-blam NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)                            
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0/wireless): access point 'WiPS' has security, but secrets are required.
Feb 10 14:03:42 linux-blam NetworkManager: <info>  (wlan0): device state change: 5 -> 6 (reason 0)                                         
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.                            
Feb 10 14:03:42 linux-blam NetworkManager: <WARN>  update_one_setting(): Failed to update connection secrets: 1 802-1x                     
Feb 10 14:03:42 linux-blam NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting 'ipv4'.         
Feb 10 14:03:42 linux-blam NetworkManager: <WARN>  real_connection_secrets_updated(): Ignoring updated secrets for setting '802-11-wireless'.
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...                             
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Feb 10 14:03:42 linux-blam NetworkManager: <info>  (wlan0): device state change: 6 -> 4 (reason 0)
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Feb 10 14:03:42 linux-blam NetworkManager: <info>  (wlan0): device state change: 4 -> 5 (reason 0)
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0/wireless): connection 'WiPS' requires no security.  No secrets needed.
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Config: added 'ssid' value 'WiPS'
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Feb 10 14:03:42 linux-blam NetworkManager: <info>  Config: set interface ap_scan to 1
Feb 10 14:03:42 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Feb 10 14:03:42 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Feb 10 14:03:58 linux-blam NetworkManager: <info>  wlan0: link timed out.
Feb 10 14:04:08 linux-blam NetworkManager: <info>  Activation (wlan0/wireless): association took too long, failing activation.
Feb 10 14:04:08 linux-blam NetworkManager: <info>  (wlan0): device state change: 5 -> 9 (reason 11)
Feb 10 14:04:08 linux-blam NetworkManager: <info>  Activation (wlan0) failed for access point (WiPS)
Feb 10 14:04:08 linux-blam NetworkManager: <info>  Marking connection 'WiPS' invalid.
Feb 10 14:04:08 linux-blam NetworkManager: <info>  Activation (wlan0) failed.
Feb 10 14:04:08 linux-blam NetworkManager: <info>  (wlan0): device state change: 9 -> 3 (reason 0)
Feb 10 14:04:08 linux-blam NetworkManager: <info>  (wlan0): deactivating device (reason: 0).

no entries in wpa_supplicant

qdbus --system --literal org.freedesktop.NetworkManagerUserSettings /org/freedesktop/NetworkManagerSettings/5 org.freedesktop.NetworkManagerSettings.Connection.GetSettings
[Argument: a{sa{sv}}
{"802-11-wireless" = [Argument: a{sv}
{"mode" = [Variant(QString): "infrastructure"],
"seen-bssids" = [Variant(QStringList): {"00:1D:0F:D9:03:99"}],
"ssid" = [Variant(QByteArray): {87, 105, 80, 83}]}],
"802-11-wireless-security" = [Argument: a{sv}
{"key-mgmt" = [Variant(QString): "wpa-psk"]}],
"connection" = [Argument: a{sv}
{"autoconnect" = [Variant(bool): true],
"id" = [Variant(QString): "WiPS"],
"timestamp" = [Variant(uint): 1265788760],
"type" = [Variant(QString): "802-11-wireless"],
"uuid" = [Variant(QString): "baacee48-1409-4907-8fed-0be2ff3add46"]}],
"ipv4" = [Argument: a{sv}
{"method" = [Variant(QString): "auto"]}]}]

--------- nm-applet:

NetwrokManager:

Feb 10 14:07:03 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating                             
Feb 10 14:07:03 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> disconnected                         
Feb 10 14:07:03 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> associated                          
Feb 10 14:07:03 linux-blam NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> completed                             
Feb 10 14:07:03 linux-blam NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'WiPS'.                                                                                                                           
Feb 10 14:07:03 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.                            
Feb 10 14:07:03 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...                            
Feb 10 14:07:03 linux-blam NetworkManager: <info>  (wlan0): device state change: 5 -> 7 (reason 0)                                            
Feb 10 14:07:03 linux-blam NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction.                                             
Feb 10 14:07:03 linux-blam NetworkManager: <info>  dhclient started with pid 2415                                                             
Feb 10 14:07:03 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.                             
Feb 10 14:07:03 linux-blam NetworkManager: <info>  DHCP: device wlan0 state changed (null) -> preinit                                         
Feb 10 14:07:10 linux-blam NetworkManager: <info>  DHCP: device wlan0 state changed preinit -> bound                                          
Feb 10 14:07:10 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Feb 10 14:07:10 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Feb 10 14:07:10 linux-blam NetworkManager: <info>    address 172.16.0.16
Feb 10 14:07:10 linux-blam NetworkManager: <info>    prefix 23 (255.255.254.0)
Feb 10 14:07:10 linux-blam NetworkManager: <info>    gateway 172.16.0.1
Feb 10 14:07:10 linux-blam NetworkManager: <info>    nameserver '172.16.0.1'
Feb 10 14:07:10 linux-blam NetworkManager: <info>    domain name 'FH-Bonn-Rhein-Sieg.de'
Feb 10 14:07:10 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Feb 10 14:07:10 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Feb 10 14:07:10 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Feb 10 14:07:11 linux-blam NetworkManager: <info>  (wlan0): device state change: 7 -> 8 (reason 0)
Feb 10 14:07:11 linux-blam NetworkManager: <debug> [1265807231.038002] periodic_update(): Roamed from BSSID 00:11:20:68:8C:A1 (WiPS) to 00:11:20:2A:7D:61 (WiPS)
Feb 10 14:07:11 linux-blam NetworkManager: <debug> [1265807231.039511] run_netconfig(): Spawning '/sbin/netconfig modify --service NetworkManager'
Feb 10 14:07:11 linux-blam NetworkManager: <debug> [1265807231.052149] write_to_netconfig(): Writing to netconfig: DNSSEARCH='FH-Bonn-Rhein-Sieg.de FH-Bonn-Rhein-Sieg.de'#012
Feb 10 14:07:11 linux-blam NetworkManager: <debug> [1265807231.052302] write_to_netconfig(): Writing to netconfig: DNSSERVERS='172.16.0.1'#012
Feb 10 14:07:11 linux-blam NetworkManager: <info>  Clearing nscd hosts cache.
Feb 10 14:07:11 linux-blam NetworkManager: <info>  Policy set 'Auto WiPS' (wlan0) as default for routing and DNS.
Feb 10 14:07:11 linux-blam NetworkManager: <info>  Activation (wlan0) successful, device activated.
Feb 10 14:07:11 linux-blam NetworkManager: <info>  Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Feb 10 14:07:11 linux-blam nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs' exited with error status 1.


wpa_supplicant:
Trying to associate with 00:11:20:2a:7d:61 (SSID='WiPS' freq=2437 MHz)
Association request to the driver failed
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Associated with 00:11:20:2a:7d:61
CTRL-EVENT-CONNECTED - Connection to 00:11:20:2a:7d:61 completed (auth) [id=0 id_str=]
CTRL-EVENT-SCAN-RESULTS

qdbus --system --literal org.freedesktop.NetworkManagerUserSettings /org/freedesktop/NetworkManagerSettings/2 org.freedesktop.NetworkManagerSettings.Connection.GetSettings
[Argument: a{sa{sv}}
{"802-11-wireless" = [Argument: a{sv}
{"mode" = [Variant(QString): "infrastructure"],
"seen-bssids" = [Variant(QStringList):
{"00:11:20:2a:7d:61", "00:11:20:68:8c:a1"}],
"ssid" = [Variant(QByteArray): {87, 105, 80, 83}]}],
"connection" = [Argument: a{sv}
{"uuid" = [Variant(QString): "e9d1273b-40ee-4224-bd52-304d4380ae86"],
"id" = [Variant(QString): "Auto WiPS"],
"type" = [Variant(QString): "802-11-wireless"],
"timestamp" = [Variant(qulonglong): 1265808070]}]}]
Comment 1 S. Burmeister 2010-04-20 13:35:50 UTC
I removed all of networkmanagement's configs and data an tried again. This time it worked. If one compares the connection settings it appears that although security is set to "", i.e. empty there is a security section in that config file which causes the failure.

non-working connection config file:

[802-11-wireless]
band=bg
bssid=
channel=0
macaddress=
mode=infrastructure
mtu=0
rate=0
security=
seenbssids=00:1D:0F:D9:03:99
ssid=WiPS
txpower=0

[802-11-wireless-security]
authalg=none
group=
keymgmt=WPAPSK
leapusername=
pairwise=
proto=
securityType=WpaPsk
weptxkeyindex=0

[connection]
autoconnect=true
icon=network-wireless
id=WiPS
timestamp=2010,2,10,8,59,20
type=802-11-wireless
uuid={baacee48-1409-4907-8fed-0be2ff3add46}

[ipv4]
addresses=
dhcpclientid=
dhcphostname=
dns=
dnssearch=
ignoreautoroute=false
ignoredhcpdns=false
method=Automatic
neverdefault=false
routes=

--------------------------------------

working connection file:

[802-11-wireless]
band=bg
bssid=
channel=0
macaddress=
mode=infrastructure
mtu=0
rate=0
security=
seenbssids=00:11:20:2A:7D:61
ssid=WiPS
txpower=0

[connection]
autoconnect=true
icon=network-wireless
id=WiPS
timestamp=2010,4,20,13,28,31
type=802-11-wireless
uuid={d1797341-2374-4fae-b65e-f5384648cd29}

[ipv4]
addresses=
dhcpclientid=
dhcphostname=
dns=
dnssearch=
ignoreautoroute=false
ignoredhcpdns=false
method=Automatic
neverdefault=false
routes=
Comment 2 S. Burmeister 2010-04-20 13:45:31 UTC
I found the bug.

If one sets a connection to e.g. WPA Personal the following section is added to the config file:

[802-11-wireless-security]
authalg=none
group=
keymgmt=WPAPSK
leapusername=
pairwise=
proto=
securityType=WpaPsk
weptxkeyindex=0

If one edits the connection after that and sets its security to "none" the section is not removed. And connecting fails.

So either knetwokmanager should ingnore the config file section if it does not fit the value set in "security=" or it should get removed as soon as the security is set to "none" in the connection's settings.
Comment 3 Lamarque V. Souza 2011-05-08 20:08:05 UTC
Can you test a more recent snapshot of Plasma NM and not the monolithic knetworkmanager, which umaintained and nobody is fixing bugs in it?