The interface naming convention for RHEL 6 and CentOS 6 is described in Appendix A. The newest naming conventions, with names like eno1 and enp0s3 are used by RHEL 7, CentOS 7, and more recent releases of Fedora.
Names like ethX are still used by CentOS 6.x. That has all changed, more than once.Īfter a short stint with some long and unintelligible network interface names, we now have a third set of naming conventions which seem only marginally better. Unfortunately, adding a new interface often forced the renaming of network interfaces, which broke scripts and configurations. It did not require extra steps to figure out what long and obscure name belonged to an interface. Using ethX made sense to me and was easy to type. The naming conventions for network interfaces used to be simple, uncomplicated, and, I thought, easy. Most of the other files in the /etc/sysconfig/network-scripts directory are scripts used to start, stop and perform various network configuration activities.Įach interface configuration file is bound to a specific physical network interface by the MAC address of the interface. Each interface has a configuration file named ifcfg-X, where X is the number of the interface, starting with zero or 1 depending upon the naming convention in use for example /etc/sysconfig/network-scripts/ ifcfg-eth0 for the first Ethernet interface. Interface configuration filesĮvery network interface has its own configuration file in the /etc/sysconfig/network-scripts directory. Linux desktop computers also support multiple network interfaces, and you can use your Linux computer as a multi-network client, or as a router for internal networks such is the case with a couple of my own systems. Laptops typically include both wired and wireless interfaces, and may also support WiMax interfaces for cellular networks. Linux easily manages multiple network interface adapters. In this article I discuss the main network configuration files for Red Hat-based Linux distributions, and take a look at the two network startup services: the venerable network startup, and the controversial NetworkManager.
0 kommentar(er)
