Re: Predictable Network Interface Names

Erwan David writes: > I also got a name change with an upgrade (I do not remember wether it > was kernel, systemd or udev). > > SInce interfaces where combined in a bond, imagine the mess... I think I noticed something like that too as I've updated my desktop HW and booted from some different me

Re: Predictable Network Interface Names

On 3/30/22, Dan Ritter wrote: > Greg Wooledge wrote: >> On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: >> > That's good advice, but are MAC addresses memorable? >> >> Doesn't matter. You can choose a memorable name. The MAC address is >> simply the data point you place in the config file

Re: Predictable Network Interface Names

On Thu, Mar 31, 2022 at 08:04:13AM -0400, Michael Stone wrote: > On Thu, Mar 31, 2022 at 07:10:33AM +0200, to...@tuxteam.de wrote: > > Somewhat self-referential. I'm not the one getting worked up here ;-) > > And I'm not the one accusing people of lying. I hope my clarification --uh-- clears thin

Re: Predictable Network Interface Names

On Thu, Mar 31, 2022 at 12:39:37PM +0100, Brian wrote: > On Thu 31 Mar 2022 at 07:28:47 +0200, to...@tuxteam.de wrote: > > [...]] > > > Since then, I learnt that I like to relax call my interfaces > > "eth0" and "wlan0". > > > > Can we still be friends? > > Of course! After all, we are both pla

Re: Predictable Network Interface Names

On Thu, Mar 31, 2022 at 07:10:33AM +0200, to...@tuxteam.de wrote: Somewhat self-referential. I'm not the one getting worked up here ;-) And I'm not the one accusing people of lying.

Re: Predictable Network Interface Names

On 2022-03-31 at 01:28, to...@tuxteam.de wrote: > This is one weakness I see with freedesktop often. They try to > fight complexity with ever more complexity, with the end result > of a more user-unfriendly (because less understandable) system. Very well expressed. I've added that to the "complet

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 05:56:47PM -0500, Nicholas Geovanis wrote: Because some of us work in corporate data centers. And everything you claim that helps us here really does the opposite. Because it was introduced in large part to support mobile computing. Which does not and will never be valuabl

Re: Predictable Network Interface Names

On Thu 31 Mar 2022 at 07:28:47 +0200, to...@tuxteam.de wrote: [...]] > Since then, I learnt that I like to relax call my interfaces > "eth0" and "wlan0". > > Can we still be friends? Of course! After all, we are both playing in the same game. -- Brian.

Re: Predictable Network Interface Names

31.03.22, 13:01 +0200, Sven Hartge: Greg Wooledge wrote: unicorn:~$ cat /etc/systemd/network/10-lan0.link [Match] MACAddress=18:60:24:77:5c:ec [Link] Name=lan0 Careful with that one. If you use VLANs then you suddenly get multiple interface with the same MAC and strange things will happe

Re: Predictable Network Interface Names

Greg Wooledge wrote: > unicorn:~$ cat /etc/systemd/network/10-lan0.link > [Match] > MACAddress=18:60:24:77:5c:ec > [Link] > Name=lan0 Careful with that one. If you use VLANs then you suddenly get multiple interface with the same MAC and strange things will happen, because it matches for all of

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 10:38:10PM +0100, Brian wrote: > On Wed 30 Mar 2022 at 21:50:53 +0200, to...@tuxteam.de wrote: > > > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > > > > > On Wed, Mar 30, 2022 at 05:35:12PM +02

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 05:55:11PM -0400, Michael Stone wrote: > On Wed, Mar 30, 2022 at 10:38:10PM +0100, Brian wrote: > > Perhaps? Perhaps what? Perhaps it is a lie? freedesktop conceals > > the truth and peddles false information purposefully? > > Some people get excessively worked up over thin

Re: Predictable Network Interface Names

On Wednesday, 30 March 2022 18:31:36 EDT Michael Stone wrote: > On Wed, Mar 30, 2022 at 06:19:17PM -0400, Greg Wooledge wrote: > >It's like you haven't even read this thread. > > of course I have > > >Predictable interface names *do* sometimes change. And when that > >happens, it's a huge deal,

Re: Predictable Network Interface Names

