Routing problem with clients in the same net as the Homeassistant host to remote site

[Zuendapp]

Hello!

yesterday I set up the Wireguard plugin. I was previously running a native Raspbian OS with Wireguard (natively, not in a Docker container).
I configured the tunnel so that each site (a second Rasperrypi at a remote site as a client) could connect to the different networks on the other side and vice versa! This worked perfectly.

With the HomeAssistantOS Wireguard addon, I have the problem that my other clients (on the same network as the HAOS RaspberryPi) at one site can no longer reach the other remote site (from the server side to the client site). On the other way (from the server to the remote site) and with my remote devices (notebook, iPhone) it works fine.

HA-OS IP: 192.168.1.50/24
Wireguard Server IP: 10.7.0.1
Wireguard Remote Site Client IP: 10.7.0.2
Fritz!Box Router: 192.168.1.0/24 (Routes to 10.7.0.0/24) added

Do I have to enter a manual route in the Homeassisstant Host for the 10.7.0.0/24 network to the container (Wireguard Addon)?

Thank you very much!

[geotibi]

Same issue for me. From wireguard network I can access everything but from local network were home assistant is I cannot access the devices from wireguard network.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[bobb16]

Same problem for me. From the client - LAN, I can get a connection to any device in server - LAN and to other clients, but it is not possible form the server LAN to connect to a device in the client - LAN. How can this be set/fixed?

[he3amo]

Same problem for me. From the client - LAN, I can get a connection to any device in server - LAN and to other clients, but it is not possible form the server LAN to connect to a device in the client - LAN. How can this be set/fixed?

It's not an addon problem. The addon uses the “virtual” network interface of the docker, that cannot access resources on the internal network. SOLVE