Exposed Host in Docker with VLAN

QNAP NAS solution for server virtualization and clustering/HA/FT
Post Reply
tuxikowski
New here
Posts: 3
Joined: Sun Feb 08, 2009 8:17 pm

Exposed Host in Docker with VLAN

Post by tuxikowski »

Hi,
I hope this is the right forum.

I have a TS-531 and use it also to run some Docker-Images.
To separate the clients and two different DMZ I use VLAN in my network.
Here is what I like to have:
My subnetworks:
DMZ1 : 192.168.10.0/24
DMZ2 : 192.168.20.0/24
Clients : 192.168.30.0/24

QNAP interface is connected to DMZ1 directly (without any VLAN-tagging) IP: 192.168.10.100
Docker-App_1 in DMZ1 with IP: 192.168.10.110
Docker-App_2 in DMZ2 with IP: 192.168.20.100
both as exposed hosts

On my switch the port with my QNAP is configured for VLAN 10 (DMZ1) direct without VLAN-tagging and VLAN 20 (DMZ2) with VLAN-tagging.

What have I done:
Created a Docker image Docker-App_1 as exposed host and bind it via virtual_switch_1 to the physical interface to DMZ1
I added the VLAN 20 to my interface. Added a virtual switch (virtual_switch_2) with the binding to VLAN 20. Created Docker image Docker-App_2 as exposed host connected to virtual_switch_2 connected to my VLAN 20. -> works.

Unfortunately the virtual_switch_1 lost its binding to thy physical interface (192.168.10.100) and as a result Docker-App_1 lost connection to.

My question:
How can I bind virtual_switch_1 again back to the interface without re configuring my complete network, the the switch using tagged-only packages on that port?
Or had I done any failure in the configuration, that I am not able to bin the virtual switch to the interface?

I hope I made it clear, what is the problem

Thanks
Post Reply

Return to “Server Virtualization & Clustering”