PXE booting and predictable NIC names?
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Hello.
I'm looking for information on how the
net.ifnamesboot option works, possibly in conjunction with thelive-netdevoption.We are running clonezilla frequently, via PXE, on machines with 2 wired interfaces. Kcmd contains
net.ifnames=0(probably just copied from a PXE booting guide without further investigation at the time of initial implementation) and alsolive-netdev=eth1, as initially this is how clonezilla would name the correct interface.After racking up more executions, we noticed that about 20% of the time, the ordering of interfaces is reversed/different, and clonezilla tries to connect on the wrong interface, which is named eth1 at the time.
Do I just set the
net.ifnames=1andlive-netdevto whatever the "predictable" name of the interface is? (Our booting setup allows us to add particular boot option on per-host basis, so looking up the predictable name on each hardware model is not a problem, though I would like if there was some symbolic name for "whichever interface PXE booted from")Which version of Clonezilla live did you use in your PXE environment?
Have you tried the latest stable one? E.g. 3.1.2-22 or 20240408-noble?
https://clonezilla.org/downloads.php
It has addressed this issue:
https://salsa.debian.org/live-team/live-boot/-/merge_requests/50
So I believe you can just use net.ifnames=1 in your boot parameters. It should work. You do not have to assign which NIC to be used and the live-boot should find the correct one.
Steven