FAI confused by DHCP on multiple network interfaces
steffen.grunewald at aei.mpg.de
Thu Mar 18 17:10:56 CET 2021
I'm trying to install an old machine in the basement - from home office,
not having a simple means to pull network plugs, just a static BMC address...
The machine is booted via PXE on *-network:0 (in "lshw"'s terms), and gets
started properly. But then things go downhill a bit, although the install
is successful - it's IPADDR that gets mangled, resulting in a chain of
wrong network settings (and the machine won't boot properly into a state
I could connect to).
Here's the boot.log returned to the server after installation:
# cat boot.log
netdevices_all="eth0 eth1 "
netdevices_up="eth0 eth1 "
netdevices="eth0 eth1 "
All is fine (the DNS server is set by DHCP) - until the addition of the
second IPADDR entry (which indeed belongs to the second NIC).
Everything that sources boot.log afterwards gets affected by this mistake,
and variables.log reads a bit strange:
# cat variables.log | grep '^[A-Z].*\..*\..*\..*'
The FAI version in the Debian Buster NFSROOT is 5.9.4, the NFSROOT was
created (and copied to the non-X86_64 server) on Feb 11.
Is this a known problem? How can I force the setup back to using the initial
IPADDR, obtained from the DHCP/TFTP server that is used for the install?
(I vaguely remember there's a way to feed this into the pxelinux.cfg file
but ideally I should not need to know whether there are responses from other
DHCP servers, and if there are any, they should not overwrite IPADDR - with
a value identical to IP1ADDR.)
Patches (to be applied directly to the NFSROOT) are welcome!
Steffen Grunewald, Cluster Administrator
Max Planck Institute for Gravitational Physics (Albert Einstein Institute)
Am Mühlenberg 1 * D-14476 Potsdam-Golm * Germany
Fon: +49-331-567 7274
More information about the linux-fai