[SOLVED] Additional network card causes dead network devices

L

lumpi

New Member
Aug 4, 2025
1
0
1
Hello

I've added an additional network card into my proxmox computer.
This causes a "device-rotation" (related to the network device names / numbers in proxmox) and a connection lost to the proxmox mgmt-ip.

Old naming of the network devices (before inserting the new network card) was:
enp4s0f0, enp4s0f1, enp4s0f2, enp4s0f3 -> Broadcom 4xRJ45 1Gbps network card
enp6s0 -> OnBoard NIC (management)

Then, after adding an additional network card, the following network devices are listed:
enp4s0f0, enp4s0f1, enp4s0f2, enp4s0f3 -> dead interfaces
enp4s0f0np0, enp4s0f1np1, enp4s0f2np2, enp4s0f3np3 -> the new intel nic, 4x10Gbps fibre
enp5s0f0, enp5s0f1, enp5s0f2, enp5s0f3 -> the already existing Broadcom 4xRJ45 1Gbps network card moved from enp4 to enp5
enp7s0 -> the alreay existing OnBoard NIC (management) moved from enp6s0 to enp7s0

As already mentioned, because of this "renaming", i wasn't able to connect to the proxmox management interface any more.
I connected by local console and did a ifreload -a, which reported missing devices in the network bridges.
Then i did a vim /etc/network/interfaces and replaced enp6s0 with enp7s0 at the mgmt-bridge (vmbr0).
After that, i was able to connect to the proxmox management again and i could reassign the other interfaces.

So finally everything is up and running, but there are still those dead interfaces. And every time i do a ifreload -a, it complains about them.
Code: 
root@proxmox-01:~# ifreload -a
warning: enp4s0f0: interface not recognized - please check interface configuration
warning: enp4s0f1: interface not recognized - please check interface configuration
warning: enp4s0f2: interface not recognized - please check interface configuration
warning: enp4s0f3: interface not recognized - please check interface configuration

My question is, can i just delete those network devices from /etc/network/interfaces and everything is ok, or do i need to consider more?

my /etc/network/interfaces
Code: 
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enp7s0 inet manual

auto enp4s0f0
iface enp4s0f0 inet manual

auto enp4s0f1
iface enp4s0f1 inet manual

auto enp4s0f2
iface enp4s0f2 inet manual

auto enp4s0f3
iface enp4s0f3 inet manual

iface wlo1 inet manual

iface enp4s0f0np0 inet manual

auto enp4s0f1np1
iface enp4s0f1np1 inet manual

auto enp4s0f2np2
iface enp4s0f2np2 inet manual

iface enp4s0f3np3 inet manual

iface enp5s0f0 inet manual

auto enp5s0f1
iface enp5s0f1 inet manual

auto enp5s0f2
iface enp5s0f2 inet manual

iface enp5s0f3 inet manual

auto bond0
iface bond0 inet manual
    bond-slaves enp5s0f1 enp5s0f2
    bond-miimon 100
    bond-mode 802.3ad
    bond-xmit-hash-policy layer2

auto vmbr0
iface vmbr0 inet static
    address 192.168.254.243/24
    gateway 192.168.254.1
    bridge-ports enp7s0
    bridge-stp off
    bridge-fd 0

auto fw_p1_wan1
iface fw_p1_wan1 inet manual
    bridge-ports enp5s0f3
    bridge-stp off
    bridge-fd 0

auto fw_p2_wan2
iface fw_p2_wan2 inet manual
    bridge-ports none
    bridge-stp off
    bridge-fd 0

auto fw_p3_lan1
iface fw_p3_lan1 inet manual
    bridge-ports bond0
    bridge-stp off
    bridge-fd 0

auto fw_p4_lan2
iface fw_p4_lan2 inet manual
    bridge-ports none
    bridge-stp off
    bridge-fd 0

auto fw_p5_lan3
iface fw_p5_lan3 inet manual
    bridge-ports none
    bridge-stp off
    bridge-fd 0

auto testridge
iface testridge inet manual
    bridge-ports none
    bridge-stp off
    bridge-fd 0

and a ip -a
Code: 
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp5s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 1c:fd:08:77:9e:3c brd ff:ff:ff:ff:ff:ff
3: enp5s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether 1c:fd:08:77:9e:3d brd ff:ff:ff:ff:ff:ff
4: enp5s0f2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
    link/ether 1c:fd:08:77:9e:3d brd ff:ff:ff:ff:ff:ff permaddr 1c:fd:08:77:9e:3e
5: enp5s0f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master fw_p1_wan1 state UP group default qlen 1000
    link/ether 1c:fd:08:77:9e:3f brd ff:ff:ff:ff:ff:ff
6: enp4s0f0np0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 64:9d:99:b2:73:3e brd ff:ff:ff:ff:ff:ff
    inet6 fe80::669d:99ff:feb2:733e/64 scope link
       valid_lft forever preferred_lft forever
7: enp4s0f1np1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 64:9d:99:b2:73:3f brd ff:ff:ff:ff:ff:ff
8: enp4s0f2np2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 64:9d:99:b2:73:40 brd ff:ff:ff:ff:ff:ff
9: enp4s0f3np3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 64:9d:99:b2:73:41 brd ff:ff:ff:ff:ff:ff
10: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
    link/ether 74:56:3c:48:4f:47 brd ff:ff:ff:ff:ff:ff
11: wlo1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 10:68:38:2b:6a:5f brd ff:ff:ff:ff:ff:ff
    altname wlp6s0
12: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 74:56:3c:48:4f:47 brd ff:ff:ff:ff:ff:ff
    inet 192.168.254.243/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::7656:3cff:fe48:4f47/64 scope link
       valid_lft forever preferred_lft forever
13: fw_p1_wan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1c:fd:08:77:9e:3f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1efd:8ff:fe77:9e3f/64 scope link
       valid_lft forever preferred_lft forever
14: fw_p2_wan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether c6:2c:8f:58:3c:5f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::a82a:16ff:fe7e:f2eb/64 scope link
       valid_lft forever preferred_lft forever
15: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p3_lan1 state UP group default qlen 1000
    link/ether 1c:fd:08:77:9e:3d brd ff:ff:ff:ff:ff:ff
16: fw_p3_lan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 1c:fd:08:77:9e:3d brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1efd:8ff:fe77:9e3d/64 scope link
       valid_lft forever preferred_lft forever
17: fw_p4_lan2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 64:9d:99:b2:73:3e brd ff:ff:ff:ff:ff:ff
    inet6 fe80::669d:99ff:feb2:733e/64 scope link
       valid_lft forever preferred_lft forever
18: fw_p5_lan3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether b6:8f:04:11:f4:73 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::832:eff:fea0:18d3/64 scope link
       valid_lft forever preferred_lft forever
19: testridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 0a:d0:70:3a:99:2c brd ff:ff:ff:ff:ff:ff
    inet6 fe80::8d0:70ff:fe3a:992c/64 scope link
       valid_lft forever preferred_lft forever
40: veth103i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
    link/ether fe:37:f3:39:f0:be brd ff:ff:ff:ff:ff:ff link-netnsid 0
41: fwbr103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3e:20:7d:73:ea:d6 brd ff:ff:ff:ff:ff:ff
42: fwpr103p0@fwln103i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p3_lan1 state UP group default qlen 1000
    link/ether 1e:6d:d9:67:f1:fd brd ff:ff:ff:ff:ff:ff
43: fwln103i0@fwpr103p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr103i0 state UP group default qlen 1000
    link/ether 3e:20:7d:73:ea:d6 brd ff:ff:ff:ff:ff:ff
44: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr100i0 state UNKNOWN group default qlen 1000
    link/ether f6:4f:98:0b:e9:6e brd ff:ff:ff:ff:ff:ff
45: fwbr100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 16:78:da:0d:27:36 brd ff:ff:ff:ff:ff:ff
46: fwpr100p0@fwln100i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p3_lan1 state UP group default qlen 1000
    link/ether 32:9b:ff:e0:7f:cb brd ff:ff:ff:ff:ff:ff
47: fwln100i0@fwpr100p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr100i0 state UP group default qlen 1000
    link/ether 16:78:da:0d:27:36 brd ff:ff:ff:ff:ff:ff
48: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN group default qlen 1000
    link/ether 8a:ba:3d:91:36:fb brd ff:ff:ff:ff:ff:ff
