75
edits
Changes
Wireguard Peer To Peer Configuration example (view source)
Revision as of 09:29, 15 January 2024
, 15 Januaryno edit summary
*Three RUTOS devices with different LAN networks
*Three RUTOS devices with different LAN networks
*One RUTOS device will need to have a '''Public IP''' address
*One RUTOS device will need to have a '''Public IP''' address
*An end device with the ability to install, set up WireGuard client, and configure RUTOS devices
*An end device with the ability to install, set up WireGuard client, and configure RUTOS devices<br>
'''Note:''' remember to switch the '''WebUI''' into '''Advanced''' mode.
==Topology used in this example==
[[File:Wireguard peer to peer config example topology v3.png|border|class=tlt-border]]
==WireGuard instance creation==
==WireGuard instance creation==
*Set an IP address. For the '''server''' set '''10.0.0.1/24'''. For the '''clients''' set the IP to '''10.0.0.2/24 and higher'''. For example, client #1 – IP 10.0.0.2/24, client #2 – IP 10.0.0.3/24, and so on
*Set an IP address. For the '''server''' set '''10.0.0.1/24'''. For the '''clients''' set the IP to '''10.0.0.2/24 and higher'''. For example, client #1 – IP 10.0.0.2/24, client #2 – IP 10.0.0.3/24, and so on
Below is an example of the server’s WireGuard interface:<br>
Below is an example of the server’s WireGuard interface:<br>
[[File:WG server interface.png|border|class=tlt-border]]
[[File:Wireguard server interface config example v1.png|border|class=tlt-border]]
==Peers Configuration==
==Peers Configuration==
===Client 3 configuration===
===Client 3 configuration===
Firstly, ensure that you have downloaded and installed WireGuard client (https://www.wireguard.com/install/) for your PC. To create client #3 to server/peer configuration, follow these steps:
Firstly, ensure that you have downloaded and installed WireGuard client ([https://www.wireguard.com/install/ wireguard.com/install]) for your PC. To create client #3 to server/peer configuration, follow these steps:
*Launch the WireGuard software
*Launch the WireGuard software
*At the bottom of the left corner select '''Add Tunnel → Add empty tunnel…'''
*At the bottom of the left corner select '''Add Tunnel → Add empty tunnel…'''<br>
[[File:Wireguard client create new empty tunnel v1.png|border|class=tlt-border]]<br>
*In the configuration window add these settings:
*In the configuration window add these settings:
Address = 10.0.0.4/32
Address = 10.0.0.4/32
[Peer]
[Peer]
PublicKey = 2JIBoK+Bxe7MJzX9zV+lFjqHxLTvehLp3piEROaNJjw=
PublicKey = 2JIBoK+Bxe7MJzX9zV+lFjqHxLTvehLp3piEROaNJjw=
AllowedIPs = 10.0.0.0/24, 192.168.1.0/24, 192.168.6.1/24
AllowedIPs = 10.0.0.0/24, 192.168.1.0/24, 192.168.6.0/24
Endpoint = 192.168.9.1:51820
Endpoint = 192.168.9.1:51820
*Enable '''Route allowed IPs'''
*Enable '''Route allowed IPs'''
*Press [[File:Save apply button.png]]
*Press [[File:Save apply button.png]]
The configuration could look like this:<br>
[[File:Wireguard server to PC client peer v1.png|border|class=tlt-border]]
The final results could look like this:<br>
The server interface's peers section could look like this:<br>
[[File:Wireguard server to client all peers v2.png|border|class=tlt-border]]
[[File:Wireguard server to client all peers v2.png|border|class=tlt-border]]
You will see the interface's and its peers' information. In the peer information section look for the latest handshake (a line below allowed IPs). If you can see “latest handshake” it means the peer made a connection to the server.
You will see the interface's and its peers' information. In the peer information section look for the latest handshake (a line below allowed IPs). If you can see “latest handshake” it means the peer made a connection to the server.
This is an example of how the command’s output could look like:<br>
This is an example of how the command’s output could look like:<br>
[[File:WG show output v1.png|border|class=tlt-border]]
[[File:Teltonika Networks WG show output v3.png|border|class=tlt-border]]
'''Note:''' if you do not see the latest handshake line, then try pinging the server’s Public IP (the one specified in the Endpoint Host parameter) and/or server’s VPN IP (in this example it would be the 10.0.0.1) from each peer.
===Checking the connectivity between the peers===
===Checking the connectivity between the peers===
