Bug 134170

Summary:	NetworkManager shuts down eth0
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Juergen Weigert <jw>
Component:	GNOME	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	joop.boonen
Version:	Alpha 3
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Juergen Weigert 2005-11-17 13:20:31 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

Comment 1 Juergen Weigert 2005-11-17 15:52:38 UTC

Coolo suggets to involve rml.

Comment 2 Robert Love 2005-11-17 17:06:38 UTC

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?

Comment 3 Timo Hoenig 2005-11-17 17:19:21 UTC

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.

Comment 4 Juergen Weigert 2005-11-17 18:13:15 UTC

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.

Comment 5 Timo Hoenig 2005-11-17 18:20:48 UTC

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!

Comment 6 Juergen Weigert 2005-11-17 18:26:33 UTC

Oh, rcypbind start fails with 'No domainname set' when eth0 is managed.
I'll fall back to dhcp for now.

Comment 7 Juergen Weigert 2005-11-17 18:27:21 UTC

still not a usable replacement for dhcp.

Comment 8 Timo Hoenig 2005-11-17 19:46:58 UTC

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 :/

Comment 9 Timo Hoenig 2005-11-17 19:58:56 UTC

Closing as duplicate of #134160.

*** This bug has been marked as a duplicate of 134160 ***

Comment 10 Martin Vidner 2005-11-18 15:35:24 UTC

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.

Comment 11 Juergen Weigert 2005-11-18 15:51:50 UTC

Yes, sorry, typo. thanks Martin. Switching off managed could leave the interface in an unconfigured state. Why not...

Comment 12 Timo Hoenig 2005-11-30 12:32:06 UTC

*** Bug 135754 has been marked as a duplicate of this bug. ***