Network Manager fails to connect to a system stored network with "set_network_cb(): Couldn't set network config: Did not receive correct message.." in intrepid

[Steven]

Workaround: install the intrepid package from the network-manager PPA: http://launchpad.net/~network-manager/+archive

Binary package hint: network-manager

When attempting to connect to a network stored system wide, Network Manager fails with 'set_network_cb(): Couldn't set network config: Did not receive correct message..'
Opening the connection editor and re-entering my wep key allows me to connect once.
The wep key is correctly saved in the global configuration folder.

Here are the relevant portions of my logs:
Not Working:

Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) starting connection 'Allen'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): device state change: 3 -> 4
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): device state change: 4 -> 5
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0/wireless): access point 'Allen' has security, but secrets are required.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): device state change: 5 -> 6
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): device state change: 6 -> 4
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): device state change: 4 -> 5
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0/wireless): connection 'Allen' has security, and secrets exist. No new secrets needed.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'ssid' value 'Allen'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'bssid' value '00:0d:72:b2:fd:41'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'psk' value '<omitted>'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'wep_key1' value '<omitted>'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'wep_key2' value '<omitted>'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'wep_key3' value '<omitted>'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Config: set interface ap_scan to 1
Oct 24 16:47:25 TheBeagle NetworkManager: <WARN> set_network_cb(): Couldn't set network config: Did not receive correct message arguments..
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0/wireless): association request to the supplicant failed: fi.epitest.hostap.WPASupplicant.InvalidOptions - Did not receive correct message arguments.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): device state change: 5 -> 9
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) failed for access point (Allen)
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Marking connection 'Allen' invalid.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> Activation (wlan0) failed.
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): device state change: 9 -> 3
Oct 24 16:47:25 TheBeagle NetworkManager: <info> (wlan0): deactivating device (reason: 0).

Working:

Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0) starting connection 'Allen'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> (wlan0): device state change: 3 -> 4
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 24 16:48:31 TheBeagle NetworkManager: <info> (wlan0): device state change: 4 -> 5
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0/wireless): connection 'Allen' has security, and secrets exist. No new secrets needed.
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: added 'ssid' value 'Allen'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: added 'bssid' value '00:0d:72:b2:fd:41'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 24 16:48:31 TheBeagle NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 0
Oct 24 16:48:31 TheBeagle NetworkManager: <info> Config: set interface ap_scan to 1
Oct 24 16:48:31 TheBeagle NetworkManager: <info> (wlan0): supplicant connection state change: 0 -> 2
Oct 24 16:48:34 TheBeagle NetworkManager: <info> (wlan0): supplicant connection state change: 2 -> 3
Oct 24 16:48:34 TheBeagle NetworkManager: <info> (wlan0): supplicant connection state change: 3 -> 4
Oct 24 16:48:34 TheBeagle NetworkManager: <info> (wlan0): supplicant connection state change: 4 -> 7
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Allen'.
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct 24 16:48:34 TheBeagle NetworkManager: <info> (wlan0): device state change: 5 -> 7
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) scheduled...
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) started...
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Get) complete.
Oct 24 16:48:34 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Oct 24 16:48:34 TheBeagle avahi-daemon[5651]: Joining mDNS multicast group on interface wlan0.IPv4 with address 172.16.1.34.
Oct 24 16:48:34 TheBeagle avahi-daemon[5651]: New relevant interface wlan0.IPv4 for mDNS.
Oct 24 16:48:34 TheBeagle avahi-daemon[5651]: Registering new address record for 172.16.1.34 on wlan0.IPv4.
Oct 24 16:48:35 TheBeagle NetworkManager: <info> (wlan0): device state change: 7 -> 8
Oct 24 16:48:35 TheBeagle NetworkManager: <info> Policy set 'Allen' (wlan0) as default for routing and DNS.
Oct 24 16:48:35 TheBeagle NetworkManager: <info> Activation (wlan0) successful, device activated.
Oct 24 16:48:35 TheBeagle NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.

It appears that the network manager is not correctly fetching the encryption information when connecting. The network manager tries to set 4 wep keys and 1 psk key.

network-manager: 0.7~~svn20081018t105859-0ubuntu1
kernel: 2.6.27-7-generic

[falstaff (falstaff)]

I can confirm this using WEP Keys... NM is unusable when using System wide settings...

Also strange is that when I go into Wireless Config, the Wireless key isnt there, altough the key is saved in the config file under /etc/NetworkManager/system-connections/MyConnection...

[Helge Turk (ausdiemaus)]

