VLAN tagging not working

[apathia]

I can't seem to figure this out. I have 2 NICs, one for management, the other for actual traffic. vmbr0 is the management interface, vmbr1 is the other.

Here's /etc/network/interfaces:

auto lo
iface lo inet loopback

iface enp4s2 inet manual

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 172.16.0.50/24
        gateway 172.16.0.1
        bridge-ports enp4s2
        bridge-stp off
        bridge-fd 0

auto vmbr1
iface vmbr1 inet manual
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

I've got the management port on my switch set for untagged traffic and the other port set for tagged VLAN traffic.

The problem I'm having is I have a VM set to use vmbr1, which works fine so long as I don't have a VLAN set. When I try to set any VLAN, it fails to get an IP.

I also initially had vmbr0.99 set with the static IP instead of vmbr0, which worked for the management NIC, and when I used vmbr1 and VLAN 99, it worked fine but no other VLAN worked so I don't get how that works? vmbr0 is a separate NIC altogether so how did vmbr1 grab an IP from VLAN 99?

So it seems only the management NIC works with VLANs, but only if I specify a LINUX VLAN, despite not bonding the physical NICs.

 

[Universal4]

Have you verified the dhcp server can be reached on the vlan you want to set to vmbr1?

One way to test that is to define a static ip on the vm you want to ultimately use dhcp, and then ping the dhcp server to make sure it can be contacted.

Is it reasonable to set vmbr1 with a static ip that is outside the dhcp scope?

 

[apathia]

Theoretically I could set it up with a static IP on the management VLAN as well, I didn't think I needed to so I didn't bother.

Looks like static IP's are a no-go, even on the management VLAN so something isn't forwarding the requests correctly.