How to rename adapters in network manager applet?
I'm on Mint 20.3 Cinnamon.
I have 3 adapters with the same name.
Image for details https://disk.yandex.by/i/3kFnLWoMQ4NC1w
How to rename network adapters in network manager applet?
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
- Level 1
- Posts: 5
- Joined: Wed Sep 28, 2022 9:08 am
How to rename network adapters in network manager applet?
Last edited by LockBot on Tue Mar 28, 2023 10:00 pm, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: How to rename network adapters in network manager applet?
In the connections window highlight one of the connections,
then click the gear icon at the bottom. You can edit the name there.
then click the gear icon at the bottom. You can edit the name there.
Everything in life was difficult before it became easy.
-
- Level 1
- Posts: 5
- Joined: Wed Sep 28, 2022 9:08 am
Re: How to rename network adapters in network manager applet?
I checked all settings in "network settings" and "network connections" - there are no names as displayed in applet. It is network card name, that system somehow detects (or sets) in deep scripts.
this is my screen to show it is not: https://disk.yandex.ru/i/QLix9Z_nLsxUeA
Could you please give the screenshot?
this is my screen to show it is not: https://disk.yandex.ru/i/QLix9Z_nLsxUeA
Could you please give the screenshot?
Re: How to rename network adapters in network manager applet?
andrew+1+2 wrote: ⤴Wed Sep 28, 2022 9:22 am How to rename adapters in network manager applet?
I'm on Mint 20.3 Cinnamon.
To post essential details about your setup: Plug in all relevant dongles, accessories, and peripherals. Then
Open a Terminal (ctrl-alt-T), then copy-and-paste the following long line of green text into the Terminal window, then tap Enter...
Code: Select all
C=code];echo "[$C`inxi -Fxxxmprzc0 --slots;mokutil --sb-state;cat /proc/cmdline;dkms status;ifconfig 2>&1;cat /etc/network/interfaces;lsusb;lsblk -fir;lspci -nnk`[/$C"|xed -
Within a moment, xed text editor pops open, showing technical data useful for others to analyze PC & peripheral issues.
Copy-and-paste everything from xed into a Reply here. < The required
[code]
tags have been added for you />Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
-
- Level 1
- Posts: 5
- Joined: Wed Sep 28, 2022 9:08 am
Re: How to rename network adapters in network manager applet?
The details with my setup
Code: Select all
[System: Kernel: 5.4.0-100-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1
dm: LightDM 1.30.0 Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal
Machine: Type: Vmware System: VMware product: VMware Virtual Platform v: N/A serial: <filter> Chassis: No Enclosure type: 1
serial: <filter>
Mobo: Intel model: 440BX Desktop Reference Platform serial: <filter> BIOS: Phoenix v: 6.00 date: 07/22/2020
Memory: RAM: total: 15.60 GiB used: 7.65 GiB (49.0%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Quad Core model: Intel Core i7-8700 bits: 64 type: MCP arch: Kaby Lake rev: A L2 cache: 12.0 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 25535
Speed: 3192 MHz min/max: N/A Core speeds (MHz): 1: 3192 2: 3192 3: 3192 4: 3192
Graphics: Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.15.0.0 bus ID: 00:0f.0 chip ID: 15ad:0405
Display: x11 server: X.Org 1.20.13 driver: vmware unloaded: fbdev,modesetting,vesa resolution: 1920x1198~60Hz
OpenGL: renderer: SVGA3D; build v: 3.3 Mesa 21.2.6 direct render: Yes
Audio: Device-1: Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371 v: kernel bus ID: 02:02.0
chip ID: 1274:1371
Sound Server: ALSA v: k5.4.0-100-generic
Network: Device-1: Intel 82371AB/EB/MB PIIX4 ACPI vendor: VMware Virtual Machine type: network bridge driver: N/A port: 1060
bus ID: 00:07.3 chip ID: 8086:7113
Device-2: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000 v: 7.3.21-k8-NAPI
port: 2000 bus ID: 02:01.0 chip ID: 8086:100f
IF: ens33 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000 v: 7.3.21-k8-NAPI
port: 2080 bus ID: 02:06.0 chip ID: 8086:100f
IF: ens38 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-4: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000 v: 7.3.21-k8-NAPI
port: 20c0 bus ID: 02:07.0 chip ID: 8086:100f
IF: ens39 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: br-04f1297e728c state: down mac: <filter>
IF-ID-2: br-0e9cccb0bca0 state: down mac: <filter>
IF-ID-3: br-408a35fd0780 state: down mac: <filter>
IF-ID-4: br-53c96bfa2d01 state: down mac: <filter>
IF-ID-5: br-a7bccf257c6a state: down mac: <filter>
IF-ID-6: br-b2c6bd5f2ac3 state: down mac: <filter>
IF-ID-7: br-be4c4f67edf8 state: up speed: N/A duplex: N/A mac: <filter>
IF-ID-8: br-c497d6a5ef79 state: up speed: N/A duplex: N/A mac: <filter>
IF-ID-9: docker0 state: down mac: <filter>
IF-ID-10: veth3433104 state: up speed: 10000 Mbps duplex: full mac: <filter>
IF-ID-11: veth357b7ee state: up speed: 10000 Mbps duplex: full mac: <filter>
IF-ID-12: veth4723321 state: up speed: 10000 Mbps duplex: full mac: <filter>
IF-ID-13: vethbb1db56 state: up speed: 10000 Mbps duplex: full mac: <filter>
IF-ID-14: vethe4a179d state: up speed: 10000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 150.00 GiB used: 104.41 GiB (69.6%)
ID-1: /dev/sda vendor: VMware model: Virtual S size: 150.00 GiB serial: N/A rev: 1.0 scheme: MBR
Partition: ID-1: / size: 146.15 GiB used: 104.41 GiB (71.4%) fs: ext4 dev: /dev/sda5
ID-2: /boot/efi size: 511.0 MiB used: 4 KiB (0.0%) fs: vfat dev: /dev/sda1
Sensors: Message: No sensors data was found. Is sensors configured?
Repos: No active apt repos in: /etc/apt/sources.list
No active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
Active apt repos in: /etc/apt/sources.list.d/docker.list
1: deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu focal stable
Active apt repos in: /etc/apt/sources.list.d/nodesource.list
1: deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x focal main
2: deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.x focal main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http://packages.linuxmint.com una main upstream import backport #id:linuxmint_main
2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http://archive.canonical.com/ubuntu/ focal partner
Active apt repos in: /etc/apt/sources.list.d/ondrej-nginx-focal.list
1: deb http://ppa.launchpad.net/ondrej/nginx/ubuntu focal main
Active apt repos in: /etc/apt/sources.list.d/ondrej-php-focal.list
1: deb http://ppa.launchpad.net/ondrej/php/ubuntu focal main
Info: Processes: 392 Uptime: 14d 7h 53m Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Shell: bash
v: 5.0.17 running in: gnome-terminal inxi: 3.0.38
BOOT_IMAGE=/boot/vmlinuz-5.4.0-100-generic root=UUID=56bd1c5e-c982-413d-aa32-9ed17ae45f30 ro quiet splash
br-04f1297e728c: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.21.0.1 netmask 255.255.0.0 broadcast 172.21.255.255
inet6 fe80::42:bff:fe62:4dd4 prefixlen 64 scopeid 0x20<link>
ether 02:42:0b:62:4d:d4 txqueuelen 0 (Ethernet)
RX packets 302 bytes 16395 (16.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 309 bytes 1755732 (1.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-0e9cccb0bca0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255
ether 02:42:e5:60:7f:2c txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-408a35fd0780: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.23.0.1 netmask 255.255.0.0 broadcast 172.23.255.255
inet6 fe80::42:9dff:fecf:5f42 prefixlen 64 scopeid 0x20<link>
ether 02:42:9d:cf:5f:42 txqueuelen 0 (Ethernet)
RX packets 73820 bytes 59018349 (59.0 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 87956 bytes 54288261 (54.2 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-53c96bfa2d01: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255
inet6 fe80::42:67ff:fe5e:e892 prefixlen 64 scopeid 0x20<link>
ether 02:42:67:5e:e8:92 txqueuelen 0 (Ethernet)
RX packets 7 bytes 248 (248.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 63 bytes 7493 (7.4 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-a7bccf257c6a: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.24.0.1 netmask 255.255.0.0 broadcast 172.24.255.255
inet6 fe80::42:84ff:fe02:e5dd prefixlen 64 scopeid 0x20<link>
ether 02:42:84:02:e5:dd txqueuelen 0 (Ethernet)
RX packets 221874646 bytes 55261860690 (55.2 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 218283136 bytes 55881313046 (55.8 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-b2c6bd5f2ac3: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.20.0.1 netmask 255.255.0.0 broadcast 172.20.255.255
ether 02:42:79:4f:15:e3 txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-be4c4f67edf8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.25.0.1 netmask 255.255.0.0 broadcast 172.25.255.255
inet6 fe80::42:a9ff:fe92:5eee prefixlen 64 scopeid 0x20<link>
ether 02:42:a9:92:5e:ee txqueuelen 0 (Ethernet)
RX packets 823584 bytes 1192930830 (1.1 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1142793 bytes 180180510 (180.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
br-c497d6a5ef79: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 172.22.0.1 netmask 255.255.0.0 broadcast 172.22.255.255
inet6 fe80::42:cdff:fee4:7580 prefixlen 64 scopeid 0x20<link>
ether 02:42:cd:e4:75:80 txqueuelen 0 (Ethernet)
RX packets 8023 bytes 2648129 (2.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10996 bytes 980893 (980.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
inet6 fe80::42:d4ff:feb4:baf2 prefixlen 64 scopeid 0x20<link>
ether 02:42:d4:b4:ba:f2 txqueuelen 0 (Ethernet)
RX packets 108893 bytes 5341319 (5.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 145226 bytes 399502609 (399.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.182.128 netmask 255.255.255.0 broadcast 192.168.182.255
inet6 fe80::933d:65de:1f57:2cd4 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:6c:6d:55 txqueuelen 1000 (Ethernet)
RX packets 7633270 bytes 10357119712 (10.3 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2719246 bytes 306148943 (306.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens38: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.88.90 netmask 255.255.255.0 broadcast 192.168.88.255
inet6 fe80::ebd5:6878:4c0f:bddc prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:6c:6d:5f txqueuelen 1000 (Ethernet)
RX packets 1935046 bytes 1009000749 (1.0 GB)
RX errors 0 dropped 613 overruns 0 frame 0
TX packets 1805473 bytes 1626468357 (1.6 GB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens39: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.101.90 netmask 255.255.255.0 broadcast 192.168.101.255
inet6 fe80::1f8:9360:449e:6e68 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:6c:6d:69 txqueuelen 1000 (Ethernet)
RX packets 722018 bytes 115534412 (115.5 MB)
RX errors 0 dropped 618 overruns 0 frame 0
TX packets 42135 bytes 4183951 (4.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 454543 bytes 51668433 (51.6 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 454543 bytes 51668433 (51.6 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth3433104: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::bcb5:f0ff:fe9a:7ad4 prefixlen 64 scopeid 0x20<link>
ether be:b5:f0:9a:7a:d4 txqueuelen 0 (Ethernet)
RX packets 788 bytes 288762 (288.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1266 bytes 132888 (132.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth4723321: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::5c09:15ff:febe:1ce2 prefixlen 64 scopeid 0x20<link>
ether 5e:09:15:be:1c:e2 txqueuelen 0 (Ethernet)
RX packets 101481 bytes 17774609 (17.7 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 119134 bytes 10500318 (10.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
veth357b7ee: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::2034:89ff:fe56:43f5 prefixlen 64 scopeid 0x20<link>
ether 22:34:89:56:43:f5 txqueuelen 0 (Ethernet)
RX packets 42569 bytes 191890248 (191.8 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 96099 bytes 7525904 (7.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vethbb1db56: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::58c1:2bff:fe8a:91be prefixlen 64 scopeid 0x20<link>
ether 5a:c1:2b:8a:91:be txqueuelen 0 (Ethernet)
RX packets 44489 bytes 7114455 (7.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 46772 bytes 6787010 (6.7 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
vethe4a179d: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::dc69:9fff:fe40:b8d5 prefixlen 64 scopeid 0x20<link>
ether de:69:9f:40:b8:d5 txqueuelen 0 (Ethernet)
RX packets 107470 bytes 9405183 (9.4 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 92896 bytes 17016271 (17.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
sda1 vfat 0391-3F4D 511M 0% /boot/efi
sda2
sda5 ext4 56bd1c5e-c982-413d-aa32-9ed17ae45f30 34,3G 71% /
sr0
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge [8086:7190] (rev 01)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Kernel driver in use: agpgart-intel
00:01.0 PCI bridge [0604]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge [8086:7191] (rev 01)
00:07.0 ISA bridge [0601]: Intel Corporation 82371AB/EB/MB PIIX4 ISA [8086:7110] (rev 08)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
00:07.1 IDE interface [0101]: Intel Corporation 82371AB/EB/MB PIIX4 IDE [8086:7111] (rev 01)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Kernel driver in use: ata_piix
Kernel modules: pata_acpi
00:07.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Kernel modules: i2c_piix4
00:07.7 System peripheral [0880]: VMware Virtual Machine Communication Interface [15ad:0740] (rev 10)
Subsystem: VMware Virtual Machine Communication Interface [15ad:0740]
Kernel driver in use: vmw_vmci
Kernel modules: vmw_vmci
00:0f.0 VGA compatible controller [0300]: VMware SVGA II Adapter [15ad:0405]
Subsystem: VMware SVGA II Adapter [15ad:0405]
Kernel driver in use: vmwgfx
Kernel modules: vmwgfx
00:10.0 SCSI storage controller [0100]: Broadcom / LSI 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI [1000:0030] (rev 01)
Subsystem: VMware LSI Logic Parallel SCSI Controller [15ad:1976]
Kernel driver in use: mptspi
Kernel modules: mptspi
00:11.0 PCI bridge [0604]: VMware PCI bridge [15ad:0790] (rev 02)
00:15.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:15.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:15.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:15.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:15.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:15.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:15.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:15.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:16.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:17.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.0 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.1 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.2 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.3 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.4 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.5 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.6 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
00:18.7 PCI bridge [0604]: VMware PCI Express Root Port [15ad:07a0] (rev 01)
Kernel driver in use: pcieport
02:00.0 USB controller [0c03]: VMware USB1.1 UHCI Controller [15ad:0774]
DeviceName: usb
Subsystem: VMware USB1.1 UHCI Controller [15ad:1976]
Kernel driver in use: uhci_hcd
02:01.0 Ethernet controller [0200]: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) [8086:100f] (rev 01)
DeviceName: Ethernet0
Subsystem: VMware PRO/1000 MT Single Port Adapter [15ad:0750]
Kernel driver in use: e1000
Kernel modules: e1000
02:02.0 Multimedia audio controller [0401]: Ensoniq ES1371/ES1373 / Creative Labs CT2518 [1274:1371] (rev 02)
DeviceName: sound
Subsystem: Ensoniq Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI] [1274:1371]
Kernel driver in use: snd_ens1371
Kernel modules: snd_ens1371
02:03.0 USB controller [0c03]: VMware USB2 EHCI Controller [15ad:0770]
DeviceName: ehci
Subsystem: VMware USB2 EHCI Controller [15ad:0770]
Kernel driver in use: ehci-pci
02:05.0 SATA controller [0106]: VMware SATA AHCI controller [15ad:07e0]
DeviceName: sata0
Subsystem: VMware SATA AHCI controller [15ad:07e0]
Kernel driver in use: ahci
Kernel modules: ahci
02:06.0 Ethernet controller [0200]: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) [8086:100f] (rev 01)
DeviceName: Ethernet1
Subsystem: VMware PRO/1000 MT Single Port Adapter [15ad:0750]
Kernel driver in use: e1000
Kernel modules: e1000
02:07.0 Ethernet controller [0200]: Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) [8086:100f] (rev 01)
DeviceName: Ethernet2
Subsystem: VMware PRO/1000 MT Single Port Adapter [15ad:0750]
Kernel driver in use: e1000
Kernel modules: e1000[/
Re: How to rename network adapters in network manager applet?
andrew+1+2 wrote: ⤴Fri Sep 30, 2022 8:42 am The details with my setup
Code: Select all
## ## data from inxi: ## Network: Device-2: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000 v: 7.3.21-k8-NAPI port: 2000 bus ID: 02:01.0 chip ID: 8086:100f IF: ens33 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-3: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000 v: 7.3.21-k8-NAPI port: 2080 bus ID: 02:06.0 chip ID: 8086:100f IF: ens38 state: up speed: 1000 Mbps duplex: full mac: <filter> Device-4: Intel 82545EM Gigabit Ethernet vendor: VMware PRO/1000 MT Single Port driver: e1000 v: 7.3.21-k8-NAPI port: 20c0 bus ID: 02:07.0 chip ID: 8086:100f IF: ens39 state: up speed: 1000 Mbps duplex: full mac: <filter> ## ## data from ifconfig: ## ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.182.128 netmask 255.255.255.0 broadcast 192.168.182.255 inet6 fe80::933d:65de:1f57:2cd4 prefixlen 64 scopeid 0x20<link> ether 00:0c:29:6c:6d:55 txqueuelen 1000 (Ethernet) RX packets 7633270 bytes 10357119712 (10.3 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2719246 bytes 306148943 (306.1 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens38: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.88.90 netmask 255.255.255.0 broadcast 192.168.88.255 inet6 fe80::ebd5:6878:4c0f:bddc prefixlen 64 scopeid 0x20<link> ether 00:0c:29:6c:6d:5f txqueuelen 1000 (Ethernet) RX packets 1935046 bytes 1009000749 (1.0 GB) RX errors 0 dropped 613 overruns 0 frame 0 TX packets 1805473 bytes 1626468357 (1.6 GB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens39: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.101.90 netmask 255.255.255.0 broadcast 192.168.101.255 inet6 fe80::1f8:9360:449e:6e68 prefixlen 64 scopeid 0x20<link> ether 00:0c:29:6c:6d:69 txqueuelen 1000 (Ethernet) RX packets 722018 bytes 115534412 (115.5 MB) RX errors 0 dropped 618 overruns 0 frame 0 TX packets 42135 bytes 4183951 (4.1 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ##
Since each of the three adapters can be identified by its Ethernet MAC address ...
ens33
00:0c:29:6c:6d:55
ens38
00:0c:29:6c:6d:5f
ens39
00:0c:29:6c:6d:69
... as well as port and bus ID ...
port:
2000
bus ID: 02:01.0
port:
2080
bus ID: 02:06.0
port:
20c0
bus ID: 02:07.0
... these could be used to create udev rules to define unique names. See Network Configuration > Change interface name.
Alternatively, there's the systemd-networkd service. See Systemd-networkd > Renaming an interface.
Linux Mint 21 Vanessa, MATE 1.26.0, kernel 5.15.0*, Dell 2-in-1
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
AMD Ryzen 7 5825U / Barcelo iGPU - 14" WUXGA Touchscreen
MediaTek MT7921 WiFi-6 BT-5.2; 32GB DDR4@3200MHz; XPG 2TB-NVMe
-
- Level 1
- Posts: 5
- Joined: Wed Sep 28, 2022 9:08 am
Re: How to rename network adapters in network manager applet?
@hglee, thank you for the advice. I'm still trying to fix, but with no luck.
The udev rules does something, but nothing changed yet. The systemd interface name change does nothing visible. I'll try study docs more.
I think I'm in one step to success. The screenshot with details. https://disk.yandex.ru/i/C9v5JZ3hPNvXow
The udev rules does something, but nothing changed yet. The systemd interface name change does nothing visible. I'll try study docs more.
I think I'm in one step to success. The screenshot with details. https://disk.yandex.ru/i/C9v5JZ3hPNvXow
-
- Level 1
- Posts: 5
- Joined: Wed Sep 28, 2022 9:08 am
Re: How to rename network adapters in network manager applet?
It seems the change I need is placed within
The applet uses nm_device_get_description() for menu items list. So I need to change the network cards vendor name or somehow make it "unknown" to force draw the network interface name here.
Code: Select all
/**
* nm_device_get_description:
* @device: an #NMDevice
*
* Gets a description of @device, based on its vendor and product names.
*
* Returns: a description of @device. If either the vendor or the
* product name is unknown, this returns the interface name.
*/
const char *
nm_device_get_description(NMDevice *device)