Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #178126
| From | Harald Dunkel <harald.dunkel@aixigo.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: how to compute predictable network interface names? |
| Date | 2017-02-24 10:20 +0100 |
| Message-ID | <tekcF-6wz-17@gated-at.bofh.it> (permalink) |
| References | <tbsq5-5wK-13@gated-at.bofh.it> <tbsJs-5E4-27@gated-at.bofh.it> <te3lw-323-21@gated-at.bofh.it> <te3vb-35q-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 over this one: % man 5 systemd.link No manual entry for systemd.link in section 5 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 matter what? > On my Stretch system that is: > > NamePolicy=kernel database onboard slot path > AFAIU NamePolicy=kernel makes sure that net.ifnames=0 given on the kernel command line works. Is this correct? > 'kernel' and 'database' are likely going to fail in most cases (kernel > means the kernel indicates that the name used so far is already > predictable, which it only does for very special hardware, probably > embedded or similar, and database means that there's an entry in the > udev hardware database, which you'd have to do manually, because I > don't know of any upstream rules), so basically it's the following > logic: > > - first try ID_NET_NAME_ONBOARD > - if that doesn't exist, try ID_NET_NAME_SLOT > - if that doesn't exist, try ID_NET_NAME_PATH > Not to forget - if that doesn't exist, use INTERFACE Thanx very much for your detailed response. Harri
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
how to compute predictable network interface names? Harald Dunkel <harald.dunkel@aixigo.de> - 2017-02-16 12:30 +0100
Re: how to compute predictable network interface names? Christian Seiler <christian@iwakd.de> - 2017-02-16 12:50 +0100
Re: how to compute predictable network interface names? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-02-16 14:40 +0100
Re: how to compute predictable network interface names? Harald Dunkel <harald.dunkel@aixigo.de> - 2017-02-23 16:20 +0100
Re: how to compute predictable network interface names? Christian Seiler <christian@iwakd.de> - 2017-02-23 16:30 +0100
Re: how to compute predictable network interface names? Harald Dunkel <harald.dunkel@aixigo.de> - 2017-02-24 10:20 +0100
Re: how to compute predictable network interface names? Harald Dunkel <harald.dunkel@aixigo.de> - 2017-02-24 11:00 +0100
Re: how to compute predictable network interface names? Christian Seiler <christian@iwakd.de> - 2017-02-24 12:50 +0100
Re: how to compute predictable network interface names? Harald Dunkel <harald.dunkel@aixigo.de> - 2017-03-09 12:10 +0100
Re: how to compute predictable network interface names? Stephen Powell <zlinuxman@fastmail.com> - 2017-02-23 18:10 +0100
csiph-web