I actually like the enp3s0 naming convention. It maps directly to the pci addresses. For instance, an 'lspci' shows my ethernet controller at
> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network > Connection (Lewisville) (rev 04) The 00:19.0 translates to enp0s25. 00 is p0, 19 is s25 (0x19). For multi-nic and even single nic machines, I can specify the network device exactly in my kickstart scripts. There is a very nice description of this new naming convention at > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.freedesktop.org_wiki_Software_systemd_PredictableNetworkInterfaceNames_&d=DwIGaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=gd8BzeSQcySVxr0gDWSEbN-P-pgDXkdyCtaMqdCgPPdW1cyL5RIpaIYrCn8C5x2A&m=ve0iDujF83qZPoGY-CHE8H46dcLDvMe-OAIzwpEPHsA&s=-WUetksEpdNV_-g9lnWnPzOxWyes58hqnZGYP2MyAJE&e= On 3/17/20 3:13 PM, Nico Kadel-Garcia wrote: > enp3s0 is now the bunny, and it's by default using systemd based DHCP > running under NetworkManager. I'm not happy, but do *not* try to reset > the ethernet device name to eth0. And I urge you to stop trying to > replace those scripts, you'll hurt yourself. >
