Bare metal installation issue when changing network interface name to eth0

[Uldis (UD)]

There is interfaces order issue, your eth0 interface is eno49


ip addr
to check IP and MAC

write new file

/etc/udev/rules.d/70-persistent-net.rules

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="eth0"

replace xx:xx... by mac

which have IP


lspci
dmesg | grep eth

[flytripper]

There is interfaces order issue, your eth0 interface is eno49


ip addr
to check IP and MAC

write new file

/etc/udev/rules.d/70-persistent-net.rules

SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx", NAME="eth0"

replace xx:xx... by mac

which have IP


lspci
dmesg | grep eth

I am having same issue as OP. Tried this and did not work. Any other ideas? Is it really important that we change the primary network connection to "eth0"??

For example, following the "community cookbook", network is DHCP and works great until step 42. Up to this point, my "primary net int" is "enp0s25". I change it to "eth0" per step 42. After the reboot at end of step 42 - network no longer works.

@Uldis (UD) - are you saying that by creating this new file (70-xxxx.rules) that it will overwrite the /etc/network/interfaces info and I should leave the value set to en0s25 in the "interfaces" file? any help would be appreciated.

[flytripper]

@ Evaldas

OK, I played around with this and got it working on my server. My server has 2 NICs. For whatever reason, on initial install it used one of the NICs on my box but after step 42 - eth0 was now assigned to my "other" NIC. I moved the network cable to the second NIC and all started working.

btw, that "other" NIC also pulled a new IP (DHCP) - different than the IP that had been assigned to the first NIC. So you may want to "ip add" to see what your new IP is if DHCP.

To summarize - I started with a fresh install (doing none of the things mentioned in this thread) and simply moved my cable to the other NIC after step 42 reboot.

GOOD GRIEF !!!!