Summary: | >=net-misc/networkmanager-0.9.6.4 (ifnet plugin) does not save settings for wired connection with 802.1x authentication | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kornel <kornel661> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | kornel661, main.haarp, tetromino |
Priority: | Normal | Keywords: | NeedPatch |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kornel
2013-02-19 11:51:06 UTC
Try switching to the keyfile plugin for networkmanager settings: set "plugins=keyfile" in /etc/NetworkManager/NetworkManager.conf, and then do "/etc/init.d/NetworkManager restart". (Note that after this, you will need to re-enter all of your connection settings once.) It's already on: /etc/NetworkManager $ cat NetworkManager.conf [main] plugins=ifnet,keyfile [ifnet] managed=true auto_refresh=false (In reply to comment #1) > Try switching to the keyfile plugin for networkmanager settings: set > "plugins=keyfile" in /etc/NetworkManager/NetworkManager.conf, and then do > "/etc/init.d/NetworkManager restart". > > (Note that after this, you will need to re-enter all of your connection > settings once.) (In reply to comment #2) > It's already on: > > /etc/NetworkManager $ cat NetworkManager.conf > [main] > plugins=ifnet,keyfile You have both ifnet and keyfile enabled, with ifnet as the default. I am hypothesizing that 802.1x settings might be saved successfully in keyfile format (which receives more testing upstream), but not in ifnet format. You were right! Thank you. After removing ifnet plugin (changing order didn't help) wired connections started working as expected (they survive reboot and I can even change their names). Unfortunately, as a side effect, I couldn't connect to my WPA2 wifi network with something like this in the logs: Feb 20 18:18:08 [NetworkManager] <info> Config: added 'ssid' value 'XXXX' Feb 20 18:18:08 [NetworkManager] <info> Config: added 'scan_ssid' value '1' Feb 20 18:18:08 [NetworkManager] <info> Config: added 'key_mgmt' value 'WPA-PSK' Feb 20 18:18:08 [NetworkManager] <info> Config: added 'psk' value '<omitted>' Feb 20 18:18:08 [NetworkManager] <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Feb 20 18:18:08 [NetworkManager] <info> Config: set interface ap_scan to 1 Feb 20 18:18:09 [NetworkManager] <info> (wlan0): supplicant interface state: disconnected -> scanning Feb 20 18:18:10 [kernel] [ 515.329818] wlan0: authenticate with XX:XX:XX:XX:XX:XX Feb 20 18:18:10 [kernel] [ 515.345007] wlan0: send auth to XX:XX:XX:XX:XX:XX (try 1/3) Feb 20 18:18:10 [kernel] [ 515.345032] wlan0: authenticated Feb 20 18:18:10 [NetworkManager] <info> (wlan0): supplicant interface state: scanning -> authenticating Feb 20 18:18:10 [NetworkManager] <info> (wlan0): supplicant interface state: authenticating -> associating Feb 20 18:18:10 [kernel] [ 515.352310] wlan0: associate with XX:XX:XX:XX:XX:XX (try 1/3) Feb 20 18:18:10 [kernel] [ 515.552932] wlan0: associate with XX:XX:XX:XX:XX:XX (try 2/3) Feb 20 18:18:11 [kernel] [ 515.753526] wlan0: associate with XX:XX:XX:XX:XX:XX (try 3/3) Feb 20 18:18:11 [kernel] [ 515.954138] wlan0: association with XX:XX:XX:XX:XX:XX timed out Feb 20 18:18:11 [NetworkManager] <info> (wlan0): supplicant interface state: associating -> disconnected Feb 20 18:18:16 [NetworkManager] <info> (wlan0): supplicant interface state: disconnected -> scanning Feb 20 18:18:17 [kernel] [ 521.880063] wlan0: authenticate with XX:XX:XX:XX:XX:XX Feb 20 18:18:17 [kernel] [ 521.893073] wlan0: send auth to XX:XX:XX:XX:XX:XX (try 1/3) Feb 20 18:18:17 [NetworkManager] <info> (wlan0): supplicant interface state: scanning -> authenticating Feb 20 18:18:17 [kernel] [ 522.093189] wlan0: send auth to XX:XX:XX:XX:XX:XX (try 2/3) Feb 20 18:18:17 [kernel] [ 522.293793] wlan0: send auth to XX:XX:XX:XX:XX:XX (try 3/3) Feb 20 18:18:17 [kernel] [ 522.494404] wlan0: authentication with XX:XX:XX:XX:XX:XX timed out Feb 20 18:18:23 [kernel] [ 528.430252] wlan0: authenticate with XX:XX:XX:XX:XX:XX Feb 20 18:18:23 [kernel] [ 528.444418] wlan0: send auth to XX:XX:XX:XX:XX:XX (try 1/3) Feb 20 18:18:23 [kernel] [ 528.444452] wlan0: authenticated Feb 20 18:18:23 [NetworkManager] <info> (wlan0): supplicant interface state: authenticating -> associating Feb 20 18:18:23 [kernel] [ 528.451805] wlan0: associate with XX:XX:XX:XX:XX:XX (try 1/3) Feb 20 18:18:23 [kernel] [ 528.652412] wlan0: associate with XX:XX:XX:XX:XX:XX (try 2/3) Feb 20 18:18:24 [kernel] [ 528.853021] wlan0: associate with XX:XX:XX:XX:XX:XX (try 3/3) Feb 20 18:18:24 [kernel] [ 529.053630] wlan0: association with XX:XX:XX:XX:XX:XX timed out Feb 20 18:18:24 [NetworkManager] <info> (wlan0): supplicant interface state: associating -> disconnected Feb 20 18:18:29 [NetworkManager] <info> (wlan0): supplicant interface state: disconnected -> scanning I rechecked configuration a couple of times and it seemd OK. (I masked some values by XXXX.) Anyways, restoring ifnet (so that ifnet and keyfile are active) helped with wifi and it seems wired connections that I configured with keyfile also work. I'll need to make sure wired conns are managed by ifnet and wifi by keyfile. Still valid with 0.9.8.2? (In reply to Pacho Ramos from comment #5) > Still valid with 0.9.8.2? Yes. The 802.1x configuration is not saved at all, it is only kept in memory during NM's runtime. Disabling the ifnet plugin solves this problem, along with a huge host of other bugs caused by it. I don't have any problems connecting to wireless without it, either. Maybe reporting to upstream could help (at least an upstream maintainer helps us with making NM "happier" with Gentoo) -> bugzilla.gnome.org When reported, please post the link here to let us track (In reply to Pacho Ramos from comment #7) > Maybe reporting to upstream could help (at least an upstream maintainer > helps us with making NM "happier" with Gentoo) -> bugzilla.gnome.org > > When reported, please post the link here to let us track Isn't the ifnet plugin an exclusively Gentoo thing? But it was upstreamed long time ago (like the plugin for opensuse, for example) +*networkmanager-0.9.10.0-r1 (13 Oct 2014) + + 13 Oct 2014; Pacho Ramos <pacho@gentoo.org> + +files/networkmanager-0.9.10.0-arpingpath.patch, + +networkmanager-0.9.10.0-r1.ebuild: + Ifnet plugin is now disabled because of it being unattended and unmaintained + for a long time, leading to some unfixed bugs and new problems appearing + (#443596, #458274, #493370, #498372, #523700). If some day somebody volunteers + for fixing/maintaining that plugin and forwarding all that fixes to upstream + it could be re-enabled of course. Append configure option regarding systemd + unit files install path only when systemd support is enabled to prevent + HAVE_SYSTEMD to be true (#524534 by Konstantin Ivanov). Ensure arping is found + (#523632 by Kobboi). + |