Multiple NICs, partial success, partial weirdness

[Carsten Aulbert]

Hi,

after this subject I seem to have caught you attention :)

First the success part: There seems to be a bug in initramfs-tools in
Lenny which manifests itself when booting a machine with multiple NICs
(Thomas might remember mny query on IRC some time ago).

The solution is relatively simple, you need to patch two files as
described here:

http://lists.debian.org/debian-live/2009/02/msg00088.html

Hopefully it'll be fixed soon.

The weird part:

Yesterday I reinstalled a computer several times, tuning ssh settings
and other customizations, however, I'm not aware to change something
substantial, but suddenly it seems the wrong entry in pxeboot.cfg is
modified:

grep 'disable' install-200903*/fai.log
install-20090302_191531/fai.log:disable pxe config for 10.20.30.3 in hex
0A141E03
install-20090302_192700/fai.log:disable pxe config for 172.28.20.3 in
hex AC1C1403
install-20090302_193420/fai.log:disable pxe config for 172.28.20.3 in
hex AC1C1403
install-20090302_194559/fai.log:disable pxe config for 172.28.20.3 in
hex AC1C1403

Looks good in theory, at least the first once, but given that this
machine has several interfaces
eth0      Link encap:Ethernet  HWaddr 00:30:48:65:40:62
          inet addr:10.20.30.3  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::230:48ff:fe65:4062/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
          RX packets:244575 errors:0 dropped:557 overruns:0 frame:0
          TX packets:202100 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:193394920 (184.4 MiB)  TX bytes:17128660 (16.3 MiB)
          Memory:d9120000-d9140000

eth1      Link encap:Ethernet  HWaddr 00:30:48:65:40:63
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Memory:d9160000-d9180000

eth2      Link encap:Ethernet  HWaddr 00:1b:21:14:79:b2
          inet6 addr: fe80::21b:21ff:fe14:79b2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:165 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:9974 (9.7 KiB)  TX bytes:2688 (2.6 KiB)

eth3      Link encap:Ethernet  HWaddr 00:1b:21:14:79:b3
          inet addr:172.28.20.3  Bcast:172.31.255.255  Mask:255.240.0.0
          inet6 addr: fe80::21b:21ff:fe14:79b3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11123 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:678595 (662.6 KiB)  TX bytes:6303 (6.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:40 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2608 (2.5 KiB)  TX bytes:2608 (2.5 KiB)

and PXE boots and installs via eth0; also it gets the IP for eth0 from
the FAI server (also tftp server), but eth3 is handled by a different
DHCP server....

Any idea what triggered FAI to use the wrong IP for disabling PXE?

I'm currently trying to find the script doing that, but so far have not
found it....

Cheers

Carsten