Hi folks,

 

Hope somebody can point me in the right direction. I've been running Unraid for a year or so and have never had any issues after updating to the latest versions. However since updating from 7.0.0 to 7.0.1, I've found that the Unraid host is not able to find a route to docker containers that use the br0 network.

 

Other devices on the network can access those containers, and even other containers can access those containers via their br0 IP address, so it's only the Unraid host > docker container via br0 that can't communicate where it previously could.

 

For example:

• Unraid host has IP address 192.168.0.120
• A docker container uses the br0 network and has IP address 192.168.0.130
• Devices on the wider network can ping the container.
• But the Unraid host can't.

 

I'll attach a couple of screenshots below if they help.

 

Thanks folks.

 

Unraid docker settings:

 

 

Ping from Unraid host to docker container via br0 address:

 

Edited March 2, 20251 yr by Goblin
Added "not solved" tag.

Forgot to add, this is what my routing table looks like in Unraid Network Settings:

 

Please post the diagnostics and the output from 

docker network ls

 

Hi Jorge,

 

I've attached a screenshot of the docker network ls command output:

 

 

Which parts of the diagnostic zip should I attach? I'd need to go through and censor parts of it as there are a lot of personal details in path names, etc. (I know, bad practice) that show up a fair bit.

 

Thanks,

Goblin.

 

So, I just figured out that the update from 7.0.0 to 7.0.1 had switched my br0 network type from macvlan to ipvlan. By switching the type back to macvlan, the Unraid host can now reach containers via their br0 IP addresses.

Oh no, I lied. After an Unraid reboot, the host can no longer reach containers using their br0 IP address.

FYI - The reason why the Unraid host needed to be able to reach a container via br0 is because I run a docker registry in a container (on 192.168.0.130) and I have the Unraid host use that registry as well as other devices outside of Unraid using it too. All via a single domain, e.g. docker.mydomain.com -> 192.168.0.130 (container running the registry).

 

What I'm doing at the moment to work around the Unraid host not being able to reach the container via br0 is using split horizon DNS for docker.mydomain.com so that the Unraid host receives the private docker network IP address of the registry container, whereas everybody else receives the br0 address (192.168.0.130). Not ideal, but is working for now.

 

Given this workaround is working ok for me right now, I'll probably switch my br0 network back to ipvlan as I know thats more stable and recommended than macvlan.

Edited March 2, 20251 yr by Goblin

Macvlan is no longer a problem, so you can use the one that works best for you.

Hello, I am facing the same issue, but this is the first time I have enabled "host access to custom networks", so I cannot say it's related to the Unraid version. My br0 custom network type is macvlan.

 

Unraid IP address 192.168.8.8, the container using br0 has 192.168.8.107. I can access the container from devices outside Unraid, while I cannot from Unraid itself and other containers not on br0.

 

I have temporary fixed creating an LXC container, and running the container there.

Edited March 18, 20251 yr by mrsparkle

I never got this fixed, so had to workaround by using a docker IP address to access the container from the host, and use spilt horizon DNS to decide which IP to return based on who was asking.

I had it working as well before and today I had an issue and figured the I could not reach my unraid IP from br0 on macvlan.

Since the latest upgrade it is not working.

Tried to reboot, switch docker off and on again, tried to disable and re-enable "Host access to custom networks".

 

I can't get it back.