Bridge VLAN-aware doesn't work only on one of my nodes.

sa10

Renowned Member
Feb 6, 2009
46
0
71
Canada
Hello,
Maybe anyone has any ideas how to find the cause of a non-working vlan with bridge in the VLAN-aware mode.
It doesn't work on just one of several nodes. All nodes has same configuration and the same hardware.

I have two vm in vlan147 :
VM-1 xx.xxx.191.4/24 node2 (pve-manager/6.4-14/15e2bf61 (running kernel: 5.4.174-2-pve))
VM-2 xx.xxx.191.101/24 node4 (pve-manager/6.2-11/22fb4983 (running kernel: 5.4.60-1-pve))
The vlan147 came to nodes as tagged traffic
VM interface for example :
net0: virtio=16:08:22:91:0A:9A,bridge=vmbr0,tag=147

I run inside VM2
ping xx.xxx.191.4
And tcpdump sees on the bond0 (eno1-eno2) of the node2 ARP Request and Reply which come from VM-1:

6), IPv4 (len 4), Request who-has xx.xxx.191.4 tell xx.xxx.191.101, length 28 23:16:10.713871 e2:a7:6f:a4:df:5f > 16:08:22:91:0a:9a, ethertype 802.1Q (0x8100), length 64: vlan 247, p 0, ethertype ARP, Ethernet (len
6), IPv4 (len 4), Reply xx.xxx.191.4 is-at e2:a7:6f:a4:df:5f, length 46

But it doesn't see the Reply on the bridge vmbr0, only Requests
The VLAN-aware is on.

My nodes have different version of proxmox, the problem node is under pve-manager/6.4-14/15e2bf61 (running kernel: 5.4.174-2-pve

What could be the reason?
Thanks!
 
Last edited:
I found the reason, now everything is working well.
I found these files in the procfs,
ls /proc/net/vlan/
bond0.147 config
I didn't find the bond0.147 in the configs or in the command history. How this was created it’s a mystery of course .
I have executed this command to remove this interface
ip link delete link bondname 0.147 type vlan id 147
 
I found the reason, now everything is working well.
I found these files in the procfs,
ls /proc/net/vlan/
bond0.147 config
I didn't find the bond0.147 in the configs or in the command history. How this was created it’s a mystery of course .
I have executed this command to remove this interface
ip link delete link bondname 0.147 type vlan id 147

it's look like a vm was started once with setup in non-vlan aware config. (so proxmox creat a bond0.147 && vmbr0v147 in background at vm start).
it's not delete on vm stop.
 

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!