Benjamin_Loison/linux
1
0
Code Issues 92 Packages Projects Wiki

Retrieve Ethernet network name #100

New Issue
Open
opened 2026-05-19 10:57:32 +02:00 by Benjamin_Loison · 5 comments
Benjamin_Loison commented 2026-05-19 10:57:32 +02:00
Owner
Copy Link
Copy Source

I have verified issues of this repository, my Debian and Cinnamon forks.

DuckDuckGo and Google search Linux get Ethernet name.

Google search Linux get Ethernet network name.

https://chat.mistral.ai/chat/e8e0c4a6-311c-4bf3-abc5-2cc80da39801

On Debian 13 GNOME Pegasus:

nmcli connection show
Output: 
NAME                UUID                                  TYPE      DEVICE  
br0                 0d86f5c7-9be4-46fa-aae8-c0d405ace5ec  bridge    br0
docker0             7e678c50-108d-4253-b59c-76b1e444e6d2  bridge    docker0
lo                  40f0be52-d89d-4267-88f2-2b5eaf6dc928  loopback  lo
lxcbr0              8a0d9f2a-1928-4618-a369-3241b0e69d06  bridge    lxcbr0
virbr0              effa35ce-fa4d-4542-8811-04bb64988e04  bridge    virbr0
vnet0               03e85cb7-fdd1-4a15-801e-2552dc4b952a  tun       vnet0
Wired connection 1  8cad3de0-3b1e-4820-a3fd-ad490675dea5  ethernet  --

I don't remember if I already noticed the Ethernet network name.

ip link show enp0s31f6
Output: 
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP mode DEFAULT group default qlen 1000
    link/ether 1c:XX:XX:XX:XX:df brd ff:ff:ff:ff:ff:ff
    altname enx1cXXXXXXXXdf
I have verified issues of this repository, my Debian and Cinnamon forks. DuckDuckGo and Google search *Linux get Ethernet name*. Google search *Linux get Ethernet network name*. https://chat.mistral.ai/chat/e8e0c4a6-311c-4bf3-abc5-2cc80da39801 On Debian 13 GNOME Pegasus: ```bash nmcli connection show ``` <details> <summary>Output:</summary> <pre> NAME UUID TYPE DEVICE <span style="color:green">br0 0d86f5c7-9be4-46fa-aae8-c0d405ace5ec bridge br0</span> <span style="color:green">docker0 7e678c50-108d-4253-b59c-76b1e444e6d2 bridge docker0</span> <span style="color:green">lo 40f0be52-d89d-4267-88f2-2b5eaf6dc928 loopback lo</span> <span style="color:green">lxcbr0 8a0d9f2a-1928-4618-a369-3241b0e69d06 bridge lxcbr0</span> <span style="color:green">virbr0 effa35ce-fa4d-4542-8811-04bb64988e04 bridge virbr0</span> <span style="color:green">vnet0 03e85cb7-fdd1-4a15-801e-2552dc4b952a tun vnet0</span> Wired connection 1 8cad3de0-3b1e-4820-a3fd-ad490675dea5 ethernet -- </pre> </details> I don't remember if I already noticed the Ethernet network name. ```bash ip link show enp0s31f6 ``` <details> <summary>Output:</summary> ``` 2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP mode DEFAULT group default qlen 1000 link/ether 1c:XX:XX:XX:XX:df brd ff:ff:ff:ff:ff:ff altname enx1cXXXXXXXXdf ``` </details>
Benjamin_Loison commented 2026-05-19 10:57:41 +02:00
Author
Owner
Copy Link
Copy Source
nmcli dev wifi show-password

Error: No Wi-Fi device found.
```bash nmcli dev wifi show-password ``` ``` Error: No Wi-Fi device found. ```
Benjamin_Loison commented 2026-05-19 10:59:29 +02:00
Author
Owner
Copy Link
Copy Source
ifconfig enp0s31f6
Output: 
enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 1c:XX:XX:XX:XX:df  txqueuelen 1000  (Ethernet)
        RX packets 6688677  bytes 853473265 (813.9 MiB)
        RX errors 0  dropped 12  overruns 0  frame 0
        TX packets 10176004  bytes 11886169611 (11.0 GiB)
        TX errors 0  dropped 2 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0x92200000-92220000
```bash ifconfig enp0s31f6 ``` <details> <summary>Output:</summary> ``` enp0s31f6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 1c:XX:XX:XX:XX:df txqueuelen 1000 (Ethernet) RX packets 6688677 bytes 853473265 (813.9 MiB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 10176004 bytes 11886169611 (11.0 GiB) TX errors 0 dropped 2 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0x92200000-92220000 ``` </details>
Benjamin_Loison commented 2026-05-19 11:00:47 +02:00
Author
Owner
Copy Link
Copy Source
dmesg

dmesg: read kernel buffer failed: Operation not permitted

sudo dmesg | grep -E '\<eth'
Output: 
[    1.716847] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 1c:XX:XX:XX:XX:df
[    1.716856] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
[    1.716931] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
[    1.873737] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0
[   42.986711] eth0: renamed from vethc950459
```bash dmesg ``` ``` dmesg: read kernel buffer failed: Operation not permitted ``` ```bash sudo dmesg | grep -E '\<eth' ``` <details> <summary>Output:</summary> ``` [ 1.716847] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 1c:XX:XX:XX:XX:df [ 1.716856] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection [ 1.716931] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF [ 1.873737] e1000e 0000:00:1f.6 enp0s31f6: renamed from eth0 [ 42.986711] eth0: renamed from vethc950459 ``` </details>
Benjamin_Loison commented 2026-05-19 11:01:10 +02:00
Author
Owner
Copy Link
Copy Source
/etc/network/interfaces: 
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# Set up interfaces manually, avoiding conflicts with, e.g., network manager
# On 29/12/25 I uncommented the following line to try to solve [Benjamin_Loison/Debian/issues/87](https://codeberg.org/Benjamin_Loison/Debian/issues/87).
# The interface name matches the only Ethernet `ifconfig` one.
# Uncommented both following sections seems to solve the issue, until select other wire interface in GUI, I saw 2 of them.
#iface enp0s31f6 inet manual

# Bridge setup
iface br0 inet dhcp
    bridge_ports enp0s31f6
<details> <summary><code>/etc/network/interfaces</code>:</summary> ``` # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # Set up interfaces manually, avoiding conflicts with, e.g., network manager # On 29/12/25 I uncommented the following line to try to solve [Benjamin_Loison/Debian/issues/87](https://codeberg.org/Benjamin_Loison/Debian/issues/87). # The interface name matches the only Ethernet `ifconfig` one. # Uncommented both following sections seems to solve the issue, until select other wire interface in GUI, I saw 2 of them. #iface enp0s31f6 inet manual # Bridge setup iface br0 inet dhcp bridge_ports enp0s31f6 ``` </details>
Benjamin_Loison commented 2026-05-19 14:16:54 +02:00
Author
Owner
Copy Link
Copy Source
nmcli device show vnet0
Output: 
GENERAL.DEVICE:                         vnet0
GENERAL.TYPE:                           tun
GENERAL.HWADDR:                         FE:XX:XX:XX:XX:1A
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected (externally))
GENERAL.CONNECTION:                     vnet0
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/6
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         fe80::XXXX:XX:XXXX:8b1a/64
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = fe80::/64, nh = ::, mt = 256

resolvectl status vnet0
Output: 
Command 'resolvectl' not found, but can be installed with:
sudo apt install systemd-resolved

command-not-found --ignore-installed resolvectl
Output: 
Command 'resolvectl' not found, but can be installed with:
sudo apt install systemd-resolved

apt show systemd-resolved
Output: 

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Package: systemd-resolved
Version: 257.13-1~deb13u1
Priority: optional
Section: admin
Source: systemd
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Installed-Size: 938 kB
Provides: resolvconf
Depends: libc6 (>= 2.39), libssl3t64 (>= 3.0.0), libsystemd-shared (= 257.13-1~deb13u1), systemd (= 257.13-1~deb13u1), default-dbus-system-bus | dbus-system-bus
Recommends: libnss-myhostname, libnss-resolve, libidn2-0
Suggests: polkitd
Conflicts: resolvconf, systemd (<< 257.4-4~)
Replaces: resolvconf
Homepage: https://systemd.io
Download-Size: 362 kB
APT-Sources: http://deb.debian.org/debian trixie/main amd64 Packages
Description: systemd DNS resolver
 This package provides systemd's DNS resolver and the command line tool to
 manage it.
 .
 Installing this package automatically overwrites /etc/resolv.conf and switches
 it to be managed by systemd-resolved.

