|
Bugzilla – Full Text Bug Listing |
| Summary: | NetworkManager seems useful but very hard to drive | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Jon Nelson <jnelson-suse> |
| Component: | Network | Assignee: | Robert Love <rml> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | lunar_raven, suse-beta |
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jon Nelson
2006-02-19 16:59:43 UTC
I agree, it is a bit confusing. You can actually configure it with the old interface, and then turn on network manager. However, that does make NetworkManager seem a little insignificant. I'd like to see a 'configure network card' option when right clicking on the NetworkManager applet, or something. AFAIK NetworkManager was mainly intended for the use of Wireless-devices. I'll redirect this to the maintainer for a comment. NetworkManager obeys the individual interface settings in /etc/sysconfig/network and several of the global settings. The difficulty to setup was the result of yast bug. It now allows you to configure whether you choose ifup or NM networking. As JP said, static IP configurations are configured under YaST. In later builds this should be more intuitive. If not, please file a _specific_ bug under the YaST component. Second, NM does offer a lot of other configuration. It is meant to "just work", although it does obey a handful of the settings under /etc/sysconfig/network. Finally, NM does not use ifplugd. It does its own carrier detection. You need to just let NM do its thing -- if you want to tweak dhcp and ifplugd and such, you don't want NetworkManager. Closing. |