On 04/11/2017 05:39 AM, Alice Wonder wrote: > On 04/11/2017 05:30 AM, Jonathan Billings wrote: >> On Tue, Apr 11, 2017 at 08:09:01AM -0400, Pete Orrall wrote: >>>> And *why* random NIC names? Quick, you've got servers from 5 >>>> manufacturers, of different ages... what's the NIC going to be >>>> called? Do >>>> names like enp5s0 offer any convenience to *anyone* not a hardware >>>> engineer? >>> >>> As someone else had stated, it's not related to SystemD but >>> Fedora/RHEL has changed the way they handle some things. NICs, for >>> instance, are no longer named after the device number (eth0, eth1, >>> eth2, etc.) but after the *driver* name. Yes, it's a change but it >>> also makes sense. IIRC this is how FreeBSD handles NIC names. >> >> It's true that FreeBSD names their network interfaces after the driver. >> >> But the consistent device naming in Linux comes from slot index >> numbers, physical location and even the MAC (if so configured), and >> not what driver it uses. >> >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html#sec-Naming_Schemes_Hierarchy >> >> > > Okay that makes sense. > > eno1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 0c:c4:7a:c8:a5:4c txqueuelen 1000 (Ethernet) > eno2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 0c:c4:7a:c8:a5:4d txqueuelen 1000 (Ethernet) > > Those two are my onboard nic, Intel - Scheme 1 > > enp10s0f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 00:1b:21:94:72:37 txqueuelen 1000 (Ethernet) > enp10s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 00:1b:21:94:72:36 txqueuelen 1000 (Ethernet) > enp9s0f0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > ether 00:1b:21:94:72:35 txqueuelen 1000 (Ethernet) > enp9s0f1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 > > Those four are on a PCI-E card, Intel - Scheme 3 > > 05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network > Connection (rev 03) > 06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network > Connection (rev 03) > 09:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (Copper) (rev 06) > 09:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (Copper) (rev 06) > 0a:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (Copper) (rev 06) > 0a:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet > Controller (Copper) (rev 06) > > Anyway thanks for that link. er, I meant to add that the 09: seems to correspond with the enp9s* and the 0a: seems to correspond with the enp10s*