Hi team.
I am deploying a HASS solution centralized on siteA, trying to manage devices at SiteA and SiteB. HAOS runs as a VM at PROXMOX virtual Environment.
The idea is to setup a VPN using wireguard: the wg addon for HASS at SiteA and de wireguard service embedded at RT200 router at SiteB.
Just to say I can not configure static routing at SiteA Router, but my idea is that just HASS server had access to SiteB noone else at SiteA
Currently wireguard VPN is running and working fine for my Phone and for a Windows labtop. Setting up the VPN for SiteB, it works fine from SiteB to SiteA (Ping OK, logging , etc) but HASS does not reach/discover any device at SiteB. HASS SSH Terminal Ping doesn´t work for any IP at 192.168.2.0, neither for 10.8.0.1 or 10.8.0.2
I have done at HASS via SSH Terminal:
sudo ip route add 192.168.2.0/24 via 172.30.33.1
and traceroute to 192.168.2.1 reach wiregurad IP, but no more….
No work
Any help on this, please?
• Site A:
o PROXMOX virtual environment 9.1.9
o HAOS 17.2 as a VM
Wireguard addon on 0.13.0
o Ip-address subnet: 192.168.0.0/24
o Router ip-address : 192.168.0.1
o Home assistant host ip-address: 192.168.0.47
o Wireguard addon:
docker container ip-address: 172.30.33.1
Server IP: 10.8.0.1
o Public url: sitea.duckdns.org.
• Site B:
o Teltonika RT200 router
o Ip-address subnet: 192.168.2.0/24
o Router ip-address : 192.168.2.1
o VPN Wireguard service enabled:
IP 10.8.0.2
Here my Wireguard YAML config:
server:
host: sitea.duckdns.org
addresses:
- 10.8.0.1/24
dns:
- 1.1.1.1
peers:
- name: siteB
public_key: Iuv0mjM5yCnRodB39KHKwgDM9TPKypBAM0qB7IEHk=
addresses:- 10.8.0.2/32
allowed_ips: - 10.8.0.2/32
- 192.168.2.0/24
client_allowed_ips: - 192.168.0.0/24
- 10.8.0.2/32
- name: MovilPhone
addresses:- 10.8.0.3/32
allowed_ips: - 10.8.0.3/32
client_allowed_ips: - 192.168.0.0/24
- 10.8.0.3/32
- name: PC
addresses:- 10.8.0.4/32
allowed_ips:
- 10.8.0.4/32