GNOME Bugzilla – Bug 574803
Auto Activation of Wired Network (eth0) not working
Last modified: 2009-03-12 20:26:22 UTC
Hello all, After NetworkManager update on Mar 09 to: ------------------------------------------------------- [root@hostname ~]# rpm -qa | grep -i network NetworkManager-openvpn-0.7.0.99-1.fc10.i386 NetworkManager-vpnc-0.7.0.99-1.fc10.i386 NetworkManager-glib-0.7.0.99-1.fc10.i386 NetworkManager-gnome-0.7.0.99-1.fc10.i386 system-config-network-1.5.95-1.fc10.noarch NetworkManager-0.7.0.99-1.fc10.i386 system-config-network-tui-1.5.95-1.fc10.noarch [root@hostname ~]# [root@hostname ~]# grep -i network /var/log/yum.log | grep 'Mar 09' Mar 09 18:54:31 Updated: 1:NetworkManager-glib-0.7.0.99-1.fc10.i386 Mar 09 18:54:34 Updated: 1:NetworkManager-0.7.0.99-1.fc10.i386 Mar 09 18:54:43 Updated: 1:NetworkManager-vpnc-0.7.0.99-1.fc10.i386 Mar 09 18:54:45 Updated: 1:NetworkManager-gnome-0.7.0.99-1.fc10.i386 Mar 09 18:54:47 Updated: 1:NetworkManager-openvpn-0.7.0.99-1.fc10.i386 [root@hostname ~]# ------------------------------------------------------- an issue appeared with the activation of my Wired Network (eth0), No VPN Networks, no Wireless Networks. I activated it manually several times from NetworkManager Applet 0.7.0.99 but Networkmanager still did not save its settings and so did not activate eth0 automatically on the next reboot. I need to activate it every time when I log on from the applet. This never happened in the previous version installed: ------------------------------------------------------- Jan 08 15:17:43 Updated: 1:NetworkManager-glib-0.7.0-1.git20090102.fc10.i386 Jan 08 15:18:58 Updated: 1:NetworkManager-0.7.0-1.git20090102.fc10.i386 Jan 08 15:19:09 Updated: 1:NetworkManager-vpnc-0.7.0-1.svn13.fc10.i386 Jan 08 15:19:12 Updated: 1:NetworkManager-gnome-0.7.0-1.git20090102.fc10.i386 Jan 08 15:19:13 Updated: 1:NetworkManager-openvpn-0.7.0-18.svn11.fc10.i386 ------------------------------------------------------- Here is the messages: ------------------------------------------------------- Mar 10 19:43:55 hostname acpid: starting up Mar 10 19:43:56 hostname NetworkManager: <info> starting... Mar 10 19:43:56 hostname NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():#012Sucess#012 Mar 10 19:43:56 hostname NetworkManager: <info> (eth0): new Ethernet device (driver: 'e100') Mar 10 19:43:56 hostname NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_20_ed_7e_83_ea Mar 10 19:43:56 hostname NetworkManager: <WARN> udevadm_get_modem_capabilities(): could not run udevadm to get modem capabilities for '/sys/devices/pnp0/00:09/tty/ttyS1': Failed to execute child process "/sbin/udevadm" (Permission denied) Mar 10 19:43:56 hostname NetworkManager: <WARN> udevadm_get_modem_capabilities(): could not run udevadm to get modem capabilities for '/sys/devices/pnp0/00:08/tty/ttyS0': Failed to execute child process "/sbin/udevadm" (Permission denied) Mar 10 19:43:56 hostname NetworkManager: <info> Trying to start the supplicant... Mar 10 19:43:56 hostname NetworkManager: <WARN> udevadm_get_modem_capabilities(): could not run udevadm to get modem capabilities for '/sys/devices/pnp0/00:08/tty/ttyS0': Failed to execute child process "/sbin/udevadm" (Permission denied) Mar 10 19:43:56 hostname NetworkManager: <WARN> udevadm_get_modem_capabilities(): could not run udevadm to get modem capabilities for '/sys/devices/pnp0/00:09/tty/ttyS1': Failed to execute child process "/sbin/udevadm" (Permission denied) Mar 10 19:43:56 hostname NetworkManager: <info> Trying to start the system settings daemon... Mar 10 19:43:57 hostname acpid: client connected from 2060[68:68] Mar 10 19:43:57 hostname nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Mar 10 19:43:57 hostname nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-lo ... Mar 10 19:43:57 hostname nm-system-settings: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ... Mar 10 19:43:57 hostname nm-system-settings: ifcfg-rh: read connection 'System eth0' Mar 10 19:43:59 hostname xinetd[2095]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in. Mar 10 19:43:59 hostname xinetd[2095]: Started working: 0 available services Mar 10 19:44:00 hostname /usr/sbin/gpm[2129]: *** info [daemon/startup.c(136)]: Mar 10 19:44:00 hostname /usr/sbin/gpm[2129]: Started gpm successfully. Entered daemon mode. Mar 10 19:44:01 hostname NetworkManager: <info> (eth0): device state change: 1 -> 2 Mar 10 19:44:01 hostname NetworkManager: <info> (eth0): bringing up device. Mar 10 19:44:01 hostname kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex Mar 10 19:44:01 hostname kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready Mar 10 19:44:01 hostname kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Mar 10 19:44:01 hostname NetworkManager: <info> (eth0): preparing device. Mar 10 19:44:01 hostname NetworkManager: <info> (eth0): deactivating device (reason: 2). Mar 10 19:44:01 hostname NetworkManager: <info> (eth0): carrier now ON (device state 2) Mar 10 19:44:01 hostname NetworkManager: <info> (eth0): device state change: 2 -> 3 ##### Manually select "System eth0" from NetworkManager Applet 0.7.0.99 ##### Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) starting connection 'System eth0' Mar 10 19:50:34 hostname NetworkManager: <info> (eth0): device state change: 3 -> 4 Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... Mar 10 19:50:34 hostname NetworkManager: <info> (eth0): device state change: 4 -> 5 Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... Mar 10 19:50:34 hostname NetworkManager: <info> (eth0): device state change: 5 -> 7 Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Beginning DHCP transaction. Mar 10 19:50:34 hostname NetworkManager: <info> dhclient started with pid 3005 Mar 10 19:50:34 hostname NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. Mar 10 19:50:34 hostname dhclient: Internet Systems Consortium DHCP Client 4.0.0 Mar 10 19:50:34 hostname dhclient: Copyright 2004-2007 Internet Systems Consortium. Mar 10 19:50:34 hostname dhclient: All rights reserved. Mar 10 19:50:34 hostname dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Mar 10 19:50:34 hostname dhclient: Mar 10 19:50:34 hostname NetworkManager: <info> DHCP: device eth0 state changed (null) -> preinit Mar 10 19:50:34 hostname dhclient: Listening on LPF/eth0/00:20:ed:7e:83:ea Mar 10 19:50:34 hostname dhclient: Sending on LPF/eth0/00:20:ed:7e:83:ea Mar 10 19:50:34 hostname dhclient: Sending on Socket/fallback Mar 10 19:50:36 hostname dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Mar 10 19:50:36 hostname dhclient: DHCPOFFER from 192.168.10.1 Mar 10 19:50:36 hostname dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67 Mar 10 19:50:36 hostname dhclient: DHCPACK from 192.168.10.1 Mar 10 19:50:36 hostname dhclient: bound to 192.168.10.100 -- renewal in 39677 seconds. Mar 10 19:50:36 hostname NetworkManager: <info> DHCP: device eth0 state changed preinit -> bound Mar 10 19:50:36 hostname NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... Mar 10 19:50:36 hostname NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started... Mar 10 19:50:36 hostname NetworkManager: <info> address 192.168.10.100 Mar 10 19:50:36 hostname NetworkManager: <info> prefix 24 (255.255.255.0) Mar 10 19:50:36 hostname NetworkManager: <info> gateway 192.168.10.1 Mar 10 19:50:36 hostname NetworkManager: <info> nameserver '192.168.10.1' Mar 10 19:50:36 hostname NetworkManager: <info> domain name 'example.com' Mar 10 19:50:36 hostname NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... Mar 10 19:50:36 hostname NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. Mar 10 19:50:36 hostname NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... Mar 10 19:50:36 hostname avahi-daemon[2174]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.10.100. Mar 10 19:50:36 hostname avahi-daemon[2174]: New relevant interface eth0.IPv4 for mDNS. Mar 10 19:50:36 hostname avahi-daemon[2174]: Registering new address record for 192.168.10.100 on eth0.IPv4. Mar 10 19:50:37 hostname NetworkManager: <info> (eth0): device state change: 7 -> 8 Mar 10 19:50:37 hostname NetworkManager: <info> Policy set 'System eth0' (eth0) as default for routing and DNS. Mar 10 19:50:37 hostname NetworkManager: <info> Activation (eth0) successful, device activated. Mar 10 19:50:37 hostname NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. ------------------------------------------------------- Not sure if this is a bug or not, just trying to figure out that, as the documentation on the NetworkManager website is not enough. Fedora 10 2.6.27.19-170.2.35.fc10.i686 #1 SMP Mon Feb 23 13:21:22 EST 2009 i686 i686 i386 GNU/Linux Best Regards, Boyan Boychev
Hello all, More information here: https://bugzilla.redhat.com/show_bug.cgi?id=489398 You could fix the issue with changing to/adding "ONBOOT=yes" in /etc/sysconfig/network-scripts/ifcfg-eth0 (without quotes). According to Dan Williams it is not a bug but normal behaviour with the new version. Best Regards, Boyan Boychev