Bugzilla – Bug 732696
Yast2 leaves network down after changes to eth0
Last modified: 2012-04-04 14:38:25 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 When I make changes to network in yast2 (IP, gateway) save and exit the network is in a down state needing ifup eth0 to bring it up. eth0 device: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) Reproducible: Always Steps to Reproduce: 1.Open yast2 2.make a change to Ethernet card settings 3.Save and exit. Actual Results: No eth0 steve@linux-vlkq:~> /sbin/ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:431 errors:0 dropped:0 overruns:0 frame:0 TX packets:431 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:35294 (34.4 Kb) TX bytes:35294 (34.4 Kb) Expected Results: steve@linux-vlkq:~> /sbin/ifconfig eth0 Link encap:Ethernet HWaddr F4:6D:04:D0:D0:5D inet addr:10.2.1.6 Bcast:10.2.1.255 Mask:255.255.255.0 inet6 addr: fe80::f66d:4ff:fed0:d05d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2858055 errors:0 dropped:201249 overruns:0 frame:0 TX packets:1332631 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2324447628 (2216.7 Mb) TX bytes:141836242 (135.2 Mb) Interrupt:46 Base address:0xa000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:431 errors:0 dropped:0 overruns:0 frame:0 TX packets:431 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:35294 (34.4 Kb) TX bytes:35294 (34.4 Kb)
steve, Can't reproduce it, which mode do you use 'ifup' or 'NetworkManager'? And what's your change for eth0? Thanks!
Standard 12.1 install had traditional method with ifup set. The 1st. change I made was to add a static IP address. Caused the problem. The second change I made was to the gateway address, caused the problem. I think driver support for the device is new, so not sure if the problem is there.
The same problem: http://forums.opensuse.org/english/get-technical-help-here/network-internet/468061-opensuse-12-1-eth0-starts-ifup-eth0-but-not-service-network-restart-2.html
*** Bug 731756 has been marked as a duplicate of this bug. ***
This is the X-Systemd-RemainAfterExit issue, fixed: * Mi Jan 04 2012 mt@suse.com - Added X-Systemd-RemainAfterExit: true LSB header (bnc#727771) Please install all updates, especially sysconfig and systemd: $ rpm -q sysconfig systemd sysconfig-0.75.4-2.7.1.x86_64 systemd-37-3.151.1.x86_64 $ rpm -q --changelog systemd | head -1 * Do Feb 09 2012 fcrozat@suse.com $ rpm -q --changelog sysconfig | head -1 * Mi Feb 29 2012 mt@suse.com *** This bug has been marked as a duplicate of bug 727771 ***