Network devices become inactive over a period of time

[CauticaL]

I have a machine running Fedora 9 which requires multiple LAN IP addresses. From time to time, eth0:1, eth0:2, etc. will become inactive and the daemons which bind to those addresses can no longer respond or communicate with the rest of the LAN.

I'm wondering how I can ensure that these stay active permanently. The machine runs 24/7/365.

[ivancat]

if you have a dynamic IP then you're most likely to get disconnects from time to time

[briantan]

Are you running NetworkManager?

[CauticaL]

Originally Posted by briantan

Are you running NetworkManager?

Yes, via gnome. Static addresses all the way through.

[briantan]

You could toy with NM_CONTROLLED=no for the alias interfaces.

EDIT: edit /etc/sysconfig/network-scripts/ifcfg-eth0:1 and change the variable.

[CauticaL]

Originally Posted by briantan

You could toy with NM_CONTROLLED=no for the alias interfaces.

EDIT: edit /etc/sysconfig/network-scripts/ifcfg-eth0:1 and change the variable.

# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
GATEWAY=192.168.1.1
TYPE=Ethernet
DNS1=205.152.132.23
DEVICE=eth0:1
BOOTPROTO=none
NETMASK=255.255.255.0
IPADDR=192.168.1.51
DNS2=205.152.37.23
USERCTL=no
PEERDNS=yes
IPV6INIT=no

Hmm, The others eth0:2, etc. are pretty much the same. Where can I find NM_CONTROLLED have any ideas where to find the docs? I've noticed they seem to turn off leaving just eth0 on, this usually happens 12 hours or so.

[stevea]

First off editing the files in /etc/sysconfig is a BAD IDEA(tm) If you mess up the syntax your service is mysteriously broken, or an upgrade to the service may not accept your change. Always use system-config-network to manipulate /etc/sysconfig/network-scripts/ifcfg-*

Next - I would not recommend NM(networkmanager) for a stand alone server. You must be logged in for NM to start and it can somewhat unpredictably select it's preferred interface.

Your statement that you are static assignment and NM is wrong. NM requires the use of dhcp service for IP assignent - no exceptions yet.

NM (since F7 at least) does not cause any surprising disabling of interface, but it does revise all the interfaces if there is a change in interface status (connection lost/made) or if the dhcp lease expires.

--

Braintan's advise is not so good.

I suggest that you disable and stop the Networkmanager service (use system-config-services).
That's probably all you need.

DO examine all the settings through system-config-network and make sure they look correct.

[briantan]

Originally Posted by CauticaL

Hmm, The others eth0:2, etc. are pretty much the same. Where can I find NM_CONTROLLED have any ideas where to find the docs? I've noticed they seem to turn off leaving just eth0 on, this usually happens 12 hours or so.

Just add NM_CONTROLLED=no in the ifcfg-eth0:1 and ifcfg-eth0:2 so on. NetworkManager will leave them alone.

EDIT: If you are not running NM, no harm done in adding NM_CONTROLLED variable. See my next post.

# Stevea:
I am running F8 and F9 servers with static IPs, with NetworkManager and init level 3. Your statement about login to run NM is wrong *. I don't use gui config as they are quite limited in functionality.

NM does work with both DHCP and static IP.

EDIT: * NM is run as a service.

[briantan]

Originally Posted by CauticaL

# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
GATEWAY=192.168.1.1
TYPE=Ethernet
DNS1=205.152.132.23
DEVICE=eth0:1
BOOTPROTO=none
NETMASK=255.255.255.0
IPADDR=192.168.1.51
DNS2=205.152.37.23
USERCTL=no
PEERDNS=yes
IPV6INIT=no

You should also change BOOTPROTO to static and add ONBOOT=yes for your alias interfaces.

BOOTPROTO=static
ONBOOT=yes