Red Hat Bugzilla – Bug 492812
NM defaults to wireless networks even when plugged in to wired network
Last modified: 2009-11-19 18:58:40 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Connect to wired network
2. Restart computer
3. See that NM has connected to wireless network
NetworkManager always connects to wireless network, even when wired network interface is plugged in
Wired network interface by default, select wireless network if wired net is not available
It's even worse: if there is no wireless network, NetworkManager just doesn't connect at all. In case it matters, I'm running F11Beta as a VMware client.
What's the output of 'nm-tool' when the cable is plugged in? If this is running inside a VM, the VM's network device may not support carrier detection, and thus the wired device won't automatically get used.
I cannot currently reproduce the problem. I had disabled NetworkManager and enabled the network service, so now to test out nm-tool I had to undo those changes. But now, NetworkManager does start up the eth0 (wired) connection after I reboot and log in (logging in is done automatically--it's a private VM only used for testing).
Anyway, nm-tool does say (among other things) Carrier Detect: yes.
Reporter, could you please reply to the previous question (comment #2)? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Fedora Bugzappers volunteer triage team
Created attachment 339184 [details]
Output of nm-tool command
Sorry for the delayed response.
Attached is the output of nm-tool after a cold boot with the computer plugged in to the wired network and in range of my preferred wireless network. NetworkManager connected to the wireless network, and eth0 remained disconnected.
After looking at the output of this file, I noted that there was no entry for "auto eth0" under "Edit Connections" through the nm-applet. I manually created an auto-connect entry for eth0, and rebooted. This time, the wired connection was brought up upon boot. Also, now if I disconnect the ethernet cable and (after seeing the wireless connection come up) reconnect it, NM defaults back to the wired connection.
So it appears the nature of the problem was that NM was not creating an "auto eth0" entry.
Also, forgot to mention this - I am running F11 Beta native, not in a VM.
My experience (comment #3) also points in the direction of comment #5. After I had switched off NM to get an automatic connection, I switched it back on to answer the question in comment #2. I had to check the box in system-config-network to indicate that NM had to control eth0 (I may have switched that off when switching to the network service, I don't remember) and after that NM worked.
So the problem seems that NM doesn't work "out of the box" for wired ethernet, but it does seem to work when configured properly.
If you've installed from DVD or CD (ie, not a network install), then your ethernet device will not be enabled by default. Please check your /etc/sysconfig/network-scripts/ifcfg-eth0 file and look for "ONBOOT=no". If that is present, then you likely did a DVD or CD install, and anaconda will then not mark your network device for autoconnection.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
Just to confirm, do you happen to remember if you installed from the DVD or CD?
I installed from the DVD.
Yeah, then this is expected. It's more of an installation process issue and not really an NM issue.
*** This bug has been marked as a duplicate of bug 494240 ***