Wireguard Peer To Peer Configuration example: Difference between revisions
Wireguard Peer To Peer Configuration example (view source)
Revision as of 14:34, 7 September 2023
, 7 September 2023no edit summary
No edit summary |
No edit summary |
||
| Line 88: | Line 88: | ||
==Peers Configuration Server== | ==Peers Configuration Server== | ||
====Server to Peer Setup==== | ====Server to Peer Setup==== | ||
In the <b>General Setup</b> section you need to enter <b>Public Key<b> and <b>Allowed IPs<b> from the Remote instance you want to connect to. | In the <b>General Setup</b> section you need to enter <b>Public Key</b> and <b>Allowed IPs</b> from the Remote instance you want to connect to. | ||
We will be creating 3 instances, these will be the remote Peers we created above and will make use of their Public Keys to create them, such as below | We will be creating 3 instances, these will be the remote Peers we created above and will make use of their Public Keys to create them, such as below | ||
| Line 116: | Line 116: | ||
[[File:WireGuard_Server_Client3.png]] | [[File:WireGuard_Server_Client3.png]] | ||
==Testing the Setup== | ==Testing the Setup== | ||
===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 | ||
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 | 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 | ||