From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt
Date: Fri, 29 Mar 2013 10:09:27 +0200 [thread overview]
Message-ID: <51554C37.4000508@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 309 bytes --]
This is required for stabilizing new udev (bug #463614)
And required otherwise too as people are still confused from what I have
seen in forums
I hope this isn't too much of an hand holding
Will push it tomorrow'ish if noone complains (and fix grammar later too
if required)
Thanks for looking into it!
[-- Attachment #2: 2013-03-29-udev-predictable-network-interface-names.en.txt --]
[-- Type: text/plain, Size: 2799 bytes --]
Title: The new default predictable network interface naming with udev
Author: Samuli Suominen <ssuominen@gentoo.org>
Content-Type: text/plain
Posted: 2013-03-29
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <sys-fs/udev-201
If you still have network interface renaming rules in /etc/udev/rules.d,
like 70-persistent-net.rules, you will need to modify or remove them.
If you choose to modify them, you will need to pick a free namespace (like
net* or internet*) that is not reserved by the kernel (like eth* or wlan*)
because in-place renaming has been deprecated[1].
You should also rename the file to something else, like 70-my-network.rules
to silence the deprecation warning coming from when you emerge udev.
This is old format:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="eth1"
This is new format:
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="xx:xx:xx:xx:xx:xx",
NAME="net0"
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="yy:yy:yy:yy:yy:yy",
NAME="net1"
With the new predictable network interface naming scheme which upstream enabled
by default you don't have to rename anymore because the names will be static
and not randomly rename when you, for example, upgrade the kernel. This can be
very important aspect, for example, security in mind.
If /etc/udev/rules.d/80-net-name-slot.rules is a empty file, or if it's a
symlink to /dev/null, the new names will be disabled and kernel will do
all the interface naming, which will be random.
The new names can also be disabled using net.ifnames=0 kernel option.
In normal new installation there is no files put in /etc/udev/rules.d and if
you haven't edited any files you have in there, you should most likely delete
(backup) them all out of the way.
You can find out using udevadm command what your interfaces will be called
before booting to make necessary changes, such as changing net.* symlinks
in /etc/init.d.
This is the example command:
# udevadm test-builtin net_id /sys/class/net/eth0 2> /dev/null
The output could be (and I'm only picking the most important line for this
example):
ID_NET_NAME_PATH=enp2s0f0
This would mean your eth0 will be called enp2s0f0 if there is no previously
mentioned files blocking the new names taking place in /etc/udev/rules.d.
This is documented more throughly at upstream wiki[2] which everyone should
read at least once.
This feature will also replace the functionality of sys-apps/biosdevname which
you should uninstall. However, you can still keep using sys-apps/biosdevname
if you want.
[1] http://www.kernel.org/doc/htmldocs/device-drivers/API-device-rename.html
[2] http://www.freedesktop.org/wiki/Software/systemd/
PredictableNetworkInterfaceNames
next reply other threads:[~2013-03-29 8:11 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 8:09 Samuli Suominen [this message]
2013-03-29 10:24 ` [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt Duncan
2013-03-29 10:26 ` Samuli Suominen
2013-03-29 10:46 ` Diego Elio Pettenò
2013-03-29 10:50 ` Samuli Suominen
2013-03-29 11:01 ` Diego Elio Pettenò
2013-03-29 11:29 ` Samuli Suominen
2013-03-29 11:38 ` Diego Elio Pettenò
2013-03-29 12:20 ` Samuli Suominen
2013-03-29 12:33 ` Diego Elio Pettenò
2013-03-29 12:47 ` Michael Mol
2013-03-29 13:24 ` Andreas K. Huettel
2013-03-29 13:30 ` Rich Freeman
2013-03-29 13:44 ` Samuli Suominen
2013-03-29 14:35 ` Rich Freeman
2013-03-29 14:45 ` Samuli Suominen
2013-03-29 14:55 ` Rich Freeman
2013-03-31 8:41 ` Walter Dnes
2013-03-31 10:21 ` Nuno J. Silva (aka njsg)
2013-03-29 19:20 ` Ian Stakenvicius
2013-03-29 20:03 ` Diego Elio Pettenò
2013-03-31 1:06 ` Philip Webb
2013-03-31 1:17 ` Samuli Suominen
2013-03-31 1:20 ` Diego Elio Pettenò
2013-03-31 10:18 ` Nuno J. Silva (aka njsg)
2013-03-31 11:36 ` Andreas K. Huettel
2013-03-31 14:22 ` Philip Webb
2013-04-01 1:56 ` [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt : SOLVED Philip Webb
2013-04-01 9:23 ` Markos Chandras
2013-04-01 15:32 ` Philip Webb
2013-04-01 17:06 ` Markos Chandras
2013-04-01 19:53 ` Michael Mol
2013-04-01 20:14 ` Markos Chandras
2013-03-29 11:34 ` [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt Chí-Thanh Christopher Nguyễn
2013-03-29 11:40 ` Diego Elio Pettenò
2013-03-29 16:21 ` Nuno J. Silva (aka njsg)
2013-03-29 16:40 ` Markos Chandras
2013-03-29 17:38 ` Rich Freeman
2013-03-29 22:27 ` Walter Dnes
2013-03-29 18:03 ` Samuli Suominen
2013-03-29 18:59 ` Nuno J. Silva (aka njsg)
2013-03-29 11:13 ` [gentoo-dev] " Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51554C37.4000508@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox