[SOLVED] How to delete network devices in UI

Dulcow

Member
Sep 1, 2023
38
0
6
Hi there,

I'm installing a new machine and I'm facing this:

1715672277019.png

I have no services running on this server yet and I had a bunch of "enx" devices in the network tab. The "/etc/network/interfaces" file has been cleaned and the server rebooted but I can still see those. What are they?

1715672514884.png

The only physical NICs are the "enp" ones (2x 10G SFP+ and 2x 10G RJ45). I tried to look for "enx86febf2c6edb" but it is nowhere in the configuration files. I also have no idea what "enp16s0f0np0" and "enp16s0f1np1"

Any ideas?

Thanks,

D.
 
Sure thing, here you go:

Bash:
root@pve-nas-2:~# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp16s0f0np0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether f8:f2:1e:1f:84:c0 brd ff:ff:ff:ff:ff:ff
3: enp16s0f1np1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether f8:f2:1e:1f:84:c2 brd ff:ff:ff:ff:ff:ff
4: enp43s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:36:50:70 brd ff:ff:ff:ff:ff:ff
5: enx86febf2c6edb: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 86:fe:bf:2c:6e:db brd ff:ff:ff:ff:ff:ff
6: enp43s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:36:5e:38 brd ff:ff:ff:ff:ff:ff
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/ether f2:5b:2f:93:d4:71 brd ff:ff:ff:ff:ff:ff
8: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:36:5e:38 brd ff:ff:ff:ff:ff:ff
 
enx86febf2c6edb is a virtual NIC, most likely from your motherboard (is it a Supermicro?).

Regarding enp16s0f1np1 vs enp16s0p1: Your system currently seems to detect that NIC as enp16s0f1np1, judging from the ip link output. Did you switch kernels on this installation? Network interface names can change when using different kernels, it might make sense to pin those names and then only use one variant in the configuration. You can read more about network interface names and how to override them in our documentation [1]

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_naming_conventions
 
  • Like
Reactions: Dulcow and fluxX04
Supermicro board? enx is your IPMI interface (enx+MAC)

ASRock Rack and they do some funky stuff with their IMPI interface (kind of bridge by default). I will check again in the IPMI configurations.

That does not explain the "...np1" and "...np0" interface.
 
Regarding enp16s0f1np1 vs enp16s0p1: Your system currently seems to detect that NIC as enp16s0f1np1, judging from the ip link output. Did you switch kernels on this installation? Network interface names can change when using different kernels, it might make sense to pin those names and then only use one variant in the configuration. You can read more about network interface names and how to override them in our documentation [1]
I upgraded the kernel this morning from 6.5 to 6.8. However, the interfaces used by the bridges are still the non "np" ones. How can I fix that?
 
I upgraded the kernel this morning from 6.5 to 6.8. However, the interfaces used by the bridges are still the non "np" ones. How can I fix that?

You can edit the entries of the bridge via the Web UI and enter the correct name there. Additionally, you should be able to remove the obsolete entries with the old name of the NIC as well.
 
Thanks, I removed the uneeded NICs. For the enx one, it has to be related to the IPMI stuff.
 
For the enx interface, if you have ipmitool installed, then you can simply check with the command:
Code:
ipmitool lan print 1 | grep "MAC Address"
It should be identical to the one resulting from:
Code:
ip l | grep enx86febf2c6edb
or:
Code:
cat /sys/class/net/enx86febf2c6edb/address
 
I cannot find the MAC address from the IPMI interface under Proxmox. It has to be something else but I have no idea what it is :D

I looked in dmesg and I found something which should be a USB NIC but I don't think I have one... Odd.

Bash:
root@pve-nas-2:~# dmesg | grep enx060fb8f2da6f
[    6.700896] cdc_ether 1-14.2:2.0 enx060fb8f2da6f: renamed from usb0
 
The interface name has changed now:

1715697883426.png

I can get the MAC address from the list below:

Bash:
root@pve-nas-2:~# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp16s0f0np0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether f8:f2:1e:1f:84:c0 brd ff:ff:ff:ff:ff:ff
3: enp16s0f1np1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
    link/ether f8:f2:1e:1f:84:c2 brd ff:ff:ff:ff:ff:ff
4: enp43s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:36:50:70 brd ff:ff:ff:ff:ff:ff
5: enx060fb8f2da6f: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 06:0f:b8:f2:da:6f brd ff:ff:ff:ff:ff:ff
6: enp43s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:36:5e:38 brd ff:ff:ff:ff:ff:ff
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether f8:f2:1e:1f:84:c2 brd ff:ff:ff:ff:ff:ff
8: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether a8:a1:59:36:5e:38 brd ff:ff:ff:ff:ff:ff

But it does not correspond to the IPMI one (a8:a1:59:37:c:d1). It is something else...

Thanks,

D.
 
  • Like
Reactions: Dulcow

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!