NIC TP-LINK TG-3468 cant connect

dixzee

New Member
Nov 21, 2023
1
0
1
I bought 2 TP-Link TG-3468 and after I set them up on Proxmox and connected them to one of the VMs they couldn't connect
ip a :
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: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vmbr1 state DOWN group default qlen 1000
link/ether 14:eb:b6:e0:50:b8 brd ff:ff:ff:ff:ff:ff
3: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast master vmbr2 state DOWN group default qlen 1000
link/ether 14:eb:b6:e0:46:5e brd ff:ff:ff:ff:ff:ff
4: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000
link/ether 30:e1:71:6a:bb:bd brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
5: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 30:e1:71:6a:bb:bd brd ff:ff:ff:ff:ff:ff
inet 192.168.92.100/24 scope global vmbr0
valid_lft forever preferred_lft forever
inet6 fe80::32e1:71ff:fe6a:bbbd/64 scope link
valid_lft forever preferred_lft forever
6: vmbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 14:eb:b6:e0:50:b8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::16eb:b6ff:fee0:50b8/64 scope link
valid_lft forever preferred_lft forever
7: vmbr2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 14:eb:b6:e0:46:5e brd ff:ff:ff:ff:ff:ff
inet6 fe80::16eb:b6ff:fee0:465e/64 scope link
valid_lft forever preferred_lft forever
8: tap101i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr101i0 state UNKNOWN group default qlen 1000
link/ether 8a:d2:85:db:5b:1b brd ff:ff:ff:ff:ff:ff
9: fwbr101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 96:aa:f0:8a:0e:4b brd ff:ff:ff:ff:ff:ff
10: fwpr101p0@fwln101i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether fe:92:37:71:2c:ea brd ff:ff:ff:ff:ff:ff
11: fwln101i0@fwpr101p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr101i0 state UP group default qlen 1000
link/ether 1a:c1:d3:cc:32:00 brd ff:ff:ff:ff:ff:ff
16: veth103i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether fe:2b:fb:84:ce:d3 brd ff:ff:ff:ff:ff:ff link-netnsid 0
70: tap102i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr102i0 state UNKNOWN group default qlen 1000
link/ether 02:7c:5c:1c:9a:03 brd ff:ff:ff:ff:ff:ff
71: fwbr102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 8a:c5:08:42:ae:0a brd ff:ff:ff:ff:ff:ff
72: fwpr102p0@fwln102i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
link/ether 7a:8e:bd:94:62:be brd ff:ff:ff:ff:ff:ff
73: fwln102i0@fwpr102p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr102i0 state UP group default qlen 1000
link/ether f6:d1:36:7b:69:16 brd ff:ff:ff:ff:ff:ff

root@server:~# 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 eno1 inet manual

iface wlxecc89cd165e4 inet manual

iface enp1s0 inet manual

iface enp2s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.92.100/24
gateway 192.168.92.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

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

auto vmbr2
iface vmbr2 inet manual
bridge-ports enp2s0
bridge-stp off
bridge-fd 0
 
Same issue basically. Just wondering if you made any progress on this? I just received my TP-Link TG-3468 to be used as a secondary NIC but it seems to just disconnect both NICs.
 
Same issue basically. Just wondering if you made any progress on this? I just received my TP-Link TG-3468 to be used as a secondary NIC but it seems to just disconnect both NICs.
I'm planning to get the same card. Does proxmox recognise it and can I use it as my main interface? What about pcie pass through?
 
Yes it works. I haven't tested pcie pass through as my processor doesn't support it.
Thanks :)
I getting a small HP Prodesk 600 G4 with i7-7700 so i think it will support pass through.

Im planing to move my pfsense to proxmox, i have had it running on a HP Server before with proxmox, but dont remember i i used pass through.
 

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!