Template:Networking rutx configuration example openvpn bridge use case
|
Configuration overview and prerequisites
Prerequisites:
- Two RUTX routers
- A Public Static or Public Dynamic IP addresses
- An end device to configure the router (PC, Laptop, Tablet, Smartphone)
The topology above depicts the OpenVPN scheme. The router with the Public IP address (RUTX) acts as the OpenVPN server and other RUTX acts as client. OpenVPN connects the networks of HQ Office and Remote Office.
When the scheme is realized, remote office workers will be able to reach HQ’s internal network with all internal systems, allowing working from remote office to be possible. All remote office's WAN and LAN traffic is going to travel through VPN tunnel.
Configuring HQ office router
OpenVPN
Login to the router's WebUI, navigate to the Services → CLI page and do the following:
|
Write the following commands to create and open OpenVPN Static key, which will be used for authentication: 1) cd /etc/easy-rsa 2) openvpn --genkey --secret static.key 3) cat static.key |
Create .txt file on your computer and copy Static key to it. Copy from the beginning to the end as in the example. |
Now go to Services → VPN → OpenVPN. There create a new configuration by selecting role Server, writing New configuration name and pressing Add button. It should appear after a few seconds. Then press Edit. |
Now apply the following configuration:
|
Configuring remote office router
OpenVPN
Go to Services → VPN → OpenVPN. There create a new configuration by selecting role Client, writing New configuration name and pressing Add button. It should appear after a few seconds. Then press Edit. |
Now apply the following configuration:
|
LAN
Now go to Network → LAN and press Edit next to your LAN interface: |
Apply the following steps:
|
Results
Remote office should now be able to access HQ network resources. To verify the connection you can ping remote RUTX HQ server LAN IP and if you get a reply, you have successfully connected to HQ‘s internal network. Also, all LAN addresses should now be leased to the LAN devices by HQ router. |