31
edits
Changes
Wireguard Peer To Peer Configuration example (view source)
Revision as of 15:43, 7 September 2023
, 15:43, 7 September 2023no edit summary
<li>Please ensure that you save the Public key for later use</li>
<li>Please ensure that you save the Public key for later use</li>
<li>Enter the IP address of the WireGuard Interface on the server (e.g. 10.0.0.1/24) </li>
<li>Enter the IP address of the WireGuard Interface on the server (e.g. 10.0.0.1/24) </li>
[[File:WireGuard_Server.png]]
Please ensure that on the Server side, that you allow the Firewall to accept traffic going through the Server router for Peer-to-Peer traffic to flow
This can be located in <b>Network -> Firewall -> General settings</b>
A zone for WireGuard to WireGuard can be created as below to ensure traffic is not restricted from the server
[[File:WireGuard_Server.png]]
[[File:WireGuard_Firewall_Rules.png]]
==Peers Configuration==
==Peers Configuration==
===Testing===
===Testing===
Once you have setup the WireGuard Server and Peer settings, you can test by making use of the below
Once you have setup the WireGuard Server and Peer settings, you can test by making use of the below
Once you have created your Peers and Host, via the CLI you will be able to see the new WireGuard interfaces and ping across the new VPN, below is an example
Once you have created your Peers and Host, via the CLI you will be able to see the new WireGuard interfaces and ping across the new VPN, below is an example
Show peers and uptime of WireGuard instances with use of “wg” command in the CLI
Show peers and uptime of WireGuard instances with use of “wg” command in the CLI