FAI 4 - forcing dracut/dhcp to specific interface

[Mike Messick]

Hi folks,

I'm new to fai and am still learning how all of the pieces fit together.  If this has been asked and answered already, please point me in the right direction and accept my apologies for the noise on the list.

I'm using FAI 4 to install debian on a device that has 6 ethernet interfaces on it.  Per the installation walkthrough documentation, it looks like FAI 4 is designed to iterate through the interfaces, trying each one until dhcp gets an IP.

My problem is that eth0 is tried last on this device, and happens to be the interface I need/want to use for fai installs:

[ snip ]
[    7.413341] sd 2:0:0:0: [sda] Attached SCSI disk
Starting dhcp for interface eth2
[   44.373888] ADDRCONF(NETDEV_UP): eth2: link is not ready
dhcp failed
Starting dhcp for interface eth3
[  106.997866] ADDRCONF(NETDEV_UP): eth3: link is not ready
dhcp failed
Starting dhcp for interface eth4
[  168.465885] ADDRCONF(NETDEV_UP): eth4: link is not ready
dhcp failed
Starting dhcp for interface eth5
[  229.609877] ADDRCONF(NETDEV_UP): eth5: link is not ready
dhcp failed
Starting dhcp for interface eth1
[  290.709887] ADDRCONF(NETDEV_UP): eth1: link is not ready
dhcp failed
[  352.426992] dracut: Mounted root filesystem 192.168.210.1:/srv/fai/nfsroot
[  352.442919] aufs: module is from the staging directory, the quality is unknown.
[  352.456081] aufs 3.2-20130204
[ snip ]

Is there a way to force the interface that dhcp uses on the client during boot to use eth0 so I can avoid the several-minute delay during initial boot?

Thanks in advance for any guidance on this,
-Mike.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.uni-koeln.de/pipermail/linux-fai/attachments/20130320/c17361fb/attachment.html>