Re: preseed with multiple network interfaces
hello,
there is no final solution. Depending on the order of your pci device, the
kernel detects your network card. There are kernel parameters that do not
work 100% as "pci = bfsort" or if you have two adapter drivers (ex: bnx2
and tg2) you can blacklist network adapter drivers via "blacklist=tg2".
The solution I found to deploy machines with multiple NICs with the
Debian-Installer (preseed-installation) is modified initrd.
Sincerely,
-
Arnaud
On Tue, 29 Mar 2011 08:53:02 -0700, melbogia <melbogia@gmail.com> wrote:
> Anybody has any ideas how to fix or get around this issue?
>
> On Mon, Mar 28, 2011 at 1:44 PM, melbogia <melbogia@gmail.com> wrote:
>> Hello,
>> We have a bunch of machines with multiple NICs and eth0 isn't the one
>> that is connected to the network, but the installers tries to get a
>> link on eth0 and doesn't seem to try other interfaces. This is how the
>> PXE label looks like, I do have inteerface=auto, which should pick the
>> correct interface.
>>
>> label squeeze
>> kernel debian-installer/squeeze/i386/linux
>> append vga=788 initrd=debian-installer/squeeze/i386/initrd.gz
>> auto=true priority=critical ramdisk_size=10800 root=/dev/rd/0 rw
>> url=example.com/d-i/squeeze/preseed.cfg interface=auto
>> netcfg/dhcp_timeout=60
>>
>> This is the error I encounter
>>
>> âââââââââââââââââââââ⤠[!!] Configure the network
>> âââââââââââââââââââââââ
>> â â
>> â Network autoconfiguration failed â
>> â Your network is probably not using the DHCP protocol. Alternatively,
â
>> â the DHCP server may be slow or some network hardware is not working â
>> â properly. â
>> â â
>> â <Continue> â
>> â â
>>
âââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
>>
>> If I then drop to a shell, and look at dmesg, it sees all the
>> interfaces albeit with no link
>>
>> ~ # dmesg | grep eth
>> [ 11.348317] 0000:0a:00.0: eth0: (PCI Express:2.5GB/s:Width x4)
>> 00:0e:b6:92:eb:e1
>> [ 11.436859] 0000:0a:00.0: eth0: Intel(R) PRO/1000 Network Connection
>> [ 11.512950] 0000:0a:00.0: eth0: MAC: 0, PHY: 4, PBA No: c83246-002
>> [ 12.204810] 0000:0a:00.1: eth1: (PCI Express:2.5GB/s:Width x4)
>> 00:0e:b6:92:eb:e0
>> [ 12.293317] 0000:0a:00.1: eth1: Intel(R) PRO/1000 Network Connection
>> [ 12.369408] 0000:0a:00.1: eth1: MAC: 0, PHY: 4, PBA No: c83246-002
>> [ 13.353230] 0000:09:00.0: eth2: (PCI Express:2.5GB/s:Width x4)
>> 00:0e:b6:92:eb:df
>> [ 13.441777] 0000:09:00.0: eth2: Intel(R) PRO/1000 Network Connection
>> [ 13.517865] 0000:09:00.0: eth2: MAC: 0, PHY: 4, PBA No: c83246-002
>> [ 15.095250] 0000:09:00.1: eth3: (PCI Express:2.5GB/s:Width x4)
>> 00:0e:b6:92:eb:de
>> [ 15.183810] 0000:09:00.1: eth3: Intel(R) PRO/1000 Network Connection
>> [ 15.259900] 0000:09:00.1: eth3: MAC: 0, PHY: 4, PBA No: c83246-002
>> [ 16.204523] 0000:03:00.0: eth4: (PCI Express:2.5GB/s:Width x1)
>> 00:0e:b6:3d:4d:11
>> [ 16.293069] 0000:03:00.0: eth4: Intel(R) PRO/1000 Network Connection
>> [ 16.369155] 0000:03:00.0: eth4: MAC: 3, PHY: 8, PBA No: ffffff-0ff
>> [ 17.533191] 0000:02:00.0: eth5: (PCI Express:2.5GB/s:Width x1)
>> 00:0e:b6:3d:4d:10
>> [ 17.621734] 0000:02:00.0: eth5: Intel(R) PRO/1000 Network Connection
>> [ 17.697834] 0000:02:00.0: eth5: MAC: 3, PHY: 8, PBA No: ffffff-0ff
>> [ 27.196361] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 27.568354] ADDRCONF(NETDEV_UP): eth1: link is not ready
>> [ 27.940352] ADDRCONF(NETDEV_UP): eth2: link is not ready
>> [ 28.312354] ADDRCONF(NETDEV_UP): eth3: link is not ready
>> [ 28.500634] ADDRCONF(NETDEV_UP): eth4: link is not ready
>> [ 28.596630] ADDRCONF(NETDEV_UP): eth5: link is not ready
>> [ 29.892356] ADDRCONF(NETDEV_UP): eth0: link is not ready
>> [ 30.264357] ADDRCONF(NETDEV_UP): eth1: link is not ready
>> [ 30.636354] ADDRCONF(NETDEV_UP): eth2: link is not ready
>> [ 31.008357] ADDRCONF(NETDEV_UP): eth3: link is not ready
>> [ 31.196637] ADDRCONF(NETDEV_UP): eth4: link is not ready
>> [ 31.288633] ADDRCONF(NETDEV_UP): eth5: link is not ready
>> [ 31.576355] ADDRCONF(NETDEV_UP): eth0: link is not ready
>>
>> I then try to get a lease on the right interface and it works
>>
>> ~ # udhcpc -i eth4
>> udhcpc (v1.17.1) started
>> Sending discover...
>> Sending discover...
>> Sending select for 10.1.8.202...
>> Lease of 10.1.8.202 obtained, lease time 1800
>>
>> On the kernel line I can try interface=eth4 and it works but we have a
>> bunch of machines and eth4 may or may not be right for different
>> machines. Why isn't interface=auto working correctly and what can I do
>> to make it work and automatically pick the right interface?
>>
Reply to: