Can't have a 3rd network interface up

dohedmuvhk

New Member
Feb 1, 2024
2
0
1
I installed PVE on a small machine with 4 network interfaces. It hosts my openwrt based router os, with which I already have two network interfaces working (WAN + LAN). Now I want to add a 3rd network interface, which connecting to the ISP router with my PVE machine and to my openwrt.

But the 3rd one seems to be not working.

As showed in the screenshot, the enp4s0 is connected to the cable. But it's not in active (cable is good)
Can I get some help regarding how to make the network interface work please?
1706759888063.png

output of `/etc/network/interfaces`
Bash:
auto lo
iface lo inet loopback

iface enp2s0 inet manual

iface enp3s0 inet manual

auto enp4s0
iface enp4s0 inet manual

auto enp5s0
iface enp5s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.11.2/24
        gateway 192.168.11.11
        bridge-ports enp2s0
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet manual
        bridge-ports enp3s0
        bridge-stp off
        bridge-fd 0

auto vmbr2
iface vmbr2 inet manual
        bridge-ports enp4s0
        bridge-stp off
        bridge-fd 0

auto vmbr3
iface vmbr3 inet manual
        bridge-ports enp5s0
        bridge-stp off
        bridge-fd 0



ip addr
Bash:
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
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP group default qlen 1000
    link/ether 00:e2:69:58:56:93 brd ff:ff:ff:ff:ff:ff
3: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP group default qlen 1000
    link/ether 00:e2:69:58:56:94 brd ff:ff:ff:ff:ff:ff
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:e2:69:58:56:93 brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.2/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::2e2:69ff:fe58:5693/64 scope link
       valid_lft forever preferred_lft forever
7: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:e2:69:58:56:94 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::2e2:69ff:fe58:5694/64 scope link
       valid_lft forever preferred_lft forever
8: vmbr2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:e2:69:58:56:95 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::2e2:69ff:fe58:5695/64 scope link
       valid_lft forever preferred_lft forever
9: vmbr3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:e2:69:58:56:96 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::2e2:69ff:fe58:5696/64 scope link
       valid_lft forever preferred_lft forever
10: tap100i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether a2:0f:e5:85:55:27 brd ff:ff:ff:ff:ff:ff
11: tap100i1: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr1 state UNKNOWN group default qlen 1000
    link/ether 3e:ee:07:9f:45:bc brd ff:ff:ff:ff:ff:ff
12: tap100i2: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr2 state UNKNOWN group default qlen 1000
    link/ether 16:51:89:d7:c0:9a brd ff:ff:ff:ff:ff:ff
13: tap100i3: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr3 state UNKNOWN group default qlen 1000
    link/ether 62:43:ca:32:3c:43 brd ff:ff:ff:ff:ff:ff
14: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UNKNOWN group default qlen 1000
    link/ether 1e:22:99:5c:31:e4 brd ff:ff:ff:ff:ff:ff

ifup enp4s
Bash:
warning: enp4s0: interface not recognized - please check interface configuration
 
Hi,
  • enp4s0 is not listed in the output of ip addr, indicating it's not recognized by the system.
  • The bridge vmbr2 is configured with bridge-ports enp4s0, but enp4s0 itself is not configured correctly.
I would double-check for typos in the interface name enp4s0 in both /etc/network/interfaces and when using commands like ifup and then use ip link show to view all available interfaces and confirm the exact name. Use ip link set enp4s0 up to bring up the interface manually, if successful, proceed to bridge configuration. Then remove the line bridge-ports enp4s0 from the vmbr2 configuration in /etc/network/interfaces and try to add a separate configuration block for enp4s0 as follows:

Code:
auto enp4s0
iface enp4s0 inet static
    address <IP_ADDRESS>/<NETMASK>  # Replace with desired IP and subnet
    gateway <GATEWAY_IP>  # If needed

Finally, use systemctl restart networking to apply the changes.

Hope it helps
 
Hi,
  • enp4s0 is not listed in the output of ip addr, indicating it's not recognized by the system.
  • The bridge vmbr2 is configured with bridge-ports enp4s0, but enp4s0 itself is not configured correctly.
I would double-check for typos in the interface name enp4s0 in both /etc/network/interfaces and when using commands like ifup and then use ip link show to view all available interfaces and confirm the exact name. Use ip link set enp4s0 up to bring up the interface manually, if successful, proceed to bridge configuration. Then remove the line bridge-ports enp4s0 from the vmbr2 configuration in /etc/network/interfaces and try to add a separate configuration block for enp4s0 as follows:

Code:
auto enp4s0
iface enp4s0 inet static
    address <IP_ADDRESS>/<NETMASK>  # Replace with desired IP and subnet
    gateway <GATEWAY_IP>  # If needed

Finally, use systemctl restart networking to apply the changes.

Hope it helps

Thanks for the help!!!

I finally figured it out, it was due to I setup an PCI device for network interface earlier (I couldn't recall why I did that). So the virtual device I created wouldn't work, after I remove the PCI device, it started to work perfectly.
 

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!