Network not up after reboot.

[vijay mohan a]

I have installed fedora core 9 and configures the ifcfg-eth0 script as below. my problem is the network is not coming up after reboot. after the reboot if i restart the network service(service network restart) network is coming up.

# Intel Corporation 82540EM Gigabit Ethernet Controller
DEVICE=eth0
BOOTPROTO=static
BROADCAST=1.1.1.255
HWADDR=00:0d:56:cf:a0:ca
IPADDR=1.1.1.9
IPV6ADDR=5555::9/64
IPV6INIT=yes
IPV6_AUTOCONF=no
NETMASK=255.255.255.0
NETWORK=1.1.1.0
ONBOOT=yes
DNS1=1.1.1.10
DNS2=192.168.111.249
NM_CONTROLLED=


configured
-------------
chkconfig network on
chkconfig NetworkMaager off


Could any one help me with this problem ?

[sideways]

You haven't defined a gateway
Do you really need ipv6?

and you should use 10.x.x.x or 192.168.x.x for internal ip addresses

[bob]

Looks like we may have a glitch. My network (eth0) did not auto-start either after the update. Checked 'system-config-network' and noticed that "Activate Device When Computer Starts" was unchecked.

Just double-checked after reboot - that fixes it. If we get others with the same error, might want to get Bugzilla involved.

Here's a partial list of yesterday's updates:

NetworkManager-glib-0.7.0.99-1.fc10 ...... Mon 09 Mar 2009 04:55:31 AM EDT
NetworkManager-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:55:36 AM EDT
NetworkManager-gnome-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:56:26 AM EDT
NetworkManager-openvpn-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:56:32 AM EDT
NetworkManager-vpnc-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:56:38 AM EDT

[vijay mohan a]

Hey BoB, i tried with "Activate Device When Computer Starts" option selected and chkconfig NetworkManager on. But no luck.

[Dinesh Sharma]

I had the same problem after updating the network manager. I am aware of the network problems with systems using fixed IP no.s, but this computer uses DHCP. I found that the DNS entries kept vanishing. Editing /etc/sysconfig/network-scripts/ifcfg-eth0 (with vim) did not help either. Then I noticed, like Bob, that the entry for "Activate Device When Computer Starts" was unchecked. Changing it has solved the problem for now -- touch wood.

I have been using Linux since the Soft Landing System (SLS) 0.4 (4 floppies N1-N4 for Networking!). I think fedora 10 is about the most annoying distribution I have ever come across.

I had recently convinced the family to make Linux the default boot for the home computer. Now I have a tough time explaining why Linux requires them to know the root password and to go mucking about in things like system-admin-network to reset nameserver addresses!

[Dinesh Sharma]

Originally Posted by vijay mohan a

Hey BoB, i tried with "Activate Device When Computer Starts" option selected and chkconfig NetworkManager on. But no luck.

Vijay: I hope you saved the new configuration. You may want to add the name server entries to etc/sysconfig/network-scripts/ifcfg-eth0 by old fashioned editing. The change is reflected automatically in some other hard linked files. Don't use emacs -- I have heard that it decouples hardlinked files.

[vijay mohan a]

solved the issue. i have unchecked "Controlled by NetworkManager" box. Now my config is as below

# Intel Corporation 82540EM Gigabit Ethernet Controller
DEVICE=eth0
BOOTPROTO=none
BROADCAST=1.1.1.255
HWADDR=00:0d:56:cf:a0:ca
IPADDR=1.1.1.9
IPV6ADDR=5555::9/64
IPV6INIT=yes
IPV6_AUTOCONF=no
NETMASK=255.255.255.0
NETWORK=1.1.1.0
ONBOOT=yes
DNS1=1.1.1.10
DNS2=192.168.101.111
NM_CONTROLLED=no <<<------ by disabling this every thing works fine.
TYPE=Ethernet
USERCTL=yes
PEERDNS=yes

NetworkManagerScreenShot
http://www.flickr.com/photos/3621528...49602/sizes/o/

[vijay mohan a]

Is this a BUG ? or am i missing something.

[John the train]

Originally Posted by bob

Looks like we may have a glitch. My network (eth0) did not auto-start either after the update. Checked 'system-config-network' and noticed that "Activate Device When Computer Starts" was unchecked.

Just double-checked after reboot - that fixes it. If we get others with the same error, might want to get Bugzilla involved.

Here's a partial list of yesterday's updates:

NetworkManager-glib-0.7.0.99-1.fc10 ...... Mon 09 Mar 2009 04:55:31 AM EDT
NetworkManager-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:55:36 AM EDT
NetworkManager-gnome-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:56:26 AM EDT
NetworkManager-openvpn-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:56:32 AM EDT
NetworkManager-vpnc-0.7.0.99-1.fc10 ..... Mon 09 Mar 2009 04:56:38 AM EDT

See the latest couple of posts in ' Who's the idiot...? ' I had the same problem, but fixed it like you Bob.I also had an SELinux denial report, was SELinux also updated or does it look as if the Network Manager updates caused a conflict?

[bob]

I'd long since disabled SELinux, but will be tied up for most of the day today. If anyone has the opportunity, could you get into Bugzilla and see if this is already filed? It should be reported.

[petermholmes]

Originally Posted by bob

If anyone has the opportunity, could you get into Bugzilla and see if this is already filed?

It's in there: https://bugzilla.redhat.com/show_bug.cgi?id=470467

[jaslar]

My wireless network keeps quitting on me, too (usually after a logout, but not shut down). A service network restart shuts DOWN an active connection, but doesn't bring it up again. When I look at the system-config-network, it says the wireless is inactive -- but there appears to be no way to MAKE it active within that application (is there?). Rebooting brings it up -- but why should I have to reboot a linux machine?

The interesting thing is that the panel network applet shows me OTHER wireless connection, but not the one within my own house.

I've just turned off the allow network manager, and just made it Activate device when computer starts. Wireless settings includes the hex password. Also switch it from Master to Managed.

[caf4926]

@bob

Looks like we may have a glitch. My network (eth0) did not auto-start either after the update. Checked 'system-config-network' and noticed that "Activate Device When Computer Starts" was unchecked.

Just double-checked after reboot - that fixes it. If we get others with the same error, might want to get Bugzilla involved.

This fixed it for me too.