Bug 428532

Summary: NetworkManager cannot handle static IP connection
Product: [Fedora] Fedora Reporter: Pavel Šefránek <pavel>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 8CC: dcbw, djuran, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-01 21:35:00 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 Pavel Šefránek 2008-01-12 22:32:25 UTC
NetworkManager included in F8 is unsuable, because it cannot handle my static IP
connection. It absolutely ignore all that /etc/sysconfig/net* scripts and trying
a long time to obtain wrong settings.

In F7 it works with no problem.

With this strange behavior of 0.7.0 NM makes no sense.

Comment 1 Pavel Šefránek 2008-02-01 20:51:38 UTC
Any updates Dan?

Comment 2 Dan Williams 2008-02-01 21:26:31 UTC
The system settings daemon works already for those configurations that ifcfg-*
files support (ie, Ethernet and unencrypted/WEP Wifi).  Since ifcfg-* files
don't support WPA yet (working on that now...) we can't do WPA before login yet.
 The applet bits are mostly done, needed to intelligently display all available
connections (both system and user) and allow the user to choose between them. 
Have to set up the D-Bus service activation stuff for the system settings daemon
and get NM to service activate it too.  Mostly cleanups, the heavy lifting is done.

I hope to land some stuff in Rawhide early next week.

Beyond the system settings daemon, static IP should already Just Work if you
have set up the right bits in GConf.  The connection editor that would allow you
to set up static IP without the system settings daemon isn't quite there yet.

Comment 3 Dan Williams 2008-02-01 21:35:00 UTC

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