Connection eth0 never active on boot

sauvagii · #1 16th July 2011, 09:28 PM

Hi,

I am trying to sort out some issues following an upgrade from F12.

I have eth0 as the connection I want to use. Prior to the upgrade, this connection was enabled and active at boot.

Now, for some reason after the upgrade it has to be manually enabled at every boot - even though when I go the Network tool, Ethernet Device > General tab - "Activate device when computer starts" is checked.

At every boot time it is inactive.

In all the ifcft-eth0 files, the ONBOOT parameter is set to "yes".

Can anyone advise?

marko · #2 16th July 2011, 09:40 PM

If you're using NetworkManager, then check the "Connect Automatically" check box by using your NetworkManager desktop widget.

In KDE you do that by selecting the widget (looks like some waves going up) in the lower right corner, left click it, pick "Manage Connections", select the right interface, hit "Edit..." and the "Connect Automatically" checkbox is clearly there. I think Gnome 3 has a similar widget in the upper right.

sauvagii · #3 16th July 2011, 11:18 PM

Unfortunately, that doesn't "stick" and no matter what on a reboot, the connection is back to inactive.

scott32746 · #4 16th July 2011, 11:43 PM

Hello,

try from command line
# chkconfig --list |grep etw

If using NetworkManager or network
one of them need to say on for level 3 and 5

# chkconfig --level 35 NetworkManager on

With you saying you have yes in ifup-eth0 I am thinking you want to use network

# chkconfig --level 35 network on

sauvagii · #5 17th July 2011, 12:29 AM

I've confirmed network is on at level 3 and 5 at boot.

But the eth0 adapter still starts in "inactive" state, and needs to be manually activated from Preferences > Network, despite being set to start at boot.

scott32746 · #6 17th July 2011, 12:55 AM

Hello,

Post output from

# cat /etc/sysconfig/network
# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# chkconfig --list |grep etw
# ifconfig

sauvagii · #7 17th July 2011, 01:08 AM

Results as requested below:

ifconfig - I have 3 network ports on my server, eth1 and eth2 are inactive in the same way that eth0 is - I don't want to use them, yet eth1+2 show in ifconfig results, but nothing for eth0?

Sorry - I'm a newbie to Linux networking and it's pretty confusing...!

[root@dl ~]# cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=dl.net

[root@dl ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
TYPE=Ethernet
DEVICE=eth0
IPV6INIT=no
USERCTL=yes
HWADDR=00:e0:81:32:3f:57
PREFIX0=24
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
NAME="System eth0"
UUID=5fb06bd0-0bb0-7ffb-45f1-d6edd65f3e03
PREFIX=24
IPADDR=192.168.1.76
NETMASK=255.255.255.0
GATEWAY=192.168.1.254
DNS1=192.168.1.76
DNS2=192.168.1.76
SEARCH=dl.net
DOMAIN=dl.net
BOOTPROTO=none
NM_CONTROLLED=no
ONBOOT=yes
# generated by hdactl on 2011-07-17 00:07:50 / 1

[root@dl ~]# chkconfig --list |grep etw
NetworkManager 0:off 1:off 2:off 3:on 4:off 5:on 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off

[root@dl ~]# ifconfig
eth1 Link encap:Ethernet HWaddr 00:E0:81:32:3F:56
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

eth2 Link encap:Ethernet HWaddr 00:E0:81:32:3E:F1
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:476 errors:0 dropped:0 overruns:0 frame:0
TX packets:476 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:36344 (35.4 KiB) TX bytes:36344 (35.4 KiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:18077 (17.6 KiB)

marko · #8 17th July 2011, 01:15 AM

Quote:

Originally Posted by sauvagii

[root@dl ~]# chkconfig --list |grep etw
NetworkManager 0:off 1:off 2:off 3:on 4:off 5:on 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off

I think that could be the problem, NetworkManager and network are mutually exclusive, you should just run one or the other. For a fixed server, you should run network and turn off NetworkManager:

Quote:

chkconfig NetworkManager off
service NetworkManager stop

sauvagii · #9 17th July 2011, 01:20 AM

So how do I permanently disable network manager?

this wasn't a problem before the upgrade so I must have screwed something up.

scott32746 · #10 17th July 2011, 01:18 AM

Need to turn off one of ether NetworkManager or network , do not need both running.
I think for hardware network is best, but that is me
# chkconfig NetworkManager off
# service NetworkManager stop

Also add to /etc/sysconfig/network
NETWORKING_IPV6=no
# echo "NETWORKING_IPV6=no" >> /etc/sysconfig/network

# reboot

scott32746 · #11 17th July 2011, 01:22 AM

# chkconfig NetworkManager off
This is going to permanently disable NetworkManager

sauvagii · #12 17th July 2011, 10:56 AM

Hi Scott,

I've tried making the changes you have listed but to no avail. Eth0 is still inactive on boot, and I need to manually activate it to be able to see the server on the network.

sauvagii · #13 18th July 2011, 03:40 PM

Still having this issue - anyone else have any thoughts?