Replies: 3 comments 3 replies
-
|
Maybe this helps? https://github.com/mjtechguy/wireguard-site-to-site |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I know how to configure that "by hand" (manually with .conf file). I don't know how to achieve that using WGDashbard. It's possible to configure that with https://github.com/ngoduykhanh/wireguard-ui, but I'm interested with WGDashboard statistics. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Any news? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I have two locations (geographically separated):
On first network there is a host with Wireguard server (with manual configuration - for example 10.0.0.1/32). There is a static route which is directing other clients (from this network) to VPN through host with VPN server. All hosts from this network can communicate with hosts from second network.
On second network there is a host with Wireguard client (for example 10.0.0.2/32). There is a static route which is directing other clients (from this network) to VPN through host with VPN client. All hosts from this network can communicate with hosts from first network.
How it's possible?
On server's configuration:
On peer's configuration:
By giving extra 192.168.2.0/24 in peer's configuration on server's side the hosts from first network have access to whole second network.
How to add an extra allowedIPs for peer on server's side in WGDashboard?
Beta Was this translation helpful? Give feedback.
All reactions