https://bugzilla.novell.com/show_bug.cgi?id=806959
https://bugzilla.novell.com/show_bug.cgi?id=806959#c7
Marius Tomaschewski
I think this is a similar bug to bnc 807018.
Yes, I think so. In the meantime (most recent submission), yast2 is able to switch between NetworkManager and /etc/init.d/network, see also bnc#798348#c43.
Also the workaround is described here: https://www.suse.com/releasenotes/i386/openSUSE/12.3/RELEASE-NOTES.en.html#u...
Using "sudo /usr/sbin/NetworkManager" (comment 4) will not fix anything but may make it worser and cause that both, /etc/init.d/network and the NetworkManager are running and trying to apply different configurations at the same time. Instead use: # # 1) ensure it is stopped, whatever is running # systemctl stop network.service # # 2) enable NetworkManager. # This creates a network.service -> NetworkManager.service link, # which disables /etc/init.d/network and makes NM responsible. # systemctl --force enable NetworkManager.service # # 3) start NetworkManager.service (via its network.service link) # A "systemctl start NetworkManager.service" works here too. # systemctl start network.service Now _and_ after reboot, NetworkManager should be running. I'm resolving it as duplicate of bnc#798348 for now, but when the above manual "enable" doesn't help, please remove the duplicate flag. *** This bug has been marked as a duplicate of bug 798348 *** http://bugzilla.novell.com/show_bug.cgi?id=798348 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.