June 9, 20251 yr Community Expert Hi there,After updating Unraid to 7.1.3 I cannot access the Unraid host address from a Docker container on br0. The shim-br0 link is up as normal:root@unraid:/boot# ifconfig shim-br0 shim-br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.250 netmask 255.255.255.0 broadcast 0.0.0.0 ether b6:3a:f4:e2:4d:78 txqueuelen 1000 (Ethernet) RX packets 206 bytes 20697 (20.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13 bytes 546 (546.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0For example, my Swag container runs on the custom: br0 network. It can no longer proxy to containers on the bridge network (returning 502). From within Swag (the 'console'), I cannot ping the host's IP address:root@unraid:/boot# docker exec -ti swag ping -c 2 192.168.0.250 PING 192.168.0.250 (192.168.0.250): 56 data bytes --- 192.168.0.250 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet lossAny ideas or advice would be greatly appreciated :)Thanks for reading! Unraid Diagnostics Jun 09 2025.zip
June 9, 20251 yr Community Expert Some users are having connectivity issues with 7.1.3, if you are affected, best to downgrade back to 7.1.2 for now.
June 9, 20251 yr Author Community Expert Thanks. It doesnt seem to be the same connectivity issues others are seeing, though. It's just that the macvlan shim seems to have stopped working
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.