CentOS - Feb 2020 - CentOS 7 : network interface renamed from eth0 to eth1 after reboot

There may be ways to force NIC naming, I've done so but only on Ubuntu so
you'll need to do the research if it's important to you.  Things to look
for based on my experience: 70-persistent-net.rules, net.ifnames=0,
biosdevname=0.

________________________________
From: CentOS <centos-bounces at centos.org> on behalf of Nicolas Kovacs
<info at microlinux.fr>
Sent: Sunday, February 9, 2020 12:51 PM
To: centos at centos.org <centos at centos.org>
Subject: [EXTERNAL] Re: [CentOS] CentOS 7 : network interface renamed from eth0
to eth1 after reboot

Le 09/02/2020 ? 16:54, Alexander Dalloz a ?crit :
> "Kernel always uses the ethX naming convention at boot when it
enumerates
> network devices. Due to parallelization, the order of the kernel interface
> enumeration is expected to vary across reboots."
Thanks for the heads up.

I experimented quite a bit, and found some surprising behavior. So I documented
everything in a little blog article.

   *
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.microlinux.fr%2finterfaces-reseau-persistantes%2f&c=E,1,apWInXfONKIS7FI-2r96hzoROBMB28lpEncRGtBCvS-yWk5DU4roROpidqfC06FNDn2rlEYO-xJjHn2B0klz4_h1y7kiuBvlSjCMer8MBCuMgAcKUg,,&typo=1

Cheers,

Niki

--
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site :
https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.microlinux.fr&c=E,1,egz8jO853imKX3mT5r9bs5vOCANcassZ0dea14ELcSZMwyZ5fJhfqPU6G1SltXyA8jjCrUwRU-k0Hj5oXsh2RioeNQj-7HsnfPYs1pYwHt6Vnp0cvNSVHpBAPA,,&typo=1
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32
Mob. : 06 51 80 12 12
_______________________________________________
CentOS mailing list
CentOS at centos.org
https://lists.centos.org/mailman/listinfo/centos

Harriscomputer

Leroy Tennison
Network Information/Cyber Security Specialist
E: leroy at datavoiceint.com


[cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG]


2220 Bush Dr
McKinney, Texas
75070
www.datavoiceint.com<http://www..com>


This message has been sent on behalf of a company that is part of the Harris
Operating Group of Constellation Software Inc.

If you prefer not to be contacted by Harris Operating Group please notify
us<http://subscribe.harriscomputer.com/>.



This message is intended exclusively for the individual or entity to which it is
addressed. This communication may contain information that is proprietary,
privileged or confidential or otherwise legally exempt from disclosure. If you
are not the named addressee, you are not authorized to read, print, retain, copy
or disseminate this message or any part of it. If you have received this message
in error, please notify the sender immediately by e-mail and delete all copies
of the message.

On Mon, Feb 10, 2020 at 03:12:11PM +0000, Leroy Tennison
wrote:
> There may be ways to force NIC naming, I've done so but only on Ubuntu
so you'll need to do the research if it's important to you.  Things to
look for based on my experience: 70-persistent-net.rules, net.ifnames=0,
biosdevname=0.
I cheated; I use NIC teaming, and before starting networking, run a
script that iterates over NICs, picking up their current device
names, and scripting the if-cfg* files.

I had to do this when a few years ago, Dell was getting clever about
renaming NICs aggressively, and nothing could trust 'eth0' anymore.
Now, I always get a 'bond0'.

(Oh, and I also disabled NetworkManager, because, like systemd, it
tries to be Too Clever for it's own good.)

Overkill for most, I admit, but it make my installation media much
more portable.

-- 
Brian Reichert				<reichert at numachi.com>
BSD admin/developer at large

Le 10/02/2020 ? 16:12, Leroy Tennison a ?crit :
> There may be ways to force NIC naming, I've done so but only on Ubuntu
so
> you'll need to do the research if it's important to you.  Things to
look for
> based on my experience: 70-persistent-net.rules, net.ifnames=0,
> biosdevname=0.
That's exactly the solution I described in detail in my blog article.

:o)

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site : https://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32
Mob. : 06 51 80 12 12

On 2020-02-11 00:09, Nicolas Kovacs wrote:
> Le 10/02/2020 ? 16:12, Leroy Tennison a ?crit :
>> There may be ways to force NIC naming, I've done so but only on
Ubuntu so
>> you'll need to do the research if it's important to you.?
Things to look for
>> based on my experience: 70-persistent-net.rules, net.ifnames=0,
>> biosdevname=0.
> 
> That's exactly the solution I described in detail in my blog article.

Having messed a lot with this renaming issue in the past,
I can tell you there is only one thing that you have to do for
stable ethernet naming, just have "HWADDR=" in your
ifcfg-* scripts.

See

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-understanding_the_device_renaming_procedure

(you can stop reading at rule 1)

Regards.

-- 
    Roberto Ragusa    mail at robertoragusa.it