I can not get containers in one LAN to communicate with containers in another VLAN. 

More specificly get a Wordpress container in a vlan2 to connect to mariadb in vlan1. These two containers connects fine when in vlan1. Testing with another container in vlan2 to connect to container in vlan1 also fails. Connections from a device in vlan3 connects to vlan1. Unifi UDM SE network, no blocking policies there. This point to some network issues on the server. Docker custum network = ipvlan.

 

Hopeing to solve this.

 

 

kjell-diagnostics-20250306-1603.zip

On 3/6/2025 at 4:18 PM, frodr said:

I can not get containers in one LAN to communicate with containers in another VLAN. 

More specificly get a Wordpress container in a vlan2 to connect to mariadb in vlan1. These two containers connects fine when in vlan1. Testing with another container in vlan2 to connect to container in vlan1 also fails. Connections from a device in vlan3 connects to vlan1. Unifi UDM SE network, no blocking policies there. This point to some network issues on the server. Docker custum network = ipvlan.

 

Hopeing to solve this.

 

 

kjell-diagnostics-20250306-1603.zip 288.84 kB · 1 download

 

 

Anyone?

Either this is an obsure issue, or it is super easy so I should be able to fix it myself…...

VLAN are use to separate network, so can't communicate each other is normal. 

8 minutes ago, Vr2Io said:

VLAN are use to separate network, so can't communicate each other is normal. 

That can´t be correct in this case. I tested communication between VLANs, it worked, but not when going from a container. I was able to manually include a route, then it was partly working. I expect a routing issue with ipvlan.

11 minutes ago, frodr said:

I expect a routing issue

That could be true if you apply routing rule in Unraid, so Unraid would acting router to route traffic between VLAN. ( I am not sure about that )

But I perform this at router side and I never add routing in Unraid.

Edited March 8, 20251 yr by Vr2Io