Wireguard Peer To Peer Configuration example: Difference between revisions

Revision as of 09:23, 5 September 2023

Main Page > General Information > Configuration Examples > VPN > Wireguard Peer To Peer Configuration example

==Introduction==

Introduction to a Peer-to-Peer WireGuard configuration example, this also covers LAN-TO-LAN connectivity aspect as well.

'''WireGuard''' is simple, fast, lean, and modern VPN that utilizes secure and trusted cryptography.

This page will show you an example on how to configure a basic tunnel between WireGuard interface and its peers.

Note: WireGuard is additional software that can be installed from the Services → Package Manager page (in RUT9/RUT2 this page is located in System → Package Manager).

==Prerequisites==

----

For this example you need:

<ul>

<li>Three RUTOS devices</li>

<li>An end device to configure devices (PC, Laptop, Tablet or Smartphone) </li>

<li>One end device must have Public IP address</li>

<ul>

----

==WireGuard Instances==

To create Instance enter its name and click the Add button.

Then click the Edit [[File:Networking_rutx_manual_edit_button_v1.png]] button to configure it.

[[File: Wireguard.png]]

[[File: Wireguard_Add.png]]

==Server Configuration==

===Peer to Peer Setup===

The following part of example applies to both devices.

Before editing any fields click [[File:Networking_rutx_manual_generate_button_v1.png]] button to generate Public and Private keys.

After that you need to Enable this instance and in the Listen Port field enter your desired port. WireGuard by default uses 51820 port which will be used in this example.

Lastly you need to enter IP Address for instance. We will set the SERVER will have 10.0.0.1 and Clients will have 10.0.0.2 IP addresses and increasing.

Note: enter IP address and its mask e.g. 10.0.0.1/24

Note: You will need to copy the Public and Private Keys for Peer instances between server and Clients

<ul>

<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>

<ul>

[[File:WireGuard_Server.png]]

==Peers Configuration==

==Peer to Peer Setup==

In the General Setup section you need to enter Public Key and Allowed IPs from the Remote instance you want to connect to.

In this example a peer from Client1 needs to connect to RUTX11, which means SERVER will enter Public Key and Allowed IPs from Client1.

You will need the Public Keys of the Client VPN users that you setup, so it is recommended to create the Instances to Generate the Keys for use of Peer instances

==Peers Configuration Client 1==

Client 1 is setup with the following details, WireGuard Interface IP is set as 10.0.0.2 with a LAN range of 192.168.5.0/24

You will need to create a new WireGuard instance and Peer connection, please ensure you copy the public Key that was generated via the creation of the instance, as this will be used on the Server side for the VPN.

<ul>

<li>Copy the Public Key and save it in a text file for later use, as it will be used on the Server Peer configuration</li>

<li>Enter the IP address of the WireGuard interface e.g. 10.0.0.2/24</li>

<li>Now we will Create a Peer connection</li>

<li>Point 1 is the Server’s Public Key that was acquired when creating the instance on the Server/Main router side</li>

<li>Allowed IPs are the IP ranges you want to have access to over the VPN (the remote side) </li>

<li>Please ensure you enable “Route allowed IPs” </li>

<li>Under “Advanced Settings” please ensure you enter the Server side Public IP address</li>

<li>Save and Apply the settings</li>

<ul>

[[File:WireGuard_Client1.png]]

[[File:WireGuard_Client1_IP_list.png]]

[[File:WireGuard_Client1_HostEnd.png]]

==Peers Configuration Client 2==

Client 2 is setup with the following details, WireGuard Interface IP is set as 10.0.0.3 with a LAN range of 192.168.10.0/24

You will need to create a new WireGuard instance and Peer connection, please ensure you copy the public Key that was generated via the creation of the instance, as this will be used on the Server side for the VPN.

<ul>

<li>Copy the Public Key and save it in a text file for later use, as it will be used on the Server Peer configuration</li>

<li>Enter the IP address of the WireGuard interface e.g. 10.0.0.3/24</li>

<li>Now we will Create a Peer connection</li>

<li>Point 1 is the Server’s Public Key that was acquired when creating the instance on the Server/Main router side</li>

<li>Allowed IPs are the IP ranges you want to have access to over the VPN (the remote side) </li>

<li>Please ensure you enable “Route allowed IPs” </li>

<li>Under “Advanced Settings” please ensure you enter the Server side Public IP address</li>

<li>Save and Apply the settings</li>

<ul>

[[File:WireGuard_Client2.png]]

[[File:WireGuard_Client2_IP_list.png]]

[[File:WireGuard_Client2_HostEnd.png]]

==Peers Configuration Client 3==

Please ensure you download WireGuard for your PC (Windows Client)

Installation: https://www.wireguard.com/install/

Once you have created a new Tunnel, you will need to add the below lines of code to finish the VPN setup,

<ul>

<li>Address = 10.0.0.4/24</li>

<li>PublicKey = Which will be the Server’s Public Key</li>

<li>AllowedIPs = IP ranges you want access to (Remote side) </li>

<li>EndPoint = Server’s IP (our instance was 192.168.1.1 as it was part of the LAN) </li>

<ul>

[[File:WireGuard_PC_Client.png]]

==Peers Configuration Server==

==Server to Peer Setup==

In the General Setup section you need to enter Public Key and Allowed IPs 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

[[File:WireGuard_Server_Clients.png]]

==Server To Client 1==

Create your 1^st client peer under the server

<ul>

<li>Enter the Public Key you created for Client 1</li>

<li>Enter in the IP address you want to access on Client 1 side(LAN side and WireGuard Interface IP) </li>

<li>Ensure you have enabled “Route allowed IPs” </li>

<ul>

[[File:WireGuard_Server_Client1.png]]

==Server To Client 2==

Create your 2^nd client peer under the server

<ul>

<li>Enter the Public Key you created for Client 2</li>

<li>Enter in the IP address you want to access on Client 2 side(LAN side and WireGuard Interface IP) </li>

<li>Ensure you have enabled “Route allowed IPs” </li>

<ul>

[[File:WireGuard_Server_Client2.png]]

==Server To Client 3 (PC)==

Create your 3^rd client peer under the server

<ul>

<li>Enter the Public Key you created for Client 2</li>

<li>Enter in the IP address you want to access on Client 3 side(LAN side and WireGuard Interface IP) </li>

<li>Ensure you have enabled “Route allowed IPs” </li>

<ul>

[[File:WireGuard_Server_Client3.png]]

==Testing the Setup==

===Testing===

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

This can be located in Network -> Firewall -> General settings

A zone for WireGuard to WireGuard can be created as below to ensure traffic is not restricted from the server

[[File:WireGuard_Firewall_Rules.png]]

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

[[File:WireGuard_Test_Interface.png]]

Ping LAN to LAN

[[File:WireGuard_Server_Test.png]]

Ping PC Client to Client 1

[[File:WireGuard_Client_to_Client_Test.png]]

@@ Line 225: / Line 225: @@
 A zone for WireGuard to WireGuard can be created as below to ensure traffic is not restricted from the server
-<nowiki>[[File:WireGuard_Firewall_settings.png]]</nowiki>
+<nowiki>[[File:WireGuard_Firewall_Rules.png]]</nowiki>
 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