If I run ifconfig command on my rhel7 machine I see below output:
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet x1.x2.x3.x4 netmask 255.255.255.192 broadcast xx.xx.xx.xx inet6 xxxx:xxxx:xx:xxxx::xxxx prefixlen 64 scopeid 0x0<global> lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) lo:1: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet x5.x6.x7.x8 netmask 255.255.255.255 loop txqueuelen 1000 (Local Loopback) Edit: I read about the predictable interface naming scheme, but it nowhere mentions about the loopback interfaces below.
What does eno mean in network interface name 'eno16777736' for CentOS 7 or RHEL 7?
lo:1appears as an interface only toifconfigbecause it's using the obsolete (on Linux, for networking) ioctl(2) API which has been superseded about 20 years ago in kernel 2.2 by netlink(7) socket / rtnetlink(7) API. Because on Linux the ioctl() API doesn't provide a method to add more than one IPv4 address per interface, it presents so-called alias interfaces. Any other part of the system knows onlylo. eg:iptables -A INPUT -i lo:1will never match. Forget the use ofifconfigand disregard documentation using it. Useip link+ip address.