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

Re: Predictable Network Interface Names

Hi. On Wed, Aug 15, 2018 at 04:46:13PM +0200, Martin wrote: > 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. vmxnet3 is what's important here. > With Predicta

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