Edit for the solution:
I would have never imagined, but chatgpt came up with the solution:
I'm not sure if it's related for the NIC setup, someone with actual networking knowledge should chime in.
My server is an old HP ProLiant DL360 G6, as you can see in the screenshot the NIC is in a shared network port mode, maybe that's the reason?

Hello guys,
I'm in a need of help, since my drives failed in my server and I couldn't get back the data to make it boot.
I remember having a difficult time to configuring VLAN to work, now I have to do it again, sadly I didn't make a backup of the configuration.
The goal is to get PVE (host) to be in VLAN 201 tagged up and running. Here's my configuration:
/etc/network/interfaces
/etc/hosts
/etc/resolv.conf
ip route
brctl show
tcpdump -i enp2s0f0 host not 10.66.0.21
tcpdump -i vmbr0
tcpdump -i vmbr0.201
Router tcpdumps
tcpdump -i eth1
tcpdump -i eth1.0
tcpdump -i eth1.201
I'm not sure if it should behave like my router, but as you can see the vmbr0.201 interface doesn't see traffic. bridge-id x.8002 is vlan 0, and x.8001 is vlan 201 according to tcpdump -i eth1 -e vlan.
My router's configuration could be ruled out, since it was working properly before my SSD's decided to make my life hell.
Whatever I'm trying to ping from Proxmox I get Destination Host Unreachable.
I'm really desperate now, I spent days playing around with multiple /etc/network/interfaces configurations, with no luck. Please help me.
I would have never imagined, but chatgpt came up with the solution:
Code:
auto lo
iface lo inet loopback
auto enp2s0f0
iface enp2s0f0 inet manual
iface enp2s0f1 inet manual
auto enp2s0f0.201
iface enp2s0f0.201 inet manual
vlan-raw-device enp2s0f0
auto vmbr0
iface vmbr0 inet static
address 10.50.0.11/24
gateway 10.50.0.1
bridge-ports enp2s0f0.201
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4092
I'm not sure if it's related for the NIC setup, someone with actual networking knowledge should chime in.
My server is an old HP ProLiant DL360 G6, as you can see in the screenshot the NIC is in a shared network port mode, maybe that's the reason?

