Mailinglist Archive: opensuse-factory (401 mails)

< Previous Next >
Re: No predictable network devices names anymore? (was: Re: [opensuse-factory] Leap 15.1 Build 426.2 released!)

On 3/12/19 1:06 PM, Manfred Hollstein wrote:
On Tue, 12 Mar 2019, 12:51:43 +0100, Knut Alejandro Anderssen González wrote:
On 3/12/19 11:47 AM, Jan Engelhardt wrote:
On Tuesday 2019-03-12 11:59, Neal Gompa wrote:

On Tue, Mar 12, 2019 at 6:47 AM Manfred Hollstein
<mhollstein@xxxxxxxxxxx> wrote:

Hi there,

I just did a new installation (no upgrade this time) and was kind of
surprised to see the network device name is "eth0" again.

If I'm not wrong, predictable network interface names is enabled by
default in TW but that should not be the case in Leap which uses
persistent network names.

but, where did these "persistent" network names come from then? As I
wrote, this was a *new installation* without any reference to former
installations, so I cannot imagine, where this notion of eth0 comes

These names are assigned by the kernel, probably this document [1] could
clarify some of your doubts about predictable vs persistent

Yes, I know, bus enumeration, speed of devices to respond etc.,
but what does this have to do with "persistent network names" in a new

As I said, Leap 15.1 should be based on SLE-15-SP1. Although we give
predictable network interface names a try during SLE-15 development as
you can see in this blog post [1], it finally was not adopted.

So for Leap 15.X it should be the same, that is the classic naming

If you want to force the use of predictable network interface names,
then, giving biosdevname=1 net.ifnames=1 should work.

FWIW, I have three interfaces (two eth and one wlan) on this
system, and I simply don't know, why eth0 won over eth1. Hmmm.




Knut Alejandro Anderssen González
YaST Team at SUSE Linux GmbH

< Previous Next >