Intel 10Gb X540 Card recognized but bridge adapter does not pull ip address

R

Robertyu

New Member
Aug 29, 2026
5
1
3
First post here...

Just setup another Proxmox node in another full-size PC (intel 13th gen), and the onboard nix works fine.

I added a Vimin dual-port 10Gb networking card, and cannot get it to work in Proxmox. Here is a link for the card I bought: https://www.amazon.com/dp/B0HF7Y9FH1?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1

Here is how far I got...

The 10Gb Unifi switch sees the card, and negotiates a 10Gb connection using a CAT6 cable to one of the two card ports, and lists a mac address for the port.
Proxmox see's both ports in the node Network pane, and lists the correct mac address.
I made Linux bridges for both ports and applied the configuration, rebooted the node.
The linux bridge interfaces are active, but neither will pull an ip address from the DHCP server, and I tried both, moving the cable from one to another.

Here is the output from ip link show:

Code: 
root@pve02:~# ip link show
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: nic0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether 08:bf:b8:34:af:3d brd ff:ff:ff:ff:ff:ff
    altname enp8s0
    altname enx08bfb834af3d
3: enp2s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr1 state UP mode DEFAULT group default qlen 1000
    link/ether 1a:4b:24:c8:5f:8e brd ff:ff:ff:ff:ff:ff
    altname enx1a4b24c85f8e
4: enp2s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr2 state DOWN mode DEFAULT group default qlen 1000
    link/ether 1a:4b:24:c8:5f:8f brd ff:ff:ff:ff:ff:ff
    altname enx1a4b24c85f8f
5: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 98:59:7a:8c:d6:38 brd ff:ff:ff:ff:ff:ff
    altname wlx98597a8cd638
6: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether 08:bf:b8:34:af:3d 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 1a:4b:24:c8:5f:8e brd ff:ff:ff:ff:ff:ff
8: vmbr2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 1a:4b:24:c8:5f:8f brd ff:ff:ff:ff:ff:ff
root@pve02:~#


here is the log output:

Code: 
root@pve02:~# dmesg | grep ixgbe
[    8.497277] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver
[    8.497278] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
[    8.497325] ixgbe 0000:02:00.0: enabling device (0000 -> 0002)
[    8.774717] ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count = 32, Tx Queue count = 32 XDP Queue count = 0
[    8.860396] ixgbe 0000:02:00.0: 32.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x8 link)
[    8.885054] ixgbe 0000:02:00.0: MAC: 3, PHY: 0, PBA No: 000000-000
[    8.885069] ixgbe 0000:02:00.0: 1a:4b:24:c8:5f:8e
[    9.034572] ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network Connection
[    9.034639] ixgbe 0000:02:00.0: Firmware logging not supported
[    9.034659] ixgbe 0000:02:00.1: enabling device (0000 -> 0002)
[    9.309464] ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count = 32, Tx Queue count = 32 XDP Queue count = 0
[    9.394176] ixgbe 0000:02:00.1: 32.000 Gb/s available PCIe bandwidth (5.0 GT/s PCIe x8 link)
[    9.418344] ixgbe 0000:02:00.1: MAC: 3, PHY: 0, PBA No: 000000-000
[    9.418357] ixgbe 0000:02:00.1: 1a:4b:24:c8:5f:8f
[    9.567570] ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network Connection
[    9.567671] ixgbe 0000:02:00.1: Firmware logging not supported
[    9.568509] ixgbe 0000:02:00.1 enp2s0f1: renamed from eth1
[    9.568914] ixgbe 0000:02:00.0 enp2s0f0: renamed from eth0
[   18.370318] ixgbe 0000:02:00.0 enp2s0f0: entered allmulticast mode
[   18.370351] ixgbe 0000:02:00.0 enp2s0f0: entered promiscuous mode
[   18.504597] ixgbe 0000:02:00.0: registered PHC device on enp2s0f0
[   18.649345] ixgbe 0000:02:00.1 enp2s0f1: entered allmulticast mode
[   18.649378] ixgbe 0000:02:00.1 enp2s0f1: entered promiscuous mode
[   18.783825] ixgbe 0000:02:00.1: registered PHC device on enp2s0f1
[   23.366926] ixgbe 0000:02:00.0 enp2s0f0: NIC Link is Up 10 Gbps, Flow Control: None
root@pve02:~#

Any suggestions that could help on this? Not sure what steps I'm missing. I've searched on this and this card "should" work, but no love at this point yet.
 
Last edited:
Here you go...

Code: 
root@pve02:~# cat /etc/network/interfaces
# 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 nic0 inet manual

iface nic1 inet manual

iface enp2s0f0 inet manual

iface enp2s0f1 inet manual

iface wlp0s20f3 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.1.82/24
        gateway 192.168.1.1
        bridge-ports nic0
        bridge-stp off
        bridge-fd 0

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

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

source /etc/network/interfaces.d/*
root@pve02:~#
 
I was trying to do all interfaces as DHCP and then reserve the issued ip in the router so it stays the same as originally issued. I tend to do a lot of devices this way out of convenience, and generally only go true static on my primary NAS.

I thought by configuring the bridges with a blank ip, they would request an ip address from the DHCP server.

The goal was to get one of these ports up (vmbr1) via DHCP, reserve the issued ip address on the UDM Pro (Ubiquiti) router, then disable the on-board interface (vmbr0 via nic0).

Sorry for my ignorance. New to Proxmox, have some unix experience, but it has been a while.
 
For what it's worth, I did configure that bridge to a static ip address outside of the DHCP range and I can get to the web interface on that one now. I would still like to force it to use DHCP and then reserve the issued address.
 
You can try something like this to request a DHCP lease for the NICs
Bash: 
ifdown vmbr1; dhcpcd -d enp2s0f0
dhcpcd -k; ifup vmbr1

ifdown vmbr2; dhcpcd -d enp2s0f1
dhcpcd -k; ifup vmbr2
The NICs are part of the bridge hence downing it first. Also see here.
 
Thanks for all of your help Impact!

I went ahead and made both of my nodes static. The node in question is working well now. I went ahead and disabled the onboard NIC in the bios, rebooted, ran ip a, then edited my /etc/network/Interfaces file to account for the shift from the disabled onboard nic0 and am just using the 1st 10Gb port on the dual-port 10Gb card for now.

When I get braver, I will then try to set up aggregation for the the dual-port 10Gb card and my Ubiquity 10Gb switch. For now, this is plenty for what I need.

Once again, thanks!
 
  • Like
Reactions: Impact
You must log in or register to reply here.
Top Bottom
Back