Confirmed by another user.
Had this in Intrepid Beta and still with a fresh release install I did yesterday.
Driver: ndiswrapper, using WEP Encryption.

[Alexander Sack (asac)]

please do a tail -f -n0 /var/log/wpa_supplicant.log > /tmp/wpasupp.txt

then reproduce and after you see that error in syslog attach your wpasupp.txt

Thanks

[falstaff (falstaff)]

Here is what I've done:

1. Went into settings, insert the WEP-Key with the System Wide Setting on
2. Press OK, the connection works as expected...
3. Left-Klick on the NM Symbol and click on the wirless network => Disconnects from the network, as expected...
4. Left-Klick again on the NM Symbol and clicked again on the wireless network, the connection didnt came up => This is the bug...

Logs see attachement

[falstaff (falstaff)]

I belive that there is something wrong with WEP-Key fetching over DBUS from NM system service... That's why its working when I enter the key in the settings, nm-applet don't have to fetch the key over DBUS. The Key will be saved in the Settings file under /etc/NetworkManager/system-connections/Whatever, so its a problem of fetching the key...

[Alexander Sack (asac)]

system settings + keyring has probably issues. does it work if you dont use a system setting?

[falstaff (falstaff)]

Yes, it works without the system wide setting...

[Helge Turk (ausdiemaus)]

Only those lines are written to my wpa_supplicant.log while adding a new system-connection.

CTRL-EVENT-SCAN-RESULTS
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

[Charlie Collins (charlie-collins)]

I am experiencing this same issue in 8.10 release (Ibex). Was there a resolution or workaround for this?

The WEP key is shown when I open the connection up in nm-applet, but somehow it is not passed when nm tries to actually make the connection (though it knows security is required).

Syslog has this:

Nov 5 18:31:06 crotalus NetworkManager: <info> Activation
(wlan0/wireless): connection 'CCOLLINS_WIREFREE' has security, and
secrets exist. No new secrets needed.
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added 'ssid'
value 'CCOLLINS_WIREFREE'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'scan_ssid' value '1'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'key_mgmt' value 'NONE'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'auth_alg' value 'OPEN'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added 'psk'
value '<omitted>'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'wep_key0' value '<omitted>'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'wep_key1' value '<omitted>'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'wep_key2' value '<omitted>'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'wep_key3' value '<omitted>'
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: added
'wep_tx_keyidx' value '0'
Nov 5 18:31:06 crotalus NetworkManager: <info> Activation (wlan0)
Stage 2 of 5 (Device Configure) complete.
Nov 5 18:31:06 crotalus NetworkManager: <info> Config: set interface
ap_scan to 1
Nov 5 18:31:06 crotalus NetworkManager: <WARN> set_network_cb():
Couldn't set network config: Did not receive correct message
arguments..
Nov 5 18:31:06 crotalus NetworkManager: <info> Activation
(wlan0/wireless): association request to the supplicant failed:
fi.epitest.hostap.WPASupplicant.InvalidOptions - Did not receive
correct message arguments.
Nov 5 18:31:06 crotalus NetworkManager: <info> (wlan0): device state
change: 5 -> 9
Nov 5 18:31:06 crotalus NetworkManager: <info> Activation (wlan0)
failed for access point (CCOLLINS_WIREFREE)
Nov 5 18:31:06 crotalus NetworkManager: <info> Marking connection
'CCOLLINS_WIREFREE' invalid.

[Markus (markusb)]

I have the same issue with my Thinkpad A31p usin the built-in Wifi (Prism 2.5 Wavelan).

Is there a workaround ?

[StarShock (sshock3)]

Same issue here with Thinkpad T42 using ipw2200. Is there a workaround, please?

[StarShock (sshock3)]

I reproduced the bug with NetworkManager HEAD, so I submitted a bug upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=564709

[StarShock (sshock3)]

I submitted a patch that solved the problem nicely for me: http://bugzilla.gnome.org/attachment.cgi?id=124773&action=view

[falstaff (falstaff)]

Hi StarShock,

Can you provide a deb package? So then I would test it on my machine also...

[StarShock (sshock3)]

I would but I actually don't have any experience in creating deb packages.

[Chris Bainbridge (chris-bainbridge)]

I can confirm this. Without StarShock's patch I can not associate with a WEP network
using a global WEP key in /etc/NetworkManager/nm-system-settings.conf/ config.
I get the same error "set_network_cb(): Couldn't set network config: Did not
receive correct message". With the patch I can now connect.

