Wireguard Site-to-Site / Externals clients cannot reach remote Site-to-Site subnet
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Wireguard Site-to-Site / Externals clients cannot reach remote Site-to-Site subnet
Hi!
Wireguard mesh Site to Site connection working ok.
When an external client tries to connect it can only reach WG server subnet only, but the mesh network.
Do I have to add those routes as static?
Why Routing table does not show Wireguard routes?
Hope this example clarifies:
R1, R2, R3, all connected as Wireguard mesh.
LAN1 (R1) can ping any R2 or R3 subnet.
LAN2 (R2) can ping any R1 or R3 subnet.
LAN3 (R3) can ping any R1 or R2 subnet.
So far, so good.
>>> Here is the problem:
When a client (outside those buldings) connect with WG VPN to R1, it can ping LAN1 only.
How can I solve this?
I'll appreciate your help!
