Re: how to compute predictable network interface names?
- To: debian-user@lists.debian.org
- Subject: Re: how to compute predictable network interface names?
- From: Harald Dunkel <harald.dunkel@aixigo.de>
- Date: Thu, 9 Mar 2017 12:04:46 +0100
- Message-id: <[🔎] 99d19720-b080-c8dd-ae93-d23bb3f50f78@aixigo.de>
- In-reply-to: <858cdd98-f843-c64f-7515-eb362cfa4944@iwakd.de>
- References: <d366e557-2797-15a8-f07e-1b17f2d80cfc@aixigo.de> <1a26c5d8-dd9a-14e8-926f-bc8acfd5b49c@iwakd.de> <367770f6-e652-1eaf-ddea-1a829ef08a9f@aixigo.de> <29f9d42d-70ad-a461-5ce0-555b0463e469@iwakd.de> <52984d10-afae-0c0e-63dd-f001d46f7cc8@aixigo.de> <858cdd98-f843-c64f-7515-eb362cfa4944@iwakd.de>
Hi Christian,
On 02/24/17 12:43, Christian Seiler wrote:
>
> udev will then rename the device once it encounters it.
>
> In newer udev versions, it will use some (but not all) settings from
> systemd.link files. The other settings are interpreted by
> systemd.networkd. (And if you don't use that or don't have that
> installed, they will be ignored.) That's also the reasnon why those
> files are in a systemd directory, even though udev interprets some
> parts of them - since the matching of interfaces is identical for
> the purposes of udev and systemd-networkd, systemd developers decided
> it would be simpler to have just one configuration file that is read
> by both. (udev and systemd are both in the same repository, even
> though you can use udev without systemd.)
>
Thats a bad choice. Now the man page is not installed on
"udev-only" systems, because the package maintainer recognized
it as a "systemd" man page. #857270
>
> No. net.ifnames=0 will have udev completely ignore NamePolicy here
> and not rename the interface at all.
>
Is there a policy option telling udev/systemd to not touch the
interface names? AFAIU that should be easy to implement, but
there is no "NamePolicy=keep" described in systemd.link(5) (or
I was too blind to see).
Regards
Harri
Reply to: