Creating a Tunnel on a Guest VM where OVS Bridges, Interfaces and Tunnels are Present

[minorsatellite]

I have a guest VM that was just provisioned for network monitoring running on a Proxmox host where VLAN-aware OVS interfaces already exist for the numerous VLANs that currently pass tagged-traffic to my VMs. The design goal is to create a trunked interface on the Linux guest so that it can communicate with ALL of the same VLANs present on the OVS bridge. What I have read so far seems to suggest that I need to create a new Linux bridge for this setup, but context is important, and I am not sure if this would be compatible with my OVS environment. Also, I don't see any detailed instructions on how to pull this off.

I am hoping here that someone has previously come across a setup like this and can give me so guidance.

Thanks in advance.

 

[ggoller]

You can just add the VM to the existing ovs bridge and leave the VM interface untagged. This should make it an access port and it should allow all vlans.

 

[minorsatellite]

Hi, this actually DOES NOT work. If i remove the current VLAN ID (101) I can no longer access the VM at all over the native VLAN (101) Thoughts?

 

[tschmidt]

If it worked with the tag set in the VM config the vlan probably isn't native. Try tagging it in the VM itself.