Re: how to compute predictable network interface names?

2017-03-09 Thread Harald Dunkel
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

Re: how to compute predictable network interface names?

2017-02-24 Thread Christian Seiler
On 02/24/2017 10:10 AM, Harald Dunkel wrote: > On 02/23/2017 04:25 PM, Christian Seiler wrote: >> >> There's a policy which are going to be preferred. man 5 systemd.link >> tells you what the options are and /lib/systemd/network/99-default.link >> tells you what the default setting is (the first

Re: how to compute predictable network interface names?

2017-02-24 Thread Harald Dunkel
On 02/24/2017 10:10 AM, Harald Dunkel wrote: > > Now I got confused: Who is responsible for renaming the NIC names? > Is this a systemd feature, is this the job of udev, or are the NICs > renamed by the kernel very early at boot time? Shouldn't I get the > same predictable name for eth0, no

Re: how to compute predictable network interface names?

2017-02-24 Thread Harald Dunkel
On 02/23/2017 04:25 PM, Christian Seiler wrote: > > There's a policy which are going to be preferred. man 5 systemd.link > tells you what the options are and /lib/systemd/network/99-default.link > tells you what the default setting is (the first successful one is > used). Of course I stumbled

Re: how to compute predictable network interface names?

2017-02-23 Thread Stephen Powell
On Thu, Feb 23, 2017, at 10:16, Harald Dunkel wrote: > On 02/16/2017 12:47 PM, Christian Seiler wrote: > > > > On a system with predictable names running? Or on a system > > pre-upgrade? > > > > Its more "pre-installation". I boot a USB stick and run > my own installer (using debootstrap or

Re: how to compute predictable network interface names?

2017-02-23 Thread Christian Seiler
On 02/23/2017 04:16 PM, Harald Dunkel wrote: > On 02/16/2017 12:47 PM, Christian Seiler wrote: >> >> On a system with predictable names running? Or on a system >> pre-upgrade? >> > > Its more "pre-installation". I boot a USB stick and run > my own installer (using debootstrap or creating a

Re: how to compute predictable network interface names?

2017-02-23 Thread Harald Dunkel
On 02/16/2017 12:47 PM, Christian Seiler wrote: > > On a system with predictable names running? Or on a system > pre-upgrade? > Its more "pre-installation". I boot a USB stick and run my own installer (using debootstrap or creating a clone). The NIC name is needed to setup

Re: how to compute predictable network interface names?

2017-02-16 Thread Greg Wooledge
On Thu, Feb 16, 2017 at 12:47:25PM +0100, Christian Seiler wrote: > On a system with predictable names running? Or on a system > pre-upgrade? > > Because if you have a system that's being upgraded at the > moment, the following command _might_ work _after_ you've > upgraded udev and _before_

Re: how to compute predictable network interface names?

2017-02-16 Thread Christian Seiler
On 02/16/2017 12:24 PM, Harald Dunkel wrote: > I understand that the predictable nic names can be turned off > using > > net.ifnames=0 > > on the kernel command line, but I wonder if there is a shell > script to actually predict the "enpYsZ" from the old style > "ethX" initially assigned

how to compute predictable network interface names?

2017-02-16 Thread Harald Dunkel
Hi folks, I understand that the predictable nic names can be turned off using net.ifnames=0 on the kernel command line, but I wonder if there is a shell script to actually predict the "enpYsZ" from the old style "ethX" initially assigned by the kernel? Something like %