From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5 Description of problem: Bad: The NM doesnt detect my network. Though i can still browse and use the internet, the NM shows that the computer is 'not connected' If i do a service network restart, I get the following message Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0...dhclient(5468) is already running - exiting. This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution. Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com exiting. failed. Version-Release number of selected component (if applicable): 2.6.25.3-18.fc9.i686 How reproducible: Sometimes Steps to Reproduce: 1. In the networkManager the Enable Network should be ticked 2. as root "service network restart" 3. Actual Results: Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for eth0...dhclient(5468) is already running - exiting. This version of ISC DHCP is based on the release available on ftp.isc.org. Features have been added and other changes have been made to the base software release in order to make it work better with this distribution. Please report for this software via the Red Hat Bugzilla site: http://bugzilla.redhat.com exiting. failed. The NM then comes to life and shows that the network is connected. Expected Results: I have no idea Additional info:
Could you try installing these testing packages? They are known to fix some situations where NM would not detect a wired network device. http://koji.fedoraproject.org/koji/buildinfo?buildID=51684 Thanks!
Hi, Tried the solution you mentioned. But to no avail. It still NM still doesnt detect my wired connection. Moreover, till the NM doesnt detect the wired connection PackageKit also doesnt work. It says that I am "offline" But yum works from command line. Thanks for the reply (In reply to comment #1) > Could you try installing these testing packages? They are known to fix some > situations where NM would not detect a wired network device. > > http://koji.fedoraproject.org/koji/buildinfo?buildID=51684 > > > Thanks! >
Could you restart your system and include the output of /var/log/messages by attaching it to this bug report? Thanks! That'll give me a clue as to what might be going on.
Created attachment 308739 [details] the /var/log/messages after restart I guess this is it
One more thing. Now if i do anything with the network settings, the machine simply reboots!! Its really irritating
Jun 9 23:46:14 homebaner nm-system-settings: ifcfg-fedora: read connection 'System eth0' Jun 9 23:46:14 homebaner nm-system-settings: ifcfg-fedora: Ignoring connection 'ifcfg-eth0' and its device because NM_CONTROLLED was false. Jun 9 23:46:14 homebaner NetworkManager: <info> (eth0): now unmanaged so you've told NM to ignore the eth0 device. You can make NM control the device by either editing /etc/sysconfig/network-scripts/ifcfg-eth0 and changing the NM_CONTROLLED=no to NM_CONTROLLED=yes, or you can check the "Controlled by NetworkManager" box in system-config-network. Let me know if either of these work!
Hi, I did as you said. Now the NM works. But i still have to disable and enable it by hand everytime i log in. Other than this extremely minor irritation, this seems to have solved the problem. thanks
Hi, Now i have changed the /etc/sysconfig/network-scripts/ifcfg-eth0, the NM works. But i have a VPN which i use to connect to the university. I am able to authenticate with that connection, but cannot use it when i activate it with the NM. If i activate it without NM (manually) then i am able to use it without problems. regards --sameet
Which VPN type is this? OpenVPN, IPSec (openswan), or vpnc?
Does this bug still effect the reporter? If so, can you please provide info requested by Dan?
Reporter, could you please reply to the previous question (In reply to comment #9)? 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 https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days