Hello guys,
I'm in a need of help, since my drives failed in my server and I couldn't get back the data to make it boot.
I remember having a difficult time to configuring VLAN to work, now I have to do it again, sadly I didn't make a backup of the configuration.
The goal is to get PVE (host) to be in VLAN 201 tagged up and running. Here's my configuration:
/etc/network/interfaces
Code:
auto lo
iface lo inet loopback
iface enp2s0f1 inet manual
iface enp2s0f0 inet manual
auto vmbr0.201
iface vmbr0.201 inet static
address 10.50.0.11/24
gateway 10.50.0.1
auto vmbr0
iface vmbr0 inet manual
bridge-ports enp2s0f0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-4092
source /etc/network/interfaces.d/*
/etc/hosts
Code:
127.0.0.1 localhost.localdomain localhost
10.50.0.11 proxmox.domain.com proxmox
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
/etc/resolv.conf
Code:
search domain.com
nameserver 10.50.0.1
ip route
Code:
default via 10.50.0.1 dev vmbr0.201 proto kernel onlink
10.50.0.0/24 dev vmbr0.201 proto kernel scope link src 10.50.0.11
brctl show
Code:
bridge name bridge id STP enabled interfaces
vmbr0 8000.68b599cca3a8 no enp2s0f0
tcpdump -i enp2s0f0 host not 10.66.0.21
Code:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp2s0f0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
14:54:53.812399 IP 10.66.10.22.netbios-ns > 10.66.10.255.netbios-dgm: UDP, length 174
14:54:53.812516 IP 10.66.10.22.netbios-ns > 10.66.10.255.netbios-ns: UDP, length 50
14:54:54.234193 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:54:54.234207 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
14:54:54,.569969 IP 10.66.10.22.netbios-ns > 10.66.10.255.netbios-ns: UDP, length 50
14:54:55.328782 IP 10.66.10.22.netbios-ns > 10.66.10.255.netbios-ns: UDP, length 50
14:54:56.234200 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:54:56.234209 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
14:54:57.080228 IP 10.66.10.22.netbios-dgm > 10.66.10.255.netbios-dgm: UDP, length 174
14:54:57.080238 IP 10.66.10.22.netbios-ns > 10.66.10.255.netbios-ns: UDP, length 50
14:54:57.831748 IP 10.66.10.22.netbios-ns > 10.66.10.255.netbios-ns: UDP, length 50
14:54:58.234203 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:54:58.234218 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
14:55:06.234167 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:55:06.234174 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
14:55:06.844585 ARP, Request who-has proxmox.domain.com tell 10.50.0.1, length 42
14:55:06.844595 ARP, Request who-has proxmox.domain.com tell 10.50.0.1, length 42
14:55:07.846187 ARP, Request who-has proxmox.domain.com tell 10.50.0.1, length 42
14:55:07.846209 ARP, Request who-has proxmox.domain.com tell 10.50.0.1, length 42
14:55:08.234155 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:55:08.234167 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
14:55:08.849196 ARP, Request who-has proxmox.domain.com tell 10.50.0.1, length 42
14:55:08.849206 ARP, Request who-has proxmox.domain.com tell 10.50.0.1, length 42
14:55:09.984655 LLDP, length 238: RT-AX68U
14:55:10.234137 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:55:10.234145 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
14:55:12.234127 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:55:12.234135 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
14:55:14.234140 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
14:55:14.234148 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
30 packets captured
37 packets received by filter
27 packets dropped by kernel
tcpdump -i vmbr0
Code:
tcpdump: verbose output suppressed, use -v[v...] for full protocol decode
listening on vmbr0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
15:16:26.231977 STP 802.1d, Config, Flags [None], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:16:28.231992 STP 802.1d, Config, Flags [None], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:16:30.231348 STP 802.1d, Config, Flags [None], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:16:32.231933 STP 802.1d, Config, Flags [None], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:16:34.231979 STP 802.1d, Config, Flags [None], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
5 packets captured
5 packets received by filter
0 packets dropped by kernel
tcpdump -i vmbr0.201
Code:
tcpdump: verbose output suppressed, use -v[v...] for full protocol decode
listening on vmbr0.201, link-type EN10MB (Ethernet), snapshot length 262144 bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
Router tcpdumps
tcpdump -i eth1
Code:
tcpdump: verbose output suppressed, use -v[v...] for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), snapshot length 262144 bytes
15:22:38.691534 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:22:38.691552 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
15:22:40.691533 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:22:40.691550 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
15:22:41.217664 LLDP, length 238: RT-AX86U
15:22:42.691533 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:22:42.691549 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
15:22:44.691533 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:22:44.691550 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
9 packets captured
9 packets received by filter
0 packets dropped by kernel
tcpdump -i eth1.0
Code:
tcpdump: verbose output suppressed, use -v[v...] for full protocol decode
listening on eth1.0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
15:23:46.691532 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:23:48.691531 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
15:23:50.691534 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8002, length 35
3 packets captured
3 packets received by filter
0 packets dropped by kernel
tcpdump -i eth1.201
Code:
tcpdump: verbose output suppressed, use -v[v...] for full protocol decode
listening on eth1.201, link-type EN10MB (Ethernet), snapshot length 262144 bytes
15:23:54.691545 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
15:23:56.691546 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
15:23:58.691547 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
15:24:00.691544 STP 802.1d, Config, Flags [none], bridge-id 8000.24:4b:fe:72:14:f8.8001, length 35
4 packets captured
4 packets received by filter
0 packets dropped by kernel
I'm not sure if it should behave like my router, but as you can see the vmbr0.201 interface doesn't see traffic. bridge-id x.8002 is vlan 0, and x.8001 is vlan 201 according to tcpdump -i eth1 -e vlan.
My router's configuration could be ruled out, since it was working properly before my SSD's decided to make my life hell.
Whatever I'm trying to ping from Proxmox I get Destination Host Unreachable.
Code:
root@proxmox:~# ping 10.50.0.1
PING 10.50.0.1 (10.50.0.1) 56(84) bytes of data.
From 10.50.0.11 icmp_seq=1 Destination Host Unreachable
From 10.50.0.11 icmp_seq=2 Destination Host Unreachable
From 10.50.0.11 icmp_seq=3 Destination Host Unreachable
--- 10.50.0.1 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3056ms
root@proxmox:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 10.50.0.11 icmp_seq=1 Destination Host Unreachable
From 10.50.0.11 icmp_seq=2 Destination Host Unreachable
From 10.50.0.11 icmp_seq=3 Destination Host Unreachable
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3073ms
root@proxmox:~# ping 10.50.0.11
PING 10.50.0.11 (10.50.0.11) 56(84) bytes of data.
64 bytes from 10.50.0.11: icmp_seq=1 ttl=64 time=0.027 ms
64 bytes from 10.50.0.11: icmp_seq=2 ttl=64 time=0.025 ms
--- 10.50.0.11 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1012ms
rtt min/avg/max/mdev = 0.025/0.026/0.027/0.001 ms
root@proxmox:~# ping 10.50.0.10
PING 10.50.0.10 (10.50.0.10) 56(84) bytes of data.
From 10.50.0.11 icmp_seq=1 Destination Host Unreachable
From 10.50.0.11 icmp_seq=2 Destination Host Unreachable
From 10.50.0.11 icmp_seq=3 Destination Host Unreachable
--- 10.50.0.16 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3057ms
I'm really desperate now, I spent days playing around with multiple /etc/network/interfaces configurations, with no luck. Please help me.
Last edited: