Fedora 37: How to rename and set a custom Network interface Name with NetworkManager and nmcli

[Dario Lesca]

I have two network device named ens192 and  ens224

2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
    link/ether 00:0c:29:e6:6d:d7 brd ff:ff:ff:ff:ff:ff
3: ens224: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group
default qlen 1000
    link/ether 00:0c:29:e6:6d:e1 brd ff:ff:ff:ff:ff:ff

It's possible to rename it with a logical name like LAN and WAN with
nmcli?

I have found this howto:
https://www.thegeekdiary.com/how-to-set-a-custom-interface-name-with-netw...

But seem not work into Fedora 37.

If it's possible, what is the best way to set this name?

Many thanks

-- 
Dario Lesca
(inviato dal mio Linux Fedora 37 Workstation)

[Jeffrey Walton]

On Mon, Dec 19, 2022 at 8:48 AM Dario Lesca <d.lesca(a)solinos.it&gt; wrote:
>  I have two network device named ens192 and  ens224
>
>  2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
> default qlen 1000
>      link/ether 00:0c:29:e6:6d:d7 brd ff:ff:ff:ff:ff:ff
>  3: ens224: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group
> default qlen 1000
>      link/ether 00:0c:29:e6:6d:e1 brd ff:ff:ff:ff:ff:ff
>
>  It's possible to rename it with a logical name like LAN and WAN with
>  nmcli? 
I think you have to use a udev rule nowadays. I don't think you can
use nmcli, but I am not a nmcli expert.

>  I have found this howto:
>
> https://www.thegeekdiary.com/how-to-set-a-custom-interface-name-with-netw...
>
>  But seem not work into Fedora 37.
>
>  If it's possible, what is the best way to set this name? 
Use a udev rule, like
https://enterprise-support.nvidia.com/s/article/howto-change-network-inte...

Jeff

[t_pol]

Hi,

I had the same prob.

Created 2 files in /etc/systemd/network/

	10-persistent-lan1.link
	10-persistent-lan2.link

with the following contents :

[Match]
MACAddress=xx:xx:xx:xx:xx:xx
[Link]
Name=myname

it works.

Hope this is useful for you.

Ciao
Angelo 


On Mon, 19 Dec 2022 14:48:19 +0100
Dario Lesca <d.lesca(a)solinos.it&gt; wrote:

>  I have two network device named ens192 and  ens224
>  
>  2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state
>  UP group default qlen 1000 link/ether 00:0c:29:e6:6d:d7 brd
>  ff:ff:ff:ff:ff:ff 3: ens224: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu
>  1500 qdisc mq state DOWN group default qlen 1000 link/ether
>  00:0c:29:e6:6d:e1 brd ff:ff:ff:ff:ff:ff
>  
>  It's possible to rename it with a logical name like LAN and WAN with
>  nmcli?
>  
>  I have found this howto:
>
> https://www.thegeekdiary.com/how-to-set-a-custom-interface-name-with-netw...
>  
>  But seem not work into Fedora 37.
>  
>  If it's possible, what is the best way to set this name?
>  
>  Many thanks
>

[Dario Lesca]

Il giorno lun, 19/12/2022 alle 17.49 +0100, t_pol ha scritto:
>  Created 2 files in /etc/systemd/network/
>  
>          10-persistent-lan1.link
>          10-persistent-lan2.link
>  
>  with the following contents :
>  
>  [Match]
>  MACAddress=xx:xx:xx:xx:xx:xx
>  [Link]
>  Name=myname
>  
>  it works.
>  
>  Hope this is useful for you. 
Yes, this is the only Network Manager modern way I have found to fix
and set custom network device name. 

I have use this method 

Thanks

>  Create .link files in /etc/systemd/network/, that choose an explicit
>  name or a better naming scheme for one, some, or all of your
>  interfaces.
>  For example:
>  
>  cat > /etc/systemd/network/10-ether0.link << "EOF"
>  [Match]
>  # Change the MAC address as appropriate for your network device
>  MACAddress=12:34:45:78:90:AB
>  
>  [Link]
>  Name=ether0
>  EOF            
>               
http://junyelee.blogspot.com/2020/12/apparmor.html

-- 
Dario Lesca
(inviato dal mio Linux Fedora 37 Workstation)

[Jon LaBadie]

On Mon, Dec 19, 2022 at 05:49:10PM +0100, t_pol wrote:
> Hi,
>
> I had the same prob.
>
> Created 2 files in /etc/systemd/network/
>
> 	10-persistent-lan1.link
> 	10-persistent-lan2.link
>
> with the following contents :
>
> [Match]
> MACAddress=xx:xx:xx:xx:xx:xx
> [Link]
> Name=myname
>
> it works.
>
> Hope this is useful for you.
>
> Ciao
> Angelo
>  
Do the new names ("myname" in the above) become
replacements or alternatives to the old device
names.  I.e. must I modify any current scripts
or config files that use the old names?  Or can
either name be used.

jl

-- 
Jon H. LaBadie                  jonfu(a)jgcomp.com

[Samuel Sieb]

On 12/19/22 14:25, Jon LaBadie wrote:
>  Do the new names ("myname" in the above) become
>  replacements or alternatives to the old device
>  names.  I.e. must I modify any current scripts
>  or config files that use the old names?  Or can
>  either name be used. 
They are replacements.  You can only use the new name.

[Samuel Sieb]

On 12/19/22 05:48, Dario Lesca wrote:
>  I have two network device named ens192 and  ens224
>  
>  2: ens192: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
> default qlen 1000
>       link/ether 00:0c:29:e6:6d:d7 brd ff:ff:ff:ff:ff:ff
>  3: ens224: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group
> default qlen 1000
>       link/ether 00:0c:29:e6:6d:e1 brd ff:ff:ff:ff:ff:ff
>  
>  It's possible to rename it with a logical name like LAN and WAN with
>  nmcli? 
I only have examples from the legacy ifcfg files right now, but it looks 
like:
DEVICE=myname
PHYSDEV=enp7s0

The nmcli property appears to be "connection.interface-name".