So this is annoying me since i startet using unraid. I know its a limitation of docker, but there seems way to avoid it (but i cant figure out how).

 

I would really like a built in unraid way to avoid this problem.

 

So that br0 can reach host and bridges. Maybe a setting unter network settings " [ ] Allow br0 to reach host/bridges (Warning: USE ONLY AT OWN RISK)"

 

 

Edited November 2, 20196 yr by nuhll

One can set up VLANs and fix the issue

Will need a managed switch

 

If its a built in limitation of Docker, I dont think LT devs are going to create some workaround when a viable solution exists

This is not a limitation of Docker, but a deliberate design rule of Docker. Containers must run in isolation and allowing direct communication between host and container will break that rule.

 

I doubt they will change that, but you can always file a complaint at Docker.

 

Edited November 2, 20196 yr by bonienl

20 hours ago, therapist said:

One can set up VLANs and fix the issue

Will need a managed switch

 

If its a built in limitation of Docker, I dont think LT devs are going to create some workaround when a viable solution exists

I dont have a manageable switch. I guess like most private people.

Ive read somewhere something about docker where you can change that behaivior. But i cant find it anymore  there are 1000s of threads about this problem. Some figured a way with iptables, so that could be the way for unraid, i think.

Edited November 3, 20196 yr by nuhll

What about unraid faking a extra NIC? like hopster descriped here: https://forums.unraid.net/topic/84229-dynamix-wireguard-vpn/page/6/