Running CentOS 7.0 64-bit which is a guest in Virtual Box.

I have one ethernet interface named enp0s3 and I went into /etc/sysconfig/network-scripts and renamed the file where it was getting the name enp0s3 from ifcfg-enp0s3>ifcfg-eth0-1.

Restated network services under /etc/init.d and for some reason the OS is still picking up the old name, enp0s3.

If I do a find command it pulls back alot of places from /proc (I can't copy an past from the guest to here, I don't have Virtual Box Guest Additions installed).

Is there some other place where I need to make this change so the ethernet interface shows up as eth0?

thanks

The name of the file does *not* determine the name of the interface. Renaming the file would have no impact on the name of the IF. At the very least you will have to change the NAME= line in the file itself, and I believe there are other steps required for bailing on the udev naming conventions in RHEL7/CentOS7.

Here's a guide that 2 seconds of google-time turned up: http://ask.xmodulo.com/change-networ...e-centos7.html

Why not just adopt the standard naming convention? It's not going away, so we should all get used to it (just like journalctl, etc.).

To get former interface name back add "net.ifnames=0" parameter to kernel boot command line.
It will prevent crazy enp0s3 name.
After that you (probably) have to reconfigure your networking settings to get them configured for eth0

I'd assume that every distro will eventually go to a naming convention that describes the nic base on location in system rather than arbitrary info like eth0.

It was on BSD and other OS's for a while and has practical advantages.

1 members found this post helpful.

15-20 years ago one might have been able to figure out which physical network connection corresponded to such a name, based on the (PCI) bus and slot number. Unless of course you were using a multi-port NIC with a built-in PCI-to-PCI bridge, in which case all bets would be off anyway.

Nowadays, it's usually impossible to tell which logical bus a given NIC is actually connected to, as most NICs are part of the motherboard. This is particularly true for servers, which may have anything from 2 to 5 built-in NICs.
Physical interfaces have retained their logical names on most Linux distributions for years. True, a NIC is given a semi-arbitraty "ethn" name at first bootup, based on the order in which the various NIC drivers are loaded and initialized, but then the init scripts call udev which renames the interfaces based on certain hardware characteristics, usually the MAC address. This is then stored in a persistent udev rule, causing the interface to be permanently associated with that name.

In other words, on older Linux systems, "eth0" will remain "eth0" no matter where the physical card resides. Change the physical NIC, and you get a new name.

On newer (typically systemd based) distros, the same NIC gets a new name if you move it to another PCI(e) slot, and a different make/model NIC in the same slot inherits the old name. Personally, I must say I find the old convention far more logical and less likely to cause confusion, and to me this new naming convention looks like a change being made just for the sake of it.

(Also, replacing the I/F names used by the kernel in order to accommodate a new naming convention has of course obsoleted tons of documentation and broken a lot of software.)

1 members found this post helpful.

This isn't 15-20 years ago, though...

useless feature for almost all desktops and laptops that has in general one eth and one wlan interface.

My point exactly.

There is some way to revert a distro back to the old naming scheme. I did read that someplace.

I've used QNX for decades and they have used names by driver/chipset so it's not so foreign to me.

I didn't realize that the naming standard for Linux network interfaces were changing.

Thanks for the guide.