sudo apt install -y systemd-resolved
Output: 
Installing:                     
  systemd-resolved

Installing dependencies:
  libnss-resolve

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
  Download size: 503 kB
  Space needed: 1 227 kB / 43,2 GB available

Get:1 http://deb.debian.org/debian trixie/main amd64 systemd-resolved amd64 257.13-1~deb13u1 [362 kB]
Get:2 http://deb.debian.org/debian trixie/main amd64 libnss-resolve amd64 257.13-1~deb13u1 [142 kB]
Fetched 503 kB in 0s (10,0 MB/s)         
Selecting previously unselected package systemd-resolved.
(Reading database ... 406756 files and directories currently installed.)
Preparing to unpack .../systemd-resolved_257.13-1~deb13u1_amd64.deb ...
Unpacking systemd-resolved (257.13-1~deb13u1) ...
Selecting previously unselected package libnss-resolve:amd64.
Preparing to unpack .../libnss-resolve_257.13-1~deb13u1_amd64.deb ...
Unpacking libnss-resolve:amd64 (257.13-1~deb13u1) ...
Setting up systemd-resolved (257.13-1~deb13u1) ...
Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf...
Creating group 'systemd-resolve' with GID 993.
Creating user 'systemd-resolve' (systemd Resolver) with UID 993 and GID 993.
Created symlink '/etc/systemd/system/dbus-org.freedesktop.resolve1.service' → '/usr/lib/systemd/system/systemd-resolved.service'.
Created symlink '/etc/systemd/system/sysinit.target.wants/systemd-resolved.service' → '/usr/lib/systemd/system/systemd-resolved.service'.
Setting up libnss-resolve:amd64 (257.13-1~deb13u1) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for dbus (1.16.2-2) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Scanning processes...                                                                                                                      
Scanning processor microcode...                                                                                                            
Scanning linux images...                                                                                                                   

Running kernel seems to be up-to-date.

The processor microcode seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this host.

time resolvectl status vnet0
Output: 
Failed to get link data for 9: Connection timed out

real	0m25,037s
user	0m0,011s
sys	0m0,000s

time sudo resolvectl status vnet0
Output: 
Failed to get link data for 9: Failed to activate service 'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

real	0m6,306s
user	0m0,004s
sys	0m0,019s

ip route | grep default

default via 192.168.1.1 dev br0

avahi-resolve-address 192.168.1.1

192.168.1.1	livebox.home

nslookup 192.168.1.1

1.1.168.192.in-addr.arpa	name = _gateway.

