Bug 134054 - Networkmanager: if on ifplugd nameresolution fails
Summary: Networkmanager: if on ifplugd nameresolution fails
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Network (show other bugs)
Version: Alpha 3
Hardware: Other Other
: P5 - None : Critical (vote)
Target Milestone: ---
Assignee: Martin Vidner
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-16 20:01 UTC by Danny Al-Gaaf
Modified: 2006-01-06 08:56 UTC (History)
2 users (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 Danny Al-Gaaf 2005-11-16 20:01:14 UTC 
On a fresh installed Alpha 3: I set Networkmanagement to ifplugd with yast and rebooted the machine.

If you set to ifplugd the Networkmanager is already started. Because of this I lost permanently the nameresolution. I set this again in yast to ifplugd and restarted all services and it worked some seconds perfect. Then again the same problem. First as I stopped the NetworkManager all work as expected.

If the network is managed by ifplugd the NetworkManager should not do anything in the system. The best: if use ifplugd, remove NetworkManager from init process.
Comment 1 Timo Hoenig 2005-11-17 11:23:04 UTC 
Actually, if you switch to ifplugd, YaST should make sure that NetworkManager is stopped.  I do not think that we need to change NetworkManager to check whether a device is set to "managed" or not.  NetworkManager simply should not run if devices are to be managed by something else but NetworkManager.
Comment 2 Christoph Thiel 2005-12-01 20:47:49 UTC 
So, it looks like this need to be solved in YaST?
Comment 3 Timo Hoenig 2005-12-02 08:34:42 UTC 
Yes, partly.  We're in discussion on how to get the who-does-network-management issue solved in a proper way.
Comment 4 JP Rosevear 2005-12-21 13:30:50 UTC 
I believe this is at least partially done now.
Comment 5 Dr. Werner Fink 2005-12-21 13:44:33 UTC 
You believe this only?  If the bug is fixed then please close it,
if the bug is partly solved only please reassign it the appropiate
maintainer which is not the default maintainer but the person
familiar with NetworkManager and the problems with this tool.
Comment 6 JP Rosevear 2006-01-05 15:54:58 UTC 
Let me re-assign to the yast team then.
Comment 7 Ladislav Slezák 2006-01-06 08:05:58 UTC 
Martin, another NetworkManager related problem...
Comment 8 Martin Vidner 2006-01-06 08:56:06 UTC 
YaST now uses either rcnetwork or rcnetworkmanager, since Alpha 4 IIRC.