Created attachment 853224 [details] Network Manager output Description of problem: Since Fedora 20, when I try to connect to my office wire network, NetworkManager fail with this message: <error> [1390308223.167051] [platform/nm-linux-platform.c:1127] add_object(): Netlink error: Unspecific failure All works fine with Fedora 19. I attach a file with full journalctl output. Version-Release number of selected component (if applicable): NetworkManager-0.9.9.0-25.git20131003.fc20.i686 dhclient-4.2.5-26.fc20.i686 How reproducible: When connect the ethernet cable, this message appear repeatly. Steps to Reproduce: 1. With NetworkManager started 2. Connect ethernet cable Actual results: Can't connect to wired network using NetWorkManager Expected results: Connect to wired network using NetworkManager Additional info: Ethernet controller from lspci: 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) Laptop: Lenovo T430 Also fail in a Levono T420i, with NetworkManager-0.9.9.0-23.git20131003.fc20.x86_64, dhclient-4.2.5-26.fc20.x86_64 and Ethernet Card: 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
Created attachment 853225 [details] dhclient log This log, is when I get IP, routes and ethernet connections works fine.
# ethtool -i em1 driver: e1000e version: 2.3.2-k firmware-version: 0.13-3 bus-info: 0000:00:19.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no # uname -a Linux zion.my.domain.com 3.12.8-300.fc20.i686+PAE #1 SMP Thu Jan 16 01:19:09 UTC 2014 i686 i686 i386 GNU/Linux
This configuration works fine: 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) driver: e1000e version: 2.3.2-k firmware-version: 0.13-3 bus-info: 0000:00:19.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: no Linux hal2000 3.12.6-200.fc19.i686 #1 SMP Mon Dec 23 17:12:10 UTC 2013 i686 i686 i386 GNU/Linux
Previous configuration, use NetworkManager-0.9.8.8-2.fc19.i686
This has hit me when I updated NM from -20 to -28 on one of my machines. -29 also looks pretty broken. I'm trying to downgrade back to -20
> <error> [1390308223.167051] [platform/nm-linux-platform.c:1127] add_object(): Netlink error: Unspecific failure This looks like a problem with adding an address or route. We added a debug print to catch such errors in NetworkManager-0.9.9.0-16.git20131003. @Renato: That's strange I don't see it in your output. Anyway, would you install latest Fedora 20 NM and try again. Even better if you could try with https://admin.fedoraproject.org/updates/FEDORA-2014-2092/NetworkManager-0.9.9.0-29.git20140131.fc20 from testing repository. @Paul: Would you include logs so that we can see the debug logs from netlink?
The computer I'm using for this is 3000km away, so debugging is challenging. Nevertheless, there was a lot of noise in the system - it's br0 over team0 over eth0, I removed team0 and it didn't work and eventually the problem looks like it's br0/libnl3 bz#1063290.
Created attachment 861808 [details] NetworkManager 0.9.9.0-29.git20140131.fc20 output Jirka, I update NetworkManager{,-glib} to 0.9.9.0-29.git20140131.fc20 and start the service. This file is the output. NetworkManager applet is hidden now, but the interface have IP and all the routes. -- Renato
Created attachment 871082 [details] Debug log of Netlink error I also get the "Netlink error: Unspecific failure" but only at $WORK, not at $HOME, both using wires. I have NetworkManager-0.9.9.0-31.git20131003.fc20.x86_64 but it has done it with prior versions as well starting around the time others have noted. I don't have IPv6 enabled on the connection. I used this debugging command: nmcli g logging level debug domains core,hw,device,ip4,dhcp4,ip6,dhcp6 The lines of interest seem to be: NetworkManager[23147]: <debug> [1394041594.426203] [dhcp-manager/nm-dhcp-client.c:1236] ip4_options_to_config(): adding route for server identifier: 10.10.13.144/32 via 10.10.13.129 metric 0 mss 0 [...] NetworkManager[23147]: <debug> [1394041594.427437] [platform/nm-platform.c:1492] nm_platform_ip4_route_add(): route: adding or updating IPv4 route: 10.10.13.144/32 via 10.10.13.129 dev em1 metric 1 mss 0 NetworkManager[23147]: <error> [1394041594.429421] [platform/nm-linux-platform.c:1222] add_object(): Netlink error: Unspecific failure NetworkManager[23147]: <debug> [1394041594.429488] [devices/nm-device.c:4895] nm_device_set_ip4_config(): (em1): update IP4Config instance (/org/freedesktop/NetworkManager/IP4Config/181)
George and I are at the same $WORK, and both experienced the same problem with this version of NetworkManager. This is a critical system component; why is the QA on updates so lacking?? I used the following command to downgrade back to the previous version that worked: sudo yum downgrade NetworkManager NetworkManager-glib network-manager-applet nm-connection-editor libnm-gtk I then added this line to the [main] section of "/etc/yum.conf" to prevent this from happening again: exclude=NetworkManager NetworkManager-glib libnm-gtk network-manager-applet nm-connection-editor I'm running the STABLE release of Fedora, not Rawhide. A simple "yum update" should NEVER cripple my system like this, yet this has happened REPEATEDLY with NetworkManager.
Created attachment 871550 [details] Diff of -20 vs -31 connection. I downgraded back to NetworkManager-0.9.9.0-20.git20131003.fc20.x86_64 (which works for me) and ran a diff of their debugging output. Oddly, both logs have the "Netlink error: Unspecific failure" message, but -20 doesn't error out the connection like -31 does. The logs were normalized with this command so I could compare them: perl -pe 's/\[\d+\]//; s/\[\d{10}\.\d{6}\]//; s/\.c:\d+\]/.c:~]/; s/0x[0-9a-f]{8,12}/0xdeadbeef/;' ...
At $WORK we change dhcp route config, and now with one default gw... Network Manager works. At $HOME with only the default gw, Network Manager always works. :(
... After make the 'yum downgrade ...' in comment #10.
Same problem, downgrading from NetworkManager-0.9.9.0-31.git20131003.fc20.i686 to NetworkManager-0.9.9.0-20.git20131003.fc20.i686 doesn't help at all: NetworkManager[571]: <error> [1396434424.503653] [platform/nm-linux-platform.c:1222] add_object(): Netlink error: Unspecific failure Ethernet controller: Qualcomm Atheros Attansic L2 Fast Ethernet (rev a0), driver atl2 Is there some repo with functioning version?? I tried NM_CONTROLLED=no (which works) and ifup from rc.local, but it doesn't work, after login, I have to do it manually - this is unusable.
Created attachment 950239 [details] Lenovo X220 output Same problems on Lenovo X220
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.