75
edits
Changes
Wireguard Peer To Peer Configuration example (view source)
Revision as of 09:29, 15 January 2024
, 15 Januaryno edit summary
*An end device with the ability to install, set up WireGuard client, and configure RUTOS devices<br>
*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.
'''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==
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===
