Red Hat Bugzilla – Bug 155552
NetworkManager does not allow connecting to wired network
Last modified: 2007-11-30 17:11:04 EST
If I run network manager I am not allowed to choose the wired network from the
list. Only way to get NetworkManager to connect to the wired network is to
choose to stop all wireless devices by right clicking on the docklet. I think it
would be more natural to make wired network just another option.
Hmm, it should be an option. Is the menu item grayed out completely?
The only way it would be grayed out is if NetworkManager thinks the wired card
can do carrier detection, but it doesn't think any cable is plugged in. It uses
netlink sockets for its carrier detection messaging, so if the driver doesn't
support netif_carrier_on/netif_carrier_off(), then you're out of luck...
Can you post the output of "ethtool" and "mii-tool" for your wired card?
It is not greyed out. I tested some more today and if I connect the wired
network to the laptop is now automatically switch to that. But if I switch to a
wireless network then try to choose the 'Wired Network' at the top of the list
again nothing happens. (If I unconnect the ethernet then reconnect it again it
switches automatically over again.)
Output of requested tools below (when connected with ethernet cable)
[root@wildsrc ~]# ethtool eth0
Settings for eth0:
Supported ports: [ MII ]
Supported link modes: 10baseT/Half 10baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised auto-negotiation: Yes
Port: Twisted Pair
Current message level: 0x000000ff (255)
Link detected: yes
[root@wildsrc ~]# mii-tool eth0
eth0: negotiated 100baseTx-FD flow-control, link ok
Can you post the contents of /var/log/messages from right before you manually
choose "wired network" when you are currently on wireless?
(This is a mass update of bugs which have been in the NEEDINFO state unmodified
for over a year and have not been confirmed for a still supported version of
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.