Description of problem: Version-Release number of selected component (if applicable): How reproducible: Ever Steps to Reproduce: 1. Install 2. Boot 3. Actual results: Ethernet does not start at boot time Expected results: Ethernet starting Additional info: Computer has two ethernet cards. It does not use DHCP. I don't use NetworkManager. It is possible I made a mistake at install time since I found 192.168.0.2 (ie the adress of my DNS) as the mask value in the config file. Anyway after fixing it in the system-config-network the ethernet still does not start at boot time or when I do a /etc/init.d/network restart. I checked the config file with an aditor and the onboot flag was to yes. Tried by disabling the NetworkManager service still does not work. Bug is critical at just two weeks of release.
What happens when you do /etc/init.d/network restart? Note that you'll have to specifically enable the network service with chkconfig to have it start on boot.
When I submitted the bug it did nothing. In fact it stopped the ethernet I had started manually and didn't restart it. After today's updates and the enabling of networking the problem has disappeared. It is a bizarre decison after 14 years of enabling networking by default that RedHat/Fedora has dedided to no longer do it. In fact from a usability viewpoint it is a bug since many users will be surprised by the new behavior.
Do you have NetworkManager installed?
Yes it is I did a default install.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Please attach your ifcfg files, and the output of: chkconfig --list network chkconfig --list NetworkManager This looks like a duplicate of 467946.
Is this still an issue for the reporter? If so, can you please provide the info Bill has requested.
Problem is not present in the definitive release. You may close the bug.