Bug 145825 - NetworkManager uses static ip adress previously set by yast
Summary: NetworkManager uses static ip adress previously set by yast
Status: RESOLVED INVALID
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Beta 1
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Robert Love
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-26 13:37 UTC by Jakub Friedl
Modified: 2006-02-07 16:15 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jakub Friedl 2006-01-26 13:37:58 UTC 
NetworkManager uses static ip address set in YaST even after the netework is set to be managed by NetworkManager in Yast. Deleting the static configuration solves the problem.
Comment 1 Martin Vidner 2006-02-07 15:59:19 UTC 
It is intentional that NM uses the static setup from an ifcfg. But indeed the UI does not make it apparent.

One part of the solution is to show the network setup even if using NM (see bug 148485 for that).

Also, the applets should indicate that the setup is coming from an ifcfg (and perhaps offer an option to run yast to change it). -> reassigning to applet maintainers to comment.
Comment 2 Robert Love 2006-02-07 16:05:10 UTC 
I don't think that NM's UI necessarily needs to change to reflect a static setup, since the default ifcfg settings are automatic.

But it might be a nice idea to add a "Configure Network" option, which invoked YaSt.
Comment 3 Robert Love 2006-02-07 16:09:53 UTC 
Except that Timo points out we are in string freeze ...
Comment 4 Martin Vidner 2006-02-07 16:10:14 UTC 
I mean that the Connection information box should indicate that an ifcfg is in use. And the configure option need not be there always (to keep it simple) but only in the ifcfg case.
Comment 5 Martin Vidner 2006-02-07 16:12:14 UTC 
(In reply to comment #3)
> Except that Timo points out we are in string freeze ...
Right. Feel free to postpone if you do not have suitable strings already.
Comment 6 Robert Love 2006-02-07 16:15:05 UTC 
Alright.  I will mark this has notabug (since using the YaSt information is intended).

Let's revisit as a feature request for a future product.