Description of problem: My wired network disconnected. I used the Network Configuration app to reconnect. The applet in the menu bar shows an "x" and hovering over it displays a tooltip saying "No network connection" but the network is connected, Firefox can show pages, etc. Version-Release number of selected component (if applicable): NetworkManagerApplet 0.7.1 How reproducible: Happens after network disconnect. Steps to Reproduce: 1. Boot Linux 2. Wait till you get disconnected. 3. Use Network Configuration to reconnect. Actual results: Menus show "wired network" in dark gray, "device not managed" in light gray, a line, and VPN connections in black. Not using VPN or wireless, just plain old DHCP over Ethernet.
Thanks for filling this bug. If I understand you correct, you don't use NM to configure your network? If so, then NM has no change to detect if we have a carrier on the wire ore not. If you use NM, and still got the "No network connection" message, than please so kind to provide your /var/log/messages and the output of nm-tool. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 355027 [details] tarfile with /var/log/messages and output of nm-tool
So many other things worked smoothly in the f10->f11 upgrade that I thought network connection would also be taken care of automatically. I believe I am using Network Manager: Invoking Menu:System:Admin:Services brings up the Service Configuration window. Network Manager is the first item. It is marked as "enabled" and "running." After upgrading to F11, I see a new icon on the top bar with an x in it, that says "device not managed." Bringing up "edit connections" gets a tabbed window, with all panes empty. Clicking "add" on the "Wired" pane gets a window named "Wired connection 1" with a space for a MAC address. I don't know what to put there. I have attached the output of nm-tool and a copy of /var/log/messages. I trimmed out thousands of the repeated error messages described in bug 513455. Thanks for your attention to this bug.
I found a message in fedora-forums titled 'Wired network card "unmanaged"'. I started system-config-network and clicked "edit" on eth0. I checked "Controlled by Network Manager" and unchecked "activate when computer starts" and rebooted. Network Manager Applet could then see eth0 and I could click it to connect. Furthermore I could edit the connection to request that it connect at every startup. Rebooted again and it worked. This change in system behavior from Fedora 10 should be explained in the Common F11 Bugs file, in section 7.1. Right after the paragraph "The required procedure from this point is to click the NetworkManager icon, and activate the System eth0 or similar connection. If the red X disappears from the NetworkManager icon, then this was the issue that was stopping the connection from being activated." another should be added, e.g. 'If NetworkManager shows only a "device unmanaged," then start Menu:System:administration:Network", highlight the network atapter, click "Edit", and check "Controlled by Network Manager" and uncheck "activate when computer starts", and reboot. After reboot, the network adapter should appear when the NetworkManager icon is clicked, and the chosen adapter should start automatically at boot.' Thanks for looking into this.
i have similar problem. I am using bridges for virtual machines and i needed to turn off network manager for eth0. my /etc/sysconfig/networking/devices says: ---------------------------- # Networking Interface DEVICE=eth0 HWADDR=xx:xx:xx:xx:xx:xx ONBOOT=yes BRIDGE=br0 NM_CONTROLLED=no ---------------------------- I would love to use NM for wireless networks and maybe for VPNs. Another related problem is that firefox is somehow (probably using NM status) detecting we are offline and is switching to offline mode when its started, even if the network is working well.
What we want here is better ifup/ifdown coordination. *** This bug has been marked as a duplicate of bug 523064 ***