Re: [PLUG] adding network name alias

2021-02-16 Thread Paul Heinlein
On Mon, 15 Feb 2021, Keith Lofstrom wrote: On Sun, Feb 14, 2021 at 09:45:05PM -0800, Russell Senior wrote: I can understand it making sense in the context of a server with multiple interfaces. We used to have occasional problems with ethernet enumeration when we were using recycled PCs as

Re: [PLUG] adding network name alias

2021-02-15 Thread Ben Koenig
On 2/15/21 6:46 PM, Keith Lofstrom wrote: I can remember the ancient days, when source-empowered users made Linux do what they wanted, rather than Linux making users conform to the changing whims of a powerful and unaccountable elite. I don't mind people pissing in their soup until they like

Re: [PLUG] adding network name alias

2021-02-15 Thread Russell Senior
in the output of "ip link help", I see: ip link property add dev DEVICE [ altname NAME .. ] ip link property del dev DEVICE [ altname NAME .. ] That looks like what maybe you are looking for. On Mon, Feb 15, 2021 at 6:59 PM Russell Senior wrote: > > I don't see the altname in a Ubuntu

Re: [PLUG] adding network name alias

2021-02-15 Thread Russell Senior
I don't see the altname in a Ubuntu 20.04 with a 5.4.x kernel. On Mon, Feb 15, 2021 at 6:59 PM Russell Senior wrote: > > Fwiw, on my Ubuntu 20.04 with the hwe kernel (5.8.x), I see an altname: > > russell@frieda:~$ ip link show dev enp4s0 > > 3: eth1: mtu 1500 qdisc fq_codel > state DOWN mode

Re: [PLUG] adding network name alias

2021-02-15 Thread Russell Senior
Fwiw, on my Ubuntu 20.04 with the hwe kernel (5.8.x), I see an altname: russell@frieda:~$ ip link show dev enp4s0 3: eth1: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 00:23:54:xx:xx:xx brd ff:ff:ff:ff:ff:ff altname enp4s0 So, what you are asking

Re: [PLUG] adding network name alias

2021-02-15 Thread Keith Lofstrom
On Sun, Feb 14, 2021 at 09:45:05PM -0800, Russell Senior wrote: > I can understand it making sense in the context of a server with > multiple interfaces. We used to have occasional problems with ethernet > enumeration when we were using recycled PCs as gateway routers. I just > don't see why that

Re: [PLUG] adding network name alias

2021-02-15 Thread Rich Shepard
On Mon, 15 Feb 2021, Ben Koenig wrote: They are trying to make sure that ethernet ports are predictably labeled. This means they want to look at the back of the hardware and identify eth0 without the use of software. Most devices are assigned labels in linux as they are found and the order in

Re: [PLUG] adding network name alias

2021-02-15 Thread Ben Koenig
They are trying to make sure that ethernet ports are predictably labeled. This means they want to look at the back of the hardware and identify eth0 without the use of software. Most devices are assigned labels in linux as they are found and the order in which they are found is often different

Re: [PLUG] adding network name alias

2021-02-15 Thread Rich Shepard
On Sun, 14 Feb 2021, Ben Koenig wrote: Problem remains unsolved. Whoever funded the development of this feature should probably ask for their money back. Unless of course their goal was to destabilize the Linux platform, in which case, Good Job! Ben, As a curious non-computer professional I

Re: [PLUG] adding network name alias

2021-02-14 Thread Russell Senior
I can understand it making sense in the context of a server with multiple interfaces. We used to have occasional problems with ethernet enumeration when we were using recycled PCs as gateway routers. I just don't see why that kind of corner case drove adoption for a problem that didn't exist for

Re: [PLUG] adding network name alias

2021-02-14 Thread Ben Koenig
Just some thoughts... If I'm reading the document on freedesktop.org correctly then this new system does not actually solve the problem it claims to be solving. Specifically this part here: "...The following different naming schemes for network interfaces are now supported by udev natively:

Re: [PLUG] adding network name alias

2021-02-14 Thread Chuck Hast
I too have never figured out what was gained by going to "predictable names" as far as I am concerned it is the definition of oxymoron. I always knew what eth0 or eth1 or whatever the original names were, these things though on a given machine will USUALLY come up the same but they change from

Re: [PLUG] adding network name alias

2021-02-13 Thread Russell Senior
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ Given the plenitude of schemes (!) that are supported, this system deserves the word "predictable" about as much as USB deserves the word "universal". On Sat, Feb 13, 2021 at 6:28 PM Russell Senior wrote: > > >

Re: [PLUG] adding network name alias

2021-02-13 Thread Russell Senior
> There are ways to rename the interface back to eth0, but > I assume this breaks other things, It doesn't break anything. I routinely turn off the silly "predictable" names. I use the technique of adding: GRUB_CMDLINE_LINUX_DEFAULT="net.ifnames=0" to my /etc/default/grub file, and after

[PLUG] adding network name alias

2021-02-13 Thread Keith Lofstrom
Is there a way to add an alias name for an ethernet interface, while keeping the system assigned name (visible with tools like "ip") ? As I upgrade my machines from ancient distros, one irritation is the renaming of the first and only ethernet interface from the simple name "eth0" to enp6s0 (on