Ask Your Question

Revision history [back]

Hello PZ.

By now you probably already know that yes, you can (actually, you HAVE TO) use the native interface names you system offers you, to configure your software.

Using the enoXXXX will be as good as using the ethX in the good old time, or even on other systems.

For what it is worth, the new naming, while strange to old timers like me as well, are smarter: they reflect, among other things, the topology of your particular NIC (EN for Ethernet, WL for wireless lan, etc). It seems to be a trend and we will see more and more of it.

There is some interesting material from RedHat here:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/appe-Consistent_Network_Device_Naming.html

Now, if you really like the old naming, there is a way to go back to it (direct quote from CentOS' site):

  • Add "net.ifnames=0" and "biosdevname=0" as kernel arguments to grub
  • In '/etc/sysconfig/network-scripts/' Change your configured NIC config file to 'ifcfg-ethX'
  • If you have multiple interfaces and want to control naming of each device rather than letting the kernel do in its own way, /etc/udev/rules.d/60-net.rules seems necessary to override /usr/lib/udev/rules.d/60-net.rules.

https://wiki.centos.org/FAQ/CentOS7

Cheers