Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Zuendapp opened this issue Sep 24, 2024 · 1 comment

Comments

@Zuendapp
Copy link

Zuendapp commented Sep 24, 2024

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
Copy link

geotibi commented Oct 17, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants