Fedora 10 x86/64 shuts the eth interfaces after reboot

[tictac]

Hello,

I've got a problem, the interfaces are shutted by the system, so after the reboot I have no network conectivity even if I used the setup command to configure the interfaces.

Is this a bug or somethig?Am I the only one who has this problem?

[tictac]

I've altered the following config files with "ONBOOT=yes" with no result.

/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/networking/devices/ifcfg-eth0
/etc/sysconfig/networking/profiles/default/ifcfg-eth0

I wonder what is happening.

[johno12345]

I've seen similar issues,

I installed a system with gnome accidentally, so i removed x and gnome set the system to boot to init level 3. this knocked out my network settings completely and i had to ifup eth0 on every reboot.

i found adding the onboot=yes fixed my problem however.

I think my issue was to do with network-manager maybe have a look at that?

[tictac]

Well, I did a ifconfig eth0 up in my /etc/rc.local temporary.

I didn't use network-manager, I used setup command...

[tictac]

Any ideas, please? It's not a good idea to keep script in rc.local in production environments...

[tictac]

Am I the only one with this problem?

[andyvy]

I'm seeing the same exact problem, after reboot network is down. I just click on the network icon in gnome, and click on eth0 and it activates it in a split second.

It's hardly an annoyance since I restart my PC once a year or something. I'll look at it when I get home, if i find a fix I'll post.

[Sauron]

post the output of:

chkconfig | grep etwork

I bet network and network-manager are both off in all runlevels. Make sure network is on in at least runlevels 3 and 5.

[tictac]

chkconfig | grep etwork
NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off
network 0:off 1:off 2:off 3:off 4:off 5:off 6:off

Sauron, you're right. But shouldn't the network be enable by default in init 3?

[Sauron]

The problem is that you're looking at configuration files for "network" and the system is launching "networkmanager". Well, ok, maybe not fully that, but still. Set up /etc/sysconfig/network-scripts/ifcfg-eth0 and make sure "nm_controlled"=no.

Then disable "networkmanager", enable "network" in 3 and 5 and it'll fix that problem.

The other thing is that you're looking at level 3 as the default init, it's not - level 3 is no X, level 5 is full X boot. You want network (not networkmanager) launched in 3 and 5 and you'll be fine.

[marko]

Or use the actual gui tool system-config-network
which makes these mistakes less likely by putting all the check boxes and stuff in front of you
(that is, the "controlled my networkmanager" check box is also there on the Edit page for the interface
so it reminds you there's that relationship)

[dhimes]

I think I have this problem too. I can't get the gui up because I can't get the drivers because I can't get the network. I ping any ip address and I get "network is unreachable." Trying to disable networkmanager from the cmd line.

[dhimes]

disabled NetworkManager and enabled network and still no joy reaching network (ping fails).

[marko]

I think I have this problem too. I can't get the gui up because I can't get the drivers because I can't get the network. I ping any ip address and I get "network is unreachable." Trying to disable networkmanager from the cmd line.

Disabling NM from the command line:
either run

system-config-services

and use it to stop it (and disable it starting at boot if you like)
or run

service NetworkManager stop

it's also pretty easy to manual start up a connection that's down if that interface was configured already:

ifup eth0

if for some reason ifup doesn't work (like you don't have the ifcfg-eth0 file setup, you can do:

ifconfig eth0 IPADDRESS netmask 255.255.255.0
route add default gw GATEWAYIP

you'll have to type in your LAN's gateway and local host addresses for the two I have in caps

if necessary edit your /etc/resolv.conf to add a dns server:

nameserver 208.67.222.222

(208.67.222.222 is a public "opendns" DNS )

UPDATE: also, if you just have a NetworkManager problem, you can switch to the basic network service, it can do static and dhcp setups. The only reason NetworkManager exists is that it handles dynamic connects better than network (like a netbook going to work, net cafes, etc all with different network parameters)

[dhimes]

wooo hooo! (w00t!) my ping works now! I'm working through a router so if somebody comes along behind me I used IPADDRESS = 192.168.1.101 and GATEWAYIP = 192.168.1.100

Thanks, Marko! I'll see if I can get the repo updates to get me out of this mess!