How to Configure a WireGuard VPN Between Robustel Routers

How to Configure a WireGuard VPN Between Robustel Routers

Overview

If you need a fast, secure, and easy-to-configure open-source VPN to connect remote networks, WireGuard utilizes the latest encryption technology to provide a streamlined solution. This guide explains how to establish a WireGuard VPN connection between two Robustel routers (Router-A and Router-B) so that devices on their respective local networks can communicate with each other using virtual IPs.

 


Topology

 

What You'll Need

Hardware List:

● 2 x Robustel Routers (e.g., Router-A and Router-B)

● 2 x PCs (PC1 connected to Router-A, PC2 connected to Router-B)

● Active internet connections for both routers (WAN access)

Network Information Requirements:

● Router-A WAN IP (e.g., 172.16.70.25) and LAN subnet (e.g., 192.168.0.0/24)

● Router-B WAN IP (e.g., 172.16.70.31) and LAN subnet (e.g., 192.168.10.0/24)

● Desired Virtual IPs for the VPN tunnel (e.g., 10.0.0.10/24 for Router-A and 10.0.0.1/24 for Router-B)

● A generated Preshared Key to be used on both devices (e.g., NvhqdR8rCvH3BfDfp7Q5fd9UOMFIDIEbT48EESSTT3w=)

 

Step-by-Step Configuration Guide

Phase 1: Router-A Configuration (Generate Keys and Set Interface)

1.  Navigate to VPN > WireGuard > x509 on Router-A's web interface.

2.  Click Generate next to Private Key, then click Export to save it.

 

3.  Navigate back to the WireGuard tab, click Save & Apply. The private key will automatically populate in the settings.



4. Return to the x509 tab and click Generate next to Public Key, then click Export. Save this public key string, as it is required for Router-B.

 

5. Go to the WireGuard tab and locate General Settings.

6.  Enter 10.0.0.10/24 into the IP Address field to set the local virtual interface IP.

Phase 2: Router-A Configuration (Peer Settings)

1.  Scroll down to Peer Settings on the WireGuard tab and click the + (add) button.

2.  Enter the Public Key that was generated by Router-B.

3.  Enter the Preshared Key (e.g., NvhqdR8rCvH3BfDfp7Q5fd9UOMFIDIEbT48EESSTT3w=).

4.  Enter Router-B's WAN IP (172.16.70.31) into the Endpoint Host field.

5.  Enter 51820 into the Endpoint Port field.

6.  Enter Router-B's virtual IP and LAN subnet (10.0.0.1/24,192.168.10.0/24) into the Allowed IPs field.

7.  Toggle Route Allowed IPs to ON so it automatically generates the required routes.

8.  Click Submit, then Save & Apply.

Phase 3: Router-B Configuration

1.  Repeat the key generation process from Phase 1 on Router-B.

2.  Set the IP Address in General Settings to 10.0.0.1/24.

 

3. In Peer Settings, enter the Public Key generated by Router-A.

4.  Enter the exact same Preshared Key used on Router-A.

5.  Enter Router-A's WAN IP (172.16.70.25) into the Endpoint Host field.

6.  Enter 51820 into the Endpoint Port field.

7.  Enter Router-A's virtual IP and LAN subnet (10.0.0.10/24,192.168.0.0/24) into the Allowed IPs field.

8.  Toggle Route Allowed IPs to ON, submit, and save.

Verification & Testing

Once configured, you should verify that Router-A and Router-B can communicate using their virtual IPs.

1.  On Router-A's interface, navigate to System > Tools > Ping.

2.  Enter Router-B's virtual IP (10.0.0.1) in the IP Address field and click start.

3.  Look for a successful response indicating 0% packet loss in the ping statistics.

4.  Test the LAN-to-LAN connection by pinging PC2 (192.168.10.2) from Router-A's ping tool, and PC1 (192.168.0.31) from Router-B's ping tool.



Finally, use the command prompt on PC1 to ping PC2 directly to confirm end-to-end communication.

Troubleshooting / FAQ

Q: Why is my WireGuard VPN not establishing a connection?

A: Ensure that you have correctly swapped the Public Keys between the two routers. Router-A must have Router-B's public key in its Peer Settings, and Router-B must have Router-A's public key.

Q: Why can't the two sides ping each other?

A: Check that the Preshared Key matches exactly on both Router-A and Router-B. The key acts as a password and must be identical (using standard a-zA-Z0-9 and + / = formatting). Also, verify that the Endpoint Hosts reflect the correct opposite WAN IPs.

 

Revision History

Version

Date

Author

Changes

1.0

2026-03-26

Hubery

Initial document creation.