> Some people get excessively worked up over things like interface names > and like to throw around strong words for dramatic effect. Just ignore > the noise. I've just come to accept that the actual interface name is going to be some bizarre name. So I look it up, and then promptly rename it

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022, 5:32 PM Michael Stone wrote: > On Wed, Mar 30, 2022 at 06:19:17PM -0400, Greg Wooledge wrote: > >It's like you haven't even read this thread. > > of course I have > > >Predictable interface names *do* sometimes change. And when that happens, > >it's a huge deal, because all

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 06:19:17PM -0400, Greg Wooledge wrote: It's like you haven't even read this thread. of course I have Predictable interface names *do* sometimes change. And when that happens, it's a huge deal, because all of the configuration files are set up for the old name. Things

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 05:55:11PM -0400, Michael Stone wrote: > For most consumer sytems the interface name matters not one bit, because > it's auto-discovered on install, will never change, and there's little > likelihood that another interface will be added. It's like you haven't even read this

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 10:38:10PM +0100, Brian wrote: Perhaps? Perhaps what? Perhaps it is a lie? freedesktop conceals the truth and peddles false information purposefully? Some people get excessively worked up over things like interface names and like to throw around strong words for dramati

Re: Predictable Network Interface Names

On Wed 30 Mar 2022 at 21:50:53 +0200, to...@tuxteam.de wrote: > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > > > On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > > > > as I can read here [1] network names shoul

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 04:00:42PM -0500, Nicholas Geovanis wrote: > Does anyone here know how the BSD-derived "free" unices handle this > situation? I haven't used OpenBSD in several years, but the last time I used it, it went something like this: The OpenBSD kernel has drivers for lots of diffe

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022, 2:15 PM Brian wrote: > On Wed 30 Mar 2022 at 14:39:33 -0400, Greg Wooledge wrote: > > > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > > Yes. You've now seen direct evidence of the lie. I guess

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > > > as I can read here [1] network names should be stable. > > > (Stable interface names even when hardware is added or

Re: Predictable Network Interface Names

Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > That's good advice, but are MAC addresses memorable? > > Doesn't matter. You can choose a memorable name. The MAC address is > simply the data point you place in the config file, so the system knows > this is the

Re: Predictable Network Interface Names

Le 30/03/2022 à 21:15, Brian a écrit : = which goes into some detail. Thanks. Very informative. As the second link says: The resulting reality is that your PCI based names are only stable if you change no hardware in the s

Re: Predictable Network Interface Names

On Wed 30 Mar 2022 at 14:39:33 -0400, Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > > Yes. You've now seen direct evidence of the lie. I guess I won't need > > > to post links to the wiki articles

Re: Predictable Network Interface Names

Le 30/03/2022 à 20:39, Greg Wooledge a écrit : Doesn't matter. You can choose a memorable name. The MAC address is simply the data point you place in the config file, so the system knows this is the interface you're talking about. unicorn:~$ cat /etc/systemd/network/10-lan0.link [Match] MACAd

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 07:18:07PM +0100, Brian wrote: > On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > > Yes. You've now seen direct evidence of the lie. I guess I won't need > > to post links to the wiki articles that say the same thing you've already > > observed. > > I would be

Re: Predictable Network Interface Names

On Wed 30 Mar 2022 at 13:32:53 -0400, Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > > as I can read here [1] network names should be stable. > > (Stable interface names even when hardware is added or removed) > > > [1] > > https://www.freedesktop.org/wiki/Softwa

Re: Predictable Network Interface Names

On Wed, Mar 30, 2022 at 05:35:12PM +0200, basti wrote: > as I can read here [1] network names should be stable. > (Stable interface names even when hardware is added or removed) > [1] > https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Sorry, but you've been lie

Predictable Network Interface Names

Hello, as I can read here [1] network names should be stable. (Stable interface names even when hardware is added or removed) First of all I have multiple PCIe NIC in a server. What I see now is: When I add or remove a PCIe card (USB card) the name is changed from enp5s3 to enp6s3 and back

Re: Predictable Network Interface Names

mportant here. > With Predictable Network Interface Names enabled, it should be possible, to > do this automated. It is now, once they fixed it. > I got this 'ens' part, no problem. But where do the numbers come from? Long story short, VMWare NICs were horribly broken in regards to P

Predictable Network Interface Names

Hi ML members, I have a bunch of machines, all virtual, where I have to swap the NIC type. Three or four NIC's per host, e1000 to vmxnet3 for those who may care about. With Predictable Network Interface Names enabled, it should be possible, to do this automated. Not being lazy, I'v

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Hi Michael, great, that was the problem, removed the file, recreated the initramfs, now it works like a charm. Thanks a lot for the help. Patrick > Am 27.07.2017 um 21:29 schrieb Michael Biebl : > > Am 27.07.2017 um 20:21 schrieb Patrick Flaig: >> Sure, this is the content: >> >> cat /tmp/foo

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 20:21 schrieb Patrick Flaig: > Sure, this is the content: > > cat /tmp/foo/lib/systemd/network/99-default.link Thanks Patrick. So, it seems the udev maintainer scripts detected at virtualized environment which causes the following code to be triggered: https://anonscm.debian.or

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Sure, this is the content: cat /tmp/foo/lib/systemd/network/99-default.link # This machine is most likely a virtualized guest, where the old persistent # network interface mechanism (75-persistent-net-generator.rules) did not work. # This file disables /lib/systemd/network/99-default.link to avoi

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 19:50 schrieb Patrick Flaig: > Oh my fault, 99-default.link is available, I checked the wrong folder. > The file is containing some text, saying that the machine is most likely a > virtualized guest. Can you paste the contents verbatim. -- Why is it that all of the instruments

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Oh my fault, 99-default.link is available, I checked the wrong folder. The file is containing some text, saying that the machine is most likely a virtualized guest. > Am 27.07.2017 um 19:28 schrieb Michael Biebl : > > Am 27.07.2017 um 18:55 schrieb debian-li...@patschie.de: > >>> Am 27.07.2017

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 18:55 schrieb debian-li...@patschie.de: >> Am 27.07.2017 um 18:25 schrieb Michael Biebl : >> lsinitramfs /boot/initrd.img-$(uname -r) | grep 99-default.link >> lib/systemd/network/99-default.link > Missing Odd. Do you have that file on the host system? Can you check with debsums

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

> Am 27.07.2017 um 18:25 schrieb Michael Biebl : > > Am 27.07.2017 um 18:04 schrieb debian-li...@patschie.de: >> Hi Michael, >> >> I forgot to mention that I also recreated the initramfs: >> after several tries just to update it, I deleted the initramfs and recreated >> it completely. >> But s

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

> Am 27.07.2017 um 18:25 schrieb Michael Biebl : > > Am 27.07.2017 um 18:04 schrieb debian-li...@patschie.de: >> Hi Michael, >> >> I forgot to mention that I also recreated the initramfs: >> after several tries just to update it, I deleted the initramfs and recreated >> it completely. >> But s

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Thanks, confirmed, the initrd doesn’t contain any udev rule files in /etc/udev/rules.d > Am 27.07.2017 um 18:11 schrieb Greg Wooledge : > > On Thu, Jul 27, 2017 at 06:04:49PM +0200, debian-li...@patschie.de wrote: >> Is there a way to manually check the contents of the initramfs, just to make

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 18:04 schrieb debian-li...@patschie.de: > Hi Michael, > > I forgot to mention that I also recreated the initramfs: > after several tries just to update it, I deleted the initramfs and recreated > it completely. > But still the same effect. > > Is there a way to manually check t

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

On Thu, Jul 27, 2017 at 06:04:49PM +0200, debian-li...@patschie.de wrote: > Is there a way to manually check the contents of the initramfs, just to make > sure that the 70-persistent-net.rules isn’t there? mkdir /tmp/foo && cd /tmp/foo && unmkinitramfs /boot/initrd.whatever (The old way of just

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

-net.rules isn’t there? Patrick > Am 27.07.2017 um 17:57 schrieb Michael Biebl : > > Hi Patrick > > Am 27.07.2017 um 17:15 schrieb debian-li...@patschie.de: >> Hi, >> >> I’m running into some troubles to enable the predictable network interface >>

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Hi Patrick Am 27.07.2017 um 17:15 schrieb debian-li...@patschie.de: > Hi, > > I’m running into some troubles to enable the predictable network interface > names for a system upgraded from Jessie. > > What I figured out so far: > Setting net.ifnames=1 on the kernel command

Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Hi, I’m running into some troubles to enable the predictable network interface names for a system upgraded from Jessie. What I figured out so far: Setting net.ifnames=1 on the kernel command line doesn’t help and seems no longer to be supported parameter (at least "sysctl - a" doesn

Re: Predictable Network Interface Names prevents WiFi connections.

Hi Miguel, Did you ever get an answer about this? I can't get Network Manager (from KDE) to connect if the predictable network interface names are enabled. Cheers, Marcos

Re: how to compute predictable network interface names?

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

Re: how to compute predictable network interface names?

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 su

Re: how to compute predictable network interface names?

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 matter

Re: how to compute predictable network interface names?

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 ove

Re: how to compute predictable network interface names?

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 crea

Re: how to compute predictable network interface names?

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 clone).

Re: how to compute predictable network interface names?

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 /etc/network/interface

Re: how to compute predictable network interface names?

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_ you'v

Re: how to compute predictable network interface names?

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 by

how to compute predictable network interface names?

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 % predict_n

Predictable Network Interface Names prevents WiFi connections.

Hello. I'm having a weird problem with my Debian testing installation. I use KDE Plasma 5 and NetworkManager in a up-to-date system. The problem is I can't connect to any wifi if Predictable Network Interface Names are in use. I can see all wireless networks in Network Manager, so I s