Using ifup to bring a new virtual interface (eth0:0) can in some case add a second 0.0.0.0 route which screw up the network.
*** Bug 11602 has been marked as a duplicate of this bug. ***
I disagree with the status of the bug resolution. I experience my problem with a redhat 6.2. The problem appear if the interface is not started a boot time but added by hand with "ifconfig eth0:0 up" later on. Configuration : DEVICE=eth0 BOOTPROTO=static BROADCAST=194.164.71.63 IPADDR=194.164.71.52 NETMASK=255.255.255.192 NETWORK=194.164.71.0 ONBOOT=yes DEVICE=eth0:0 BOOTPROTO=static BROADCAST=194.164.71.63 IPADDR=194.164.71.50 NETMASK=255.255.255.192 NETWORK=194.164.71.0 ONBOOT=no DEVICE=eth1 BOOTPROTO=static BROADCAST=192.168.0.255 IPADDR=192.168.0.1 NETMASK=255.255.255.0 NETWORK=192.168.0.0 ONBOOT=yes Before : Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 eth1 194.164.71.52 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 194.164.71.0 0.0.0.0 255.255.255.192 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 194.164.71.62 0.0.0.0 UG 0 0 0 eth0 ifup eth0:0 After: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 194.164.71.50 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 192.168.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 eth1 194.164.71.52 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 194.164.71.0 0.0.0.0 255.255.255.192 U 0 0 0 eth0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 194.164.71.62 0.0.0.0 UG 0 0 0 eth0 0.0.0.0 194.164.71.62 0.0.0.0 UG 0 0 0 eth0 The 194.164.71.62 is here twice ... Thomas
This bug will be fixed in initscripts-5.14-1.