I think wpa_supplicant is complaining about the following section of config:
[802-11-wireless-security]
key-mgmt=none
wep-tx-keyidx=0
wep-key0=xxxx

[Alexander Sack (asac)]

0.7 final packages are in ~network-manager PPA ... please test those

[Riccardone (rtromba)]

I installed it a while ago... and it just works!
Thank you

[falstaff (falstaff)]

Works for me too, thanks!

[Alexander Sack (asac)]

probably need a backport for intrepid then.

[Alexander Sack (asac)]

fix committed in ubuntu.0.7 branches (which have 0.7 final)

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 0.7-0ubuntu1

---------------
network-manager (0.7-0ubuntu1) jaunty; urgency=low

  * (merge) new upstream release NetworkManager 0.7 final
    - rev 3802 lp:~vcs-imports/network-manager/main/
    + fix LP: #288963 Network Manager fails to connect to a system stored
      network with "set_network_cb(): Couldn't set network config: Did not receive
      correct message.." in intrepid
    + fix LP: #288703 Routes lost on DHCP lease renewal (breaks VPN)

  * drop probe v250 modem patch; this should be done in udev-extras; until
    that happens we rely on accurate hal-info
    - delete debian/patches/add_probe_for_v250_modems.patch
    - update debian/patches/series
  * drop upstreamed patches
    - delete debian/patches/50_gcc43.patch
    - delete debian/patches/lp282207_set_apn_at_syntax.patch
    - delete debian/patches/lp268667_more_ppp_default_options.patch
    - delete debian/patches/lp278631-initscript-polishing.patch
    - update debian/patches/series
  * drop unused patch
    - delete debian/patches/41o_completely_deactivate_stage1.patch
  * make manual regristration timeout patch out of automatic one (which
    was applied upstream)
    - rename debian/patches/lp303142_more_time_for_automatic_registration.patch
      => debian/patches/lp303142_more_time_for_manual_registration.patch
  * add patch to fix ftbfs
    - add debian/patches/ftbfs_nm_netlink_monitor.patch
    - update debian/patches/series
  * [libnm-util-dev] dont try to install nm-setting-ip6-config.h - which is
    supposed to be hidden in 0.7 final
    - update debian/libnm-util-dev.install
  * prepatch upstream soname version bump for libnm-util
    - add debian/patches/04-ltversioning.patch
    - update debian/patches/series
    ship the libs in libnm-util1
    - update debian/control
    - rename debian/libnm-util0.install => debian/libnm-util1.install
    and bump so shlibs control file info for libnm-util1
    - update debian/rules
  * add easy bzr builddeb support with proper upstream-revision (--show-ids)
    - add .bzr-builddeb/default.conf
  * install plugin in ppp 2.4.4 and 2.4.5 directory
    - update debian/network-manager.install

 -- Alexander Sack <email address hidden> Mon, 12 Jan 2009 13:29:24 +0100

[StarShock (sshock3)]

FYI, the bug no longer exists upstream (which does not have my patch).

Please see comment #12 on the upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=564709

The real problem was nm-system-settings returning non-null zero-length secrets over dbus (secrets that should not have been returned at all). However, the latest nm-system-settings (from svn) works correctly, fixing the original bug (without the need for my patch).

The bug was apparently fixed upstream sometime in the last few months, but I have no idea exactly when.

[StarShock (sshock3)]

I tracked down when it was fixed upstream. See comment #13 in the upstream bug. (It was fixed on Nov 12th in commit e4ae149...)

So you may want to undo my patch and apply this change instead, since it fixes the underlying problem.

[Jacob Godserv (fun2program8)]

This bug still exists for me, and I have all the latest updates. The workaround is to retype the WEP key, save it, and then NetworkManager connects (that once).

[Alexander Sack (asac)]

its really unlikely that this gets fixed in intrepid mainarchive as the backport requires UI changes. use the network-manager team PPA to get a more recent network-manager which fixes this.

[StarShock (sshock3)]

If it's too difficult to update nm-system-settings in Intrepid then why not settle for my one-line patch (for Intrepid). Yeah, it's not the correct fix, but I doubt it will cause any harm either.

[Jacob Godserv (fun2program8)]

This bug appears to be fixed for Karmic.

[Sergio Zanchetta (primes2h)]

Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on 30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please feel free to report any other bugs you may find.
Thank you.

[Sergio Zanchetta (primes2h)]

I realized I had made a mistake.
Intrepid Ibex 8.10 "will reach" EOL on 30 "APRIL" 2010.

Sorry for this.

Anyway, I think that one month doesn't make any difference now.