After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 503129 - N-M should store its state on the system so that wifi works at bootup
N-M should store its state on the system so that wifi works at bootup
Status: RESOLVED DUPLICATE of bug 331529
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2007-12-11 21:30 UTC by Alexander “weej” Jones
Modified: 2007-12-28 22:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alexander “weej” Jones 2007-12-11 21:30:56 UTC 
Since switching to wifi in my house, I have to get a user to log on and make N-M connect to the network in order for our "home server" to work.

This is basically unusable, so I've resorted to not using network manager at all. As a result, I don't get the benefits of N-M's VPN functionality.

It seems to be a questionable design choice to harass whoever is the first person to log on for a network password. If the network connection could be considered to be owned solely by a specific user, then this might make sense, but once I have authenticated to the network - ANYONE using the same machine can use the connection! Few people would want it any other way.

Also, this poses a problem whereby if I can't log on to GNOME for whatever reason, I am stuck without a network connection.

I need my network services to be available as soon as possible, and there's no way to do this with N-M right now.

Thanks!
Comment 1 Martin Dengler 2007-12-15 02:20:23 UTC 
This looks like a dupe of bug http://bugzilla.gnome.org/show_bug.cgi?id=331529
Comment 2 Christopher Aillon 2007-12-28 22:53:49 UTC 
Yeah.  What you describe is the goal we're working towards.  NM was initially designed to do one thing well and that was to get a user who might not know how to run ifconfig, etc. up and running on a network.  This is a little more complicated and support wasn't written for it yet, but it's being worked on heavily now.  Stay tuned.

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