Hide Forgot
The network startup scripts for starting multiple ethernet devices fails on any card above eth0 if eth0 is disabled. sample ifcfg-eth0: DEVICE=eth0 BOOTPROTO=static IPADDR=192.168.1.1 NETMASK=255.255.255.0 ONBOOT=no sample ifcfg-eth1 DEVICE=eth1 BOOTPROTO=static IPADDR=192.168.1.1 NETMASK=255.255.255.0 ONBOOT=yes The assumption I would have on how this works is by enabling eth1 and setting it to the specified arguments (and leaving eth0 disabled). The way this currently works is that eth1 claims it's starting up at boot time, however it's really eth0 (you have to move the cable to the other NIC -- pain in the ass). The problem, I suspect, is in ifup or the init.d network script, however I'm too lazy to look for it right now. -- patrick@fezbox.com
assigned to initscripts
OK, the problem here is that since the module for whatever network card is 'eth0' isn't actually loaded, eth0 isn't assigned by the kernel, and therefore when the module for eth1 gets loaded, it actually gets assigned eth0.
Should be fixed in initscripts-4.85-1.