"VLAN aware" checkbox has no function

[dasfliege]

I've setup a new 8.1.3 proxmox cluster and was kind of surprised that my VM using a tagged VLAN had network connection, even though "VLAN aware" was not ticked on the bridge interface. Did a few tests and it seems that this checkbox has absolutely no impact, whether or not VLANs are passed through to the VMs. I can tag VLANs inside a guest OR on the VMs virtual NIC and it's working perfectly fine, even with VLAN aware unchecked.

Did i completely missunderstand something regarding the "VLAN aware" checkbox?

 

[unclemonk]

I have noticed the same. Funny enough, I found this post googling for "proxmox whixh interface vlan aware check box" (misspelling left intact) for this exact reason.

 

[bofh]

ofc it is you dont understand the feature.

ok if youre not vlan aware, the vm is running on vlan 0 aka untagged, and ofc all tagged also gets passed. in that case we need to config within the vm itself to go trough tagged traffic and associate additional interfaces for it.

if vlan aware is tagged you can assign a tagged vlan to a virtual nic on an vm. for the vm this traffic looks regular untagged and you wont see any other tagged traffic there.

now this is ofc a security trap.personally i would suggest run the bridge interface as a trunk interface and ALWAYS assign some vlan to virtual nics or use the newly shiny sdn feature.

or you can fully trust your vms.

 

[dasfliege]

Read my initial post. Even if you don't tick vlan aware on the bridge, tagging a vlan on the VMs virtual NIC is working perfectly fine. Try it and proof me wrong ;-)

 

[basil]

vlan 0 aka untagged

untagged vlan is 1, not zero

Did i completely missunderstand something regarding the "VLAN aware" checkbox?

bridge vlan show dev eno1
bridge -c vlan show

VLAN aware not for enabling or disabling vlan using

 

[unclemonk]

I've setup a new 8.1.3 proxmox cluster and was kind of surprised that my VM using a tagged VLAN had network connection, even though "VLAN aware" was not ticked on the bridge interface. Did a few tests and it seems that this checkbox has absolutely no impact, whether or not VLANs are passed through to the VMs. I can tag VLANs inside a guest OR on the VMs virtual NIC and it's working perfectly fine, even with VLAN aware unchecked.

Did i completely missunderstand something regarding the "VLAN aware" checkbox?

Went back and looked at this and it appears it does not do "that", but it does do "something."

The VLAN-aware checkbox is a new addition that allows Proxmox to act as a trunk in a switch that will pipe multiple VLANs over one connection. Although it is not important to enable it, however, it is a new way of handling VLANs on the bridge. For example, if we need to implement 10 VLANs, we will need to create 10 virtual bridges in the traditional Linux bridge way. However, using the VLAN-aware option, we can create one bridge and just add the VLAN ID to it, thus saving a lot of time typing out multiple bridge configurations. (https://www.oreilly.com/library/vie...ware checkbox is,handling VLANs on the bridge.)

So, what we both observed appears to be normal.

 

[spirit]

with bridge vlan-aware,the vlan tagging is done at bridge port level

without vlan-aware, the vlan tagging is done at interface level with a additional non vlan-aware bridge create in background (eth0.<vlan> ----> vmbrV<vlan>)


Without vlan-aware, you can't do trunk or transport vlan inside the vm.

 

[iwik]

Hi, it is possible to put into virtual machine only selected vlans on one nic? To create tagged vnet with selected multiple vlans. In gui it is possible to have only one vlan.

 

[spirit]

Hi, it is possible to put into virtual machine only selected vlans on one nic? To create tagged vnet with selected multiple vlans. In gui it is possible to have only one vlan.

yes. you need to use a vlan-aware bridge for classic network, or check the vlan-aware vnet. (I think you can create the vlan iwthout vlan, or with vlan=1 for default vlan).

Then, multiple vlans should be allowed. (It's allso possible to filter vlans list in vmid.conf directly, net0:.....,trunks=1,5,8,9 ... )