# Custom ethernet interface names changes after every reboot
**URL:** https://forums.rockylinux.org/t/custom-ethernet-interface-names-changes-after-every-reboot/13840
**Category:** Rocky Linux Help & Support
**Tags:** rocky-linux-9, dell
**Created:** [May 2, 2024, 3:25am UTC](https://forums.rockylinux.org/t/custom-ethernet-interface-names-changes-after-every-reboot/13840 "2024-05-02T03:25:43Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@kumar](https://forums.rockylinux.org/u/kumar)
#### Post date: [May 2, 2024, 3:25am UTC](https://forums.rockylinux.org/t/custom-ethernet-interface-names-changes-after-every-reboot/13840/1 "2024-05-02T03:25:43Z")
I recently migrated from CentOS7.9 to Rocky 9. One of our Dell server is showing weird behavior with respect to interface namings. I implemented consistent network interface naming using the following guide. I tried both udev as well as systemd approach.
> **[Chapter 1. Implementing consistent network interface naming Red Hat...](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_networking/consistent-network-interface-device-naming_configuring-and-managing-networking)**
>
> Access Red Hat’s knowledge, guidance, and support through your subscription.
However, I see the interface names changes across reboots. I did not had this issue with CentOS 7.9. The consistent naming was working correctly.
Here are the “nmcli con show” command output across reboots. See how the device column changes every reboot.
```auto
# nmcli con show
NAME UUID TYPE DEVICE
eth0 4bb9a27b-d632-4d6c-8672-7d9ce562cb42 ethernet eth0
eth1 485de0bf-81b3-46fd-b3a0-97ce2bc7b399 ethernet eth2
eth2 95bf218c-5ea5-4e65-a12e-55cc6315808e ethernet eth1
lo 96441e7e-6735-42fe-ba8f-8c2d3cce3eb0 loopback lo
eth3 d34c1135-a0d1-4bf4-8f3e-1762094e7c4e ethernet --
```
```auto
# nmcli con show
NAME UUID TYPE DEVICE
eth0 4bb9a27b-d632-4d6c-8672-7d9ce562cb42 ethernet eth0
eth1 485de0bf-81b3-46fd-b3a0-97ce2bc7b399 ethernet eth3
eth2 95bf218c-5ea5-4e65-a12e-55cc6315808e ethernet eth2
lo 96441e7e-6735-42fe-ba8f-8c2d3cce3eb0 loopback lo
eth3 d34c1135-a0d1-4bf4-8f3e-1762094e7c4e ethernet --
```
```auto
# nmcli con show
NAME UUID TYPE DEVICE
eth0 4bb9a27b-d632-4d6c-8672-7d9ce562cb42 ethernet eth2
eth1 485de0bf-81b3-46fd-b3a0-97ce2bc7b399 ethernet eth1
eth2 95bf218c-5ea5-4e65-a12e-55cc6315808e ethernet eth0
lo 96441e7e-6735-42fe-ba8f-8c2d3cce3eb0 loopback lo
eth3 d34c1135-a0d1-4bf4-8f3e-1762094e7c4e ethernet --
```
dmesg log:
```auto
[2.562662] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
[2.883749] igb 0000:01:00.0: added PHC on eth0
[2.883769] igb 0000:01:00.0: eth0: (PCIe:5.0Gb/s:Width x2) e4:43:4b:e6:1d:0e
[2.884090] igb 0000:01:00.0: eth0: PBA No: K15075-002
[2.897159] i40e 0000:18:00.0 eth1: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: None
[3.176154] igb 0000:01:00.1: added PHC on eth2
[3.176176] igb 0000:01:00.1: eth2: (PCIe:5.0Gb/s:Width x2) e4:43:4b:e6:1d:0f
[3.176498] igb 0000:01:00.1: eth2: PBA No: K15075-002
[3.234313] i40e 0000:18:00.1 eth4: renamed from eth3
[5.870475] i40e 0000:18:00.1 eth3: renamed from eth4
[9.923676] igb 0000:01:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
[10.032653] igb 0000:01:00.1 eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
```
Can someone shed some light into what’s happening here. Why Rocky 9 isn’t keeping the interface names consistent.
Thanks
---
### Author:  [@jlehtone](https://forums.rockylinux.org/u/jlehtone)
#### Post date: [May 2, 2024, 2:07pm UTC](https://forums.rockylinux.org/t/custom-ethernet-interface-names-changes-after-every-reboot/13840/2 "2024-05-02T14:07:41Z")
When you said “_custom_”, I did expect names, like “lan” and “wan”, not “eth_N_”.
The default names in el8/el9 ought to be persistent and consistent (and they do not look like “eth_N_”).
* * *
Are the connections on the correct interfaces? NetworkManager does pass name of interface to FirewallD, so each connection will get appropriate firewall rules, if they are.
* * *
> [@kumar](#):
>
> I recently migrated from CentOS7.9 to Rocky 9.
Did you do “fresh install” followed by deployment of _appropriate_ logical confic, or was your “migration” by black magick?
---
### Author:  [@kumar](https://forums.rockylinux.org/u/kumar)
#### Post date: [May 6, 2024, 10:33am UTC](https://forums.rockylinux.org/t/custom-ethernet-interface-names-changes-after-every-reboot/13840/3 "2024-05-06T10:33:36Z")
It was a fresh install. After the install the interface names were listed as enp\*. But my application expects interface names to be eth[N]. By custom, I did mean eth[N].
to rename the enp\* names to eth\*, I followed the redhat article I mentioned earlier. I have followed the article correctly to setup persistent interface names (eth[N]) using udev & systemd. But each time I reboot, the interface names changes.
---
### Author:  [@jlehtone](https://forums.rockylinux.org/u/jlehtone)
#### Post date: [May 6, 2024, 11:33am UTC](https://forums.rockylinux.org/t/custom-ethernet-interface-names-changes-after-every-reboot/13840/4 "2024-05-06T11:33:26Z")
> [@kumar](#):
>
> my application expects interface names to be eth[N].
- Does it need multiple interfaces? (Do all interfaces need an eth_N_ name?)
- Is there no way to reconfigure it?
> [@kumar](#):
>
> ```auto
> i40e 0000:18:00.1 eth4: renamed from eth3
> i40e 0000:18:00.1 eth3: renamed from eth4
>
> ```
Note how interfaces do have initially (random) eth_N_ names. What does the above even do?
Replace name “eth3” with “eth3” in one interface?
* * *
[EDIT]
EL9\_4 will add new _naming scheme_ – the Red Hat doc has been updated recently.
---
### Author:  [@system](https://forums.rockylinux.org/u/system)
#### Post date: [July 5, 2024, 11:34am UTC](https://forums.rockylinux.org/t/custom-ethernet-interface-names-changes-after-every-reboot/13840/5 "2024-07-05T11:34:19Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.