Arch Linux

zekie

Member

Registered: 2020-06-14

Posts: 3

[SOLVED] Network interface named as eth0 instead of a predictable name

I just followed through Installation Guide on my Hyper-V virtual machine and rebooted into the new system. While I was setting up my network in the new system, "ip link" shows that my only network interface is assigned as eth0, but to my knowledge, it should've been "enX" format according to Predictable Interface Names since udev v197. So my question is how could that be the case?

I checked the version of udev installed is 245, and I was trying to find the answer searching around wiki before I got hit by another confusion.

According to Network Configuration in wiki, it gives an instruction concerning "Revert to traditional interface names",

ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

But the directory "/etc/udev/rules.d", turns out to be empty on my host. Would it be related to the naming problem?

So, to make it clearly, I have two potentially coherent questions here:

1. What caused the initial naming problem?
2. How come "/etc/udev/rules.d" is empty while the wiki assume it's not?

Last edited by zekie (2020-06-15 02:43:54)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,729

Re: [SOLVED] Network interface named as eth0 instead of a predictable name

iwd is installed on the ISO, which disables predictable names. They should change when you boot the new system.

zekie

Member

Registered: 2020-06-14

Posts: 3

Re: [SOLVED] Network interface named as eth0 instead of a predictable name

iwd is installed on the ISO, which disables predictable names. They should change when you boot the new system.

Thank you, but the issue occurred in the new system instead of the ISO.

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: [SOLVED] Network interface named as eth0 instead of a predictable name

"ip link" shows that my only network interface is assigned as eth0, but to my knowledge, it should've been "enX" format according to Predictable Interface Names since udev v197.

Go back and read that site again:

The following different naming schemes for network interfaces are now supported by udev natively:

1. Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)

2. Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)

3. Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)

4. Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)

5. Classic, unpredictable kernel-native ethX naming (example: eth0)

https://www.freedesktop.org/wiki/Softwa … faceNames/

Number 5 applies to your system.

---

Jin, Jîyan, Azadî

zekie

Member

Registered: 2020-06-14

Posts: 3

Re: [SOLVED] Network interface named as eth0 instead of a predictable name

Number 5 applies to your system.

Thank you, it's really helpful. It makes sense to fall back to policy #5, considering my OS is running on vm with a virtual network adapter.