sudo nmap -sP 192.168.1.1
Output: 
Starting Nmap 7.95 ( https://nmap.org ) at 2026-05-19 14:16 CEST
Nmap scan report for _gateway (192.168.1.1)
Host is up (0.00039s latency).
MAC Address: AC:XX:XX:XX:XX:70 (Ingram Micro Services)
Nmap done: 1 IP address (1 host up) scanned in 1.44 seconds
```bash nmcli device show vnet0 ``` <details> <summary>Output:</summary> ``` GENERAL.DEVICE: vnet0 GENERAL.TYPE: tun GENERAL.HWADDR: FE:XX:XX:XX:XX:1A GENERAL.MTU: 1500 GENERAL.STATE: 100 (connected (externally)) GENERAL.CONNECTION: vnet0 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/6 IP4.GATEWAY: -- IP6.ADDRESS[1]: fe80::XXXX:XX:XXXX:8b1a/64 IP6.GATEWAY: -- IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 256 ``` </details> ```bash resolvectl status vnet0 ``` <details> <summary>Output:</summary> ``` Command 'resolvectl' not found, but can be installed with: sudo apt install systemd-resolved ``` </details> ```bash command-not-found --ignore-installed resolvectl ``` <details> <summary>Output:</summary> ``` Command 'resolvectl' not found, but can be installed with: sudo apt install systemd-resolved ``` </details> ```bash apt show systemd-resolved ``` <details> <summary>Output:</summary> ``` WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Package: systemd-resolved Version: 257.13-1~deb13u1 Priority: optional Section: admin Source: systemd Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org> Installed-Size: 938 kB Provides: resolvconf Depends: libc6 (>= 2.39), libssl3t64 (>= 3.0.0), libsystemd-shared (= 257.13-1~deb13u1), systemd (= 257.13-1~deb13u1), default-dbus-system-bus | dbus-system-bus Recommends: libnss-myhostname, libnss-resolve, libidn2-0 Suggests: polkitd Conflicts: resolvconf, systemd (<< 257.4-4~) Replaces: resolvconf Homepage: https://systemd.io Download-Size: 362 kB APT-Sources: http://deb.debian.org/debian trixie/main amd64 Packages Description: systemd DNS resolver This package provides systemd's DNS resolver and the command line tool to manage it. . Installing this package automatically overwrites /etc/resolv.conf and switches it to be managed by systemd-resolved. ``` </details> ```bash sudo apt install -y systemd-resolved ``` <details> <summary>Output:</summary> ``` Installing: systemd-resolved Installing dependencies: libnss-resolve Summary: Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0 Download size: 503 kB Space needed: 1 227 kB / 43,2 GB available Get:1 http://deb.debian.org/debian trixie/main amd64 systemd-resolved amd64 257.13-1~deb13u1 [362 kB] Get:2 http://deb.debian.org/debian trixie/main amd64 libnss-resolve amd64 257.13-1~deb13u1 [142 kB] Fetched 503 kB in 0s (10,0 MB/s) Selecting previously unselected package systemd-resolved. (Reading database ... 406756 files and directories currently installed.) Preparing to unpack .../systemd-resolved_257.13-1~deb13u1_amd64.deb ... Unpacking systemd-resolved (257.13-1~deb13u1) ... Selecting previously unselected package libnss-resolve:amd64. Preparing to unpack .../libnss-resolve_257.13-1~deb13u1_amd64.deb ... Unpacking libnss-resolve:amd64 (257.13-1~deb13u1) ... Setting up systemd-resolved (257.13-1~deb13u1) ... Converting /etc/resolv.conf to a symlink to /run/systemd/resolve/stub-resolv.conf... Creating group 'systemd-resolve' with GID 993. Creating user 'systemd-resolve' (systemd Resolver) with UID 993 and GID 993. Created symlink '/etc/systemd/system/dbus-org.freedesktop.resolve1.service' → '/usr/lib/systemd/system/systemd-resolved.service'. Created symlink '/etc/systemd/system/sysinit.target.wants/systemd-resolved.service' → '/usr/lib/systemd/system/systemd-resolved.service'. Setting up libnss-resolve:amd64 (257.13-1~deb13u1) ... Processing triggers for man-db (2.13.1-1) ... Processing triggers for dbus (1.16.2-2) ... Processing triggers for libc-bin (2.41-12+deb13u3) ... Scanning processes... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. ``` </details> ```bash time resolvectl status vnet0 ``` <details> <summary>Output:</summary> ``` Failed to get link data for 9: Connection timed out real 0m25,037s user 0m0,011s sys 0m0,000s ``` </details> ```bash time sudo resolvectl status vnet0 ``` <details> <summary>Output:</summary> ``` Failed to get link data for 9: Failed to activate service 'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms) real 0m6,306s user 0m0,004s sys 0m0,019s ``` </details> ```bash ip route | grep default ``` ``` default via 192.168.1.1 dev br0 ``` ```bash avahi-resolve-address 192.168.1.1 ``` ``` 192.168.1.1 livebox.home ``` ```bash nslookup 192.168.1.1 ``` ``` 1.1.168.192.in-addr.arpa name = _gateway. ``` ```bash sudo nmap -sP 192.168.1.1 ``` <details> <summary>Output:</summary> ``` Starting Nmap 7.95 ( https://nmap.org ) at 2026-05-19 14:16 CEST Nmap scan report for _gateway (192.168.1.1) Host is up (0.00039s latency). MAC Address: AC:XX:XX:XX:XX:70 (Ingram Micro Services) Nmap done: 1 IP address (1 host up) scanned in 1.44 seconds ``` </details>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Benjamin_Loison (Benjamin Loison)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Benjamin_Loison/linux#100
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?