Mailinglist Archive: opensuse-factory (776 mails)
< Previous | Next > |
Re: [opensuse-factory] 13.1 - why network eth0 is named instead ens33?
- From: Paul Thompson <paul@xxxxxxxx>
- Date: Sat, 28 Sep 2013 15:53:54 +0100
- Message-id: <20130928145348.GA3231@suse.com>
Carlos,
On Sat, Sep 28, 2013 at 04:17:23PM +0200, Carlos E. R. wrote:
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.
It's in order to ensure *predictable* NIC names across reboots.
You could disable the udev rule with something like:
`ln -sv /dev/null /etc/udev/rules.d/80-net-name-slot.rules`
Regards,
--
Paul Thompson
SUSE Consulting
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
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.
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`
Regards,
--
Paul Thompson
SUSE Consulting
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
< Previous | Next > |