Feature Request: VLAN Tagging

[Matt-CyberGuy]

I don't know much much work it would be to implement... but for our use case for spinning up throw away lab environments, being able to add a VLAN tag would be really useful.

[kroese]

I have no experience with VLANs, but this sounds like something that Docker should support on the container level, not something I can provide in my code.

In any case its possible to put the container inside a Docker macvlan network, and there is even a DHCP mode that allows Windows to get an IP from your DHCP server, its documented here .

[Matt-CyberGuy]

No worries... I figured since the VM's were somehow getting an IP way outside the range of the containers bridge network, and different than the host network, you were doing something fancy with the network stack of the VM. If I figure out a simple work around for this, I'll post it.

[kroese]

All the traffic to the container IP is tunneled to the (dummy) VM IP 20.20.20.21 via a tuntap interface.

If you want to avoid this tunnel/NAT you can enable DHCP=Y, and it will use a macvtap interface, so the VM will be directly connected to the network like a normal device, without any layers in between. As it will get an IP from your router, you can configure your router to put it on a specific VLAN.

[mtido]

I have been following this topic with interest. Is it possible to activate this retrospectively or does it have to be done initially?

Many thanks for this container, I love it.

[Matt-CyberGuy]

Ya, it will definitely be able to be done in post... I use portainer to orchestrate my containers, once I figure out how to do it, I'll post how to do it.