|
Bugzilla – Full Text Bug Listing |
| Summary: | NetworkManager uses static ip adress previously set by yast | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Jakub Friedl <jfriedl> |
| Component: | Network | Assignee: | Robert Love <rml> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | mvidner |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jakub Friedl
2006-01-26 13:37:58 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. 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. Except that Timo points out we are in string freeze ... 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. (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. 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. |