49: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 86:9c:e9:8e:cc:38 brd ff:ff:ff:ff:ff:ff
50: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p3_lan1 state UP group default qlen 1000
    link/ether 36:fb:e3:1f:36:3a brd ff:ff:ff:ff:ff:ff
51: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
    link/ether 86:9c:e9:8e:cc:38 brd ff:ff:ff:ff:ff:ff
52: tap104i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i0 state UNKNOWN group default qlen 1000
    link/ether d2:fc:15:ec:f4:10 brd ff:ff:ff:ff:ff:ff
53: fwbr104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 36:14:82:26:7f:e1 brd ff:ff:ff:ff:ff:ff
54: fwpr104p0@fwln104i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p1_wan1 state UP group default qlen 1000
    link/ether ca:34:ce:fb:25:3b brd ff:ff:ff:ff:ff:ff
55: fwln104i0@fwpr104p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i0 state UP group default qlen 1000
    link/ether 36:14:82:26:7f:e1 brd ff:ff:ff:ff:ff:ff
56: tap104i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i1 state UNKNOWN group default qlen 1000
    link/ether 4e:72:df:fa:f9:43 brd ff:ff:ff:ff:ff:ff
57: fwbr104i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 02:d7:9d:6d:b9:eb brd ff:ff:ff:ff:ff:ff
58: fwpr104p1@fwln104i1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p2_wan2 state UP group default qlen 1000
    link/ether c6:2c:8f:58:3c:5f brd ff:ff:ff:ff:ff:ff
59: fwln104i1@fwpr104p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i1 state UP group default qlen 1000
    link/ether 02:d7:9d:6d:b9:eb brd ff:ff:ff:ff:ff:ff
60: tap104i2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i2 state UNKNOWN group default qlen 1000
    link/ether 8a:45:49:ad:67:fd brd ff:ff:ff:ff:ff:ff
61: fwbr104i2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6e:92:7f:0b:fe:d8 brd ff:ff:ff:ff:ff:ff
62: fwpr104p2@fwln104i2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p3_lan1 state UP group default qlen 1000
    link/ether 92:97:b2:d7:f0:25 brd ff:ff:ff:ff:ff:ff
63: fwln104i2@fwpr104p2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i2 state UP group default qlen 1000
    link/ether 6e:92:7f:0b:fe:d8 brd ff:ff:ff:ff:ff:ff
64: tap104i3: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i3 state UNKNOWN group default qlen 1000
    link/ether be:c6:89:4f:64:96 brd ff:ff:ff:ff:ff:ff
65: fwbr104i3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 92:26:3d:ba:c6:71 brd ff:ff:ff:ff:ff:ff
66: fwpr104p3@fwln104i3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p4_lan2 state UP group default qlen 1000
    link/ether a2:d9:93:71:b4:9e brd ff:ff:ff:ff:ff:ff
67: fwln104i3@fwpr104p3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i3 state UP group default qlen 1000
    link/ether 92:26:3d:ba:c6:71 brd ff:ff:ff:ff:ff:ff
68: tap104i4: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr104i4 state UNKNOWN group default qlen 1000
    link/ether 92:89:13:b6:84:5b brd ff:ff:ff:ff:ff:ff
69: fwbr104i4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9a:01:3b:3a:0a:2c brd ff:ff:ff:ff:ff:ff
70: fwpr104p4@fwln104i4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fw_p5_lan3 state UP group default qlen 1000
    link/ether b6:8f:04:11:f4:73 brd ff:ff:ff:ff:ff:ff
71: fwln104i4@fwpr104p4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr104i4 state UP group default qlen 1000
    link/ether 9a:01:3b:3a:0a:2c brd ff:ff:ff:ff:ff:ff

Thanks
 
Last edited:
This is a common occurence, since those names are based on PCI IDs, which can change when adding / removing PCIe devices. We have recently added a tool for pinning your network interface names, so they stay consistent across reboots [1].

lumpi said:
My question is, can i just delete those network devices from /etc/network/interfaces and everything is ok, or do i need to consider more?
Click to expand...

Yes, since they have been renamed they serve no purpose in the network configuration anymore and ifupdown2 will complain since they don't exist anymore on the host. It should be safe to remove them from your configuration.

[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_using_the_pve_network_interface_pinning_tool
 
  • Like
Reactions: lumpi
You must log in or register to reply here.
Top Bottom