Bug 171798

Summary:	support establishing network connection upon boot
Product:	[Fedora] Fedora	Reporter:	Myk Melez <myk>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	eric.brunet, quintesse, redhat
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-12 14:41:03 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Myk Melez 2005-10-26 16:06:29 UTC

NetworkManager doesn't establish a network connection until a user logs in, but
services started on boot like ntpd and sshd have legitimate uses for a network
connection upon start.  NetworkManager should store network connection
configuration in a user-neutral location by default or when requested to do so
by the user and connect to a user-neutral network connection on boot when one is
available.

Comment 1 W. Michael Petullo 2005-11-22 01:11:23 UTC

I am interested in the same functionality.

However, I have what seems to be a catch-22.  NetworkManager requires dbus. 
Dbus seems to make LDAP requests when LDAP is used for NSS (for /etc/hosts?) 
These requests hang if the network is not available.

So, which starts first: dbus or NetworkManager?

I am using dbus-0.50-1, NetworkManager-0.5.1-4 and glibc-2.3.90-18.

Because of this, I have had to use netplugd to manage my network device.

Comment 2 Douglas Furlong 2006-02-09 09:46:02 UTC

What happens in casses when there isn't a "user neutral" option?

I would personally be more interested in a method, that allowed network services
to detect that the network is not up, and as such not attempt to load.

Comment 3 quintesse 2006-03-03 21:54:57 UTC

If there isn't a "user neutral" option those services should be made smarter,
but that's an entirely different set of problems.

What is described here is that there _is_ a network out there, NM just won't
connect to it until somebody logs in.  There should be an option saying: if
network X is available, this is the key for it, use it!

We've got several wireless machines in this house and 90% of the time they will
be used here and nowhere else, having to log in to get them conencted is a nuisance.

Comment 4 Dan Williams 2008-02-12 14:41:03 UTC


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