Installing new NIC to Proxmox VE Server

[chillybags]

Hi All,

Pretty new to this. I have proxmox setup and running nicely with a few VMs on it. (mainly TrueNAS). Its a few years old lenovo tower PC i picked up used.

Just upgraded networking at home to 2.5gbe so thought id buy a new NIC for this device. I bought a LP Link TX-201 which has a realtek 8125. I just plugged it into my PCIE slot and booted the server. Proxmox seemed to recognise it and it showed up as a network device. I added in a virtual bridge for this, reboot the server changed the ethernet cable from the original NIC over to the new TP Link on. Lights on the NIC turn on and my router eventually sees it as a "network device" but wont work cant remote into proxmox GUI and when i ping the IP i set i get nothing. Have to unplug the new NIC and plug back into the old 1gbe one and remote in

I thought i might need a drive for this, ive tried lots of things ive found on forums but doesnt seem to work. What am i missing?

Thanks in advance!

root@thinkcenter:~# lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller
00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem
00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1
00:16.3 Serial controller: Intel Corporation 200 Series Chipset Family KT Redirection
00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode]
00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0)
00:1b.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0)
00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0)
00:1f.0 ISA bridge: Intel Corporation 200 Series PCH LPC Controller (Q270)
00:1f.2 Memory controller: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio
00:1f.4 SMBus: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM
02:00.0 Non-Volatile memory controller: SK hynix BC511
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 04)
root@thinkcenter:~# ethtool enp4s0
Settings for enp4s0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Supported pause frame use: Symmetric Receive-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
                                2500baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
                                             2500baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 2500Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        MDI-X: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: yes
root@thinkcenter:~#

 

[UdoB]

Both bridges are in the same subnet. That's a fundamental error as it does not work the way some people think it does.

Simple solution: just remove the IP address from one of the bridges...

 

[chillybags]

Both bridges are in the same subnet. That's a fundamental error as it does not work the way some people think it does.

Simple solution: just remove the IP address from one of the bridges...

Wow that was dumb of me, so simple! just deleted the other IP and pluged in the new NIC and it worked fine straight away.

If only i did this two days ago would have saves a lot of trouble!

Thanks again!