Mailinglist Archive: opensuse-factory (776 mails)

< Previous Next >
Re: [opensuse-factory] 13.1 - why network eth0 is named instead ens33?
  • From: "Carlos E. R." <carlos.e.r@xxxxxxxxxxxx>
  • Date: Sat, 28 Sep 2013 17:13:16 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.1309281708420.1095@Telcontar.valinor>
Hash: SHA1

On Saturday, 2013-09-28 at 15:53 +0100, Paul Thompson wrote:


On Sat, Sep 28, 2013 at 04:17:23PM +0200, Carlos E. R. wrote:
On second boot, there was no network, but rcnetwork started it.

However, the name is abusrd: ens33.
Where is eth0?

By default systemd now names interfaces using firmware/BIOS provided
index numbers (e.g. eno1), but if that info is not available (possibly
because you're inside vmplayer) it falls back to naming after
firmware/BIOS provided PCI-E hotplug slot index numbers -- which is what
you're seeing here.

Why the change?

It's in order to ensure *predictable* NIC names across reboots.

My computers have been reliably using eth0 for decades.

This computer has two nics, and eth0 has always been eth0, and eth1 has always been eth1.

For instance, now a script that used eth0 would have to be edited for each computer.

How do I revert that change?

You could disable the udev rule with something like:
`ln -sv /dev/null /etc/udev/rules.d/80-net-name-slot.rules`

I'll have a look.

- -- Cheers,
Carlos E. R.
(from 12.3 x86_64 "Dartmouth" at Telcontar)
Version: GnuPG v2.0.19 (GNU/Linux)

To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups