Red Hat Bugzilla – Bug 454381
nm-applet always chooses "Auto eth0", regardless of nm-connection-editor settings
Last modified: 2009-03-03 15:49:34 EST
Description of problem:
Summary pretty much says it all. I have configured 1 wired connection and 1
wireless connection using "nm-connection-editor". However, on every boot,
nm-applet decides that it knows best and creates an "Auto eth0" which --
unsurprisingly -- doesn't do what I want (it gets the DNS search paths in
/etc/resolv.conf incorrect amongst other things).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run, nm-connection-editor or (nm-applet->right click->edit connections) as
a non-privileged user and set up some connections.
2. Ensure that the connections have the "connect automatically" box ticked.
Aside: took me a while to realize that the connections you create when running
nm-connection-editor as root are *not* the ones nm-applet will use - it appears
to *only* use the users configured connections.
NM creates an "Auto eth0" connection using dhcp, ignoring the 2 connections I
have created and actually want it to use.
NM should use my connections basically.
# /sbin/chkconfig --list|egrep -i "network"
NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off
network 0:off 1:off 2:off 3:off 4:off 5:off 6:off
Please see bug 454368 for some weirdness that seems related to the problem
This problem also exists in Fedora 10, NetworkManager-0.7.0-0.11.svn4229.fc10.
I have a laptop with both wired and wireless interfaces. Using the NetworkManager applet I edit the eth0 interface to use "Automatic addresses only" on the IPv4 tab. I provide addresses for DNS servers and some search domains. I do likewise for the wireless interface. The settings are remembered when I log out and back in, when I suspend and resume, when I restart the NetworkManager service but not when I reboot the system. After a reboot the wireless settings remain but the settings for eth0 return to the fully automatic setting.
This makes it difficult to configure local dns caching and/or OpenDNS.
Yes I am facing a similar issue. I have a desktop machine with F10 installed. And NetworkManager is at version
I created a wired network connection with static IP and switched to it but as soon as I logout and log back in NetworkManager chooses the 'System eth0' connection which defaults to DHCP (which I don't want to use for this particular system).
I went desperate enough to make this work but finally saw that I can't delete the network connection 'System eth0' from the connection editor.
Also note that my custom created connection in the editor is also set to connect to it automatically.
On my system the behavior has changed with the update to NetworkManager version 0.7.0-0.12-svn4326.fc10 from version 0.7.0-0.11-svn4229.fc10. Previously, as described above, it was possible to "edit" the Auto eth0 connection in the NetworkManager Applet. This is no longer the case, everything for Auto eth0 is now grayed out. Not sure if this change is due to something new in the newer version of NetworkManager or maybe the old behavior that I observed was related to the fact that my system was originally built with Fedora 10 Release Candidate and then upgraded to the final version.
I found a solution. As root run system-config-network (or launch it via the menu option "System>Administration>Network"). Edit eth0, on the General tab check the option "Controlled by NetworkManager". Save the change. Reboot (I'm not sure if that's really necessary.) When you log back in to the system, eth0 will not be connected. Right click on the NetworkManager applet and select Edit Connections. Add a new connection, configure it as needed for your requirements (note you do not have to supply a MAC address). After you save the new connection and Close the Network Connections window, NetworkManager should attempt to use the new connection. The new connection should persist after a system reboot.
I can confirm this behavior on Fedora 10. NetworkManager ignore user created connections and defaults to Auto Eth0 on boot.
Dupe-ing since the fix for bug 485555 will make the operation of the "Auto eth0" connection clearer, though it won't make NM magically start controlling connections where NM_CONTROLLED=no.
*** This bug has been marked as a duplicate of bug 485555 ***