Linux bare metal protection for clients that have a default network adapter with a name other than eth0



Modify network settings for clients with network adapter names other than eth0.


Clients that have a primary default network adapter with a name other than eth0 might not have their network settings applied properly in the BareMetal environment. The client might have no IP address at boot time, or might crash when attempting to change the IP address.

Example Device Names: eth1, ens32, enp3s0, p4p1.


When creating the Hot BareMetal media a number of system configuration details, including the network settings and their device names, are written to a configuration file (found at /bpab/nodes//config.xml in the BareMetal environment). These device names are assigned by udev, and might not carry into the BareMetal environment.


Editing the configuration file and reloading the baremetal executable should resolve the issue.

Note: Because the configuration file is written to the boot CD, changes made to it will not persist through a reboot. It is recommended that you make these changes after running the “Prepare Disks” option (which does not require a network connection and reboots the system on completion).

  1. Interrupt the BareMetal interface by pressing Ctrl+c.
  2. Use vi to edit the config.xml file (located in the /bpab/nodes// directory).

vi /bpab/nodes/*/config.xml

  1. Locate the primary network adapter entry in the XML tree under network &rarrow; netif.

Note: The device named lo is the loopback device and is never the primary network adapter. If this is one of only two entries, the other device is the primary network adapter.

  1. Change the value of the ifname attribute of the primary network adapter to eth0.
  2. Write the file and quit vi.


  1. Reload the BareMetal configuration.

/bpab/baremetal -e

  1. Launch the BareMetal interface.

/bpab/baremetal 2> /dev/tty2

  1. Proceed as normal.

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section