[cjonash]

Thanks for the info. It was working, exactly as you wrote.

[alvaroag]

Yes, that's it. Works perfectly for me under Linux; I suppose vmware should make no difference, as VLAN is a standard.

[cjonash]

So if I understand you correctly, I can use any VLAN id I want for each of my virtual networks? And for the WAN network (the one with the IP block) I leave it without a VLAN id?

[alvaroag]

That's exactly the same setup I have since two years ago :-) you just have to set the VLAN tag for each VM. But, consider that the IP blocs do not have VLAN option, so the VM interfaces which need to see those blocs will have to be without VLAN.

[cjonash]

Is it possible to use VLAN tagged traffic between servers connected with vRack?

The scenario is:

I have several servers today, which are connected to the same vRack. Also in the same vRack is a pool of IP addresses.
All the servers is running VMWare, and one virtual machine is running pfSense.

Today all the virtual machines are just connected to the same virtual LAN which is the vRack LAN.

I want to separate traffic between certain virtual machines, by creating multiple virtual LAN in vmware and tag those with VLAN tags.

Is that possible? And if so, do I need to do anything else than choosing my VLAN tags? Can I use any id's, or do I somehow need to activate them in the OVH manager?

The public traffic (using the IP's in the pool) will just remain untagged, I guess?

As this is a production environment, I would like to not just test it...

I am thankful for any information!