- Urgent
I have a custom docker bridge network, that hosts most of my containers, including swag proxy. I also have a custom macvlan network, that hosts my containers that need a unique IP, like home assistant.
With the 'Host access to custom networks' I was able to reach home assistant from Unraid and from swag, but after updating to rc5 this option no longer works.
I can ping Unraid host from swag successfuclly, but from home assistant I am unable to ping Unraid host (and vice versa). Pinging from/to other computers from home assistant works fine.
This is breaking reverse proxy for me, as well as communication between home assistant and other containers (e.g. zigbee2mqtt).
After full server restart I've just stopped getting IP altogether, server sits at 169.**.
EDIT: Going back to rc4 didn't fix anything, still sitting at 169.** reporting full connectivity with the switch, everything seems fine in GUI mode, but Unraid ignores (?) DHCP.
EDIT2: Somehow, restarting my switch fixed DHCP issue. Weird, cause other Unraid I have is connected to the same switch and it updated yesterday just fine. Original issue with docker accessing host persists.
EDIT3: Rolled back to rc4, it fixed the docker <-> host access issue. Something must be up with rc5 not respecting that option.
-
2
-
1
