I just caused myself some serious grief, breaking our network for hours. I've solved the problem... but I believe ProxMox could easily help users to avoid this issue.
A bit of background
Turns out, to use a VLAN on a VM network device you MUST:
A bit of background
- I have a four port (I350) Intel network card with SR-IOV capability. It's been wonderful.
- One of the ports is used as a multi-VLAN trunk by pfSense. Until now, ProxMox didn't need to know anything about that. It just works.
- I wanted to give another VM access to one of the VLANs
- I added a (virtio) network device, on the proper VLAN
- Didn't seem to do anything, so I removed it again
- My entire network was busted. Rebooting pfSense didn't help. Packets would go in one direction but not the other, and other strange effects.
- The only solution: reboot the ProxMox host
Turns out, to use a VLAN on a VM network device you MUST:
- Check "VLAN Aware" when configuring the VM bridge on the ProxMox host
- reboot the host ("apply configuration" is not enough)
- Is there any valid purpose for using a VLAN id on a VM network device, without setting "VLAN Aware"?
- Wouldn't it make sense to warn users when a VLAN id is used, without VLAN Aware checked?
- (In fact, perhaps VLAN Aware could be auto-checked... and a warning given that the ProxMox host may need a reboot!)