Bugzilla – Bug 134170
NetworkManager shuts down eth0
Last modified: 2005-11-30 12:32:06 UTC
Updated from 10.0 to alpha3. DHCP configuration. during boot, the network gets up, but disappears 15 seconds afterwards. rcnetwork restart gives me network for another 15 seconds. Apparently /usr/bin/NetworkManager is behaving erratic. yast network devices help says: Use 'Mananged by NetworkManager' to have a desktop applet to take care about the interface. I use a standard KDE desktop and cannot find such an applet. Yast does allow me to switch off 'Mananged by NetworkManager'. Tested Workaround: killall NetworkManager; rcnetwork restart
Coolo suggets to involve rml.
To use NM, all interfaces need to be set to manual. The observed behavior is erratic because NM and ifplugd and/or another dhcp client are fighting. I suppose the issue is that (a) in Alpha3 we need to default all interfaces to "manage" and (b) KDE should autostart the applet. Timo, do you know more?
Juergen, please set all devices to "managed" using YaST. This will ensure that ifup does not touch the interfaces at boot time and ignore them completely. We expect to have YaST setting the interfaces to "managed" by default for the next alpha of 10.1. While I am 24/7 on the implementation of a KDE applet for NetworkManager, I suggest using 'nm-applet' until this work is done. It should be installed by default and works quite well in the KDE environment.
Timo, that does not help. I've klicked managed in yast, now rcnetwork restart says "eth0 Startmode is 'managed' skipping" and the network remains down. Killing and restarting NetworkManager then connects me to the network. nm-applet says 'wired network connection' and allows me to view the connection info. Now it survives a reboot. thanks.
Having 'rcnetwork restart' skipping the devices is just fine. It ignores -the device(s) set to "managed". I'll close this bug. Please file reports if you encounter other bugs with NetworkManager. Thanks!
Oh, rcypbind start fails with 'No domainname set' when eth0 is managed. I'll fall back to dhcp for now.
still not a usable replacement for dhcp.
Hum. My last reply somehow got lost. Here I go again: The domainname issue is a known issue (see #134241). The only workaround I can offer is a pathetic 'domainname suse.de' followed by restarting ypbind and autofs. Sorry for that :/
Closing as duplicate of #134160. *** This bug has been marked as a duplicate of 134160 ***
Juergen, I assume that in comment 0 you meant "Yast does NOT allow me to switch off 'Mananged by NetworkManager'." That can be done by Editing the interface. One cannot simply switch it off because an originally unconfigured interface that was then managed and then non-managed would not have a valid configuration. I will enhance the help text.
Yes, sorry, typo. thanks Martin. Switching off managed could leave the interface in an unconfigured state. Why not...
*** Bug 135754 has been marked as a duplicate of this bug. ***