Difference between revisions of "Template:Networking rutos configuration example openvpn bridge wifi ap use case"

From Teltonika Networks Wiki
Line 173: Line 173:
 
     <tr>
 
     <tr>
 
         <td style="border-bottom: 1px solid white>
 
         <td style="border-bottom: 1px solid white>
Go to '''Network → LAN''' and press '''Edit''' next to your LAN interface:
+
Go to '''Network → Interfaces''' and press '''Edit''' next to your LAN interface:
 
         </td>
 
         </td>
 
     </tr>
 
     </tr>

Revision as of 13:52, 10 July 2020

Networking rutx configuration example openvpn bridge use case topology v2.png

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. Remote Office will also have a separate WiFi AP for guests.

When the scheme is realized, remote office workers will be able to reach HQ’s internal network with all internal systems by connecting to the router via LAN port or by connecting to WiFi AP, which is used for work. All remote office's WAN and LAN traffic is going to travel through VPN tunnel. There will also be a separate WiFi AP for guests, by connecting to it they will only be able to reach WAN, but they won't be able to reach HQ’s internal network.

Configuring HQ office router

Before you start configuring the router turn on "Advanced WebUI" mode. You can do that by clicking the "Basic" button under "Mode", which is located at the top-right corner of the WebUI.

Networking rutx manual webui basic advanced mode.gif

Note: You will need to do that in both, HQ and remote office routers.

OpenVPN


Generating Static key


Networking rutos configuration example openvpn bridge wifi ap use case 1 v1.png

Login to the router's WebUI, navigate to the Services → CLI page and do the following:

  1. Enter username root .
  2. Write the Password of your router.

Networking rutos configuration example openvpn bridge wifi ap use case 2 v1.png

Write the following commands to create OpenVPN Static key, which will be used for authentication:

1) cd /etc/easy-rsa
2) openvpn --genkey --secret static.key

Extracting the key


Linux

If you are using a Linux-based OS, extracting files from the router is simple. Just go to the directory on your PC where you want to relocate the files, right click anywhere and choose the Open in Terminal option. In the Terminal command line use the Secure Copy (scp) command to copy the files from the router. The full command should look something like this:

$ scp [email protected]:/etc/easy-rsa/static.key ./

The [email protected]:/etc/easy-rsa/static.key specifies the path to where the Static key is located (replace the IP address with your router's LAN IP); the ./ denotes that you want to copy the contents to the directory you are in at the moment.

Windows

Winscp login instructions.PNG

If you are using Windows, you can copy files from the router using WinSCP, an Open source freeware SFTP, SCP and FTP client for Windows OS. Use the same login information with WinSCP as with CLI or SSH.

Please note: You must select SCP as File Protocol in WinSCP Session settings.


Winscp interface example.PNG

Once you've connected to the router with WinSCP, copying the files should be simple enough: just go to /etc/easy-rsa/, select the Static key file and drag it to directory on your PC where you would like to store it.

Configuring OpenVPN server


Networking rutx configuration example openvpn bridge use case 4 v2.png

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.


Networking rutx configuration example openvpn bridge use case 5 v2.png

Now apply the following configuration:

  1. Enable instance.
  2. Set TUN/TAP to TAP (bridged).
  3. Enable LZO.
  4. Select Authentication: Static key.
  5. Add Keep alive interval: 10 120.
  6. Upload Static pre-shared key (use the Static.key file you created in previous steps).
  7. Save the changes.

Configuring remote office router

Before you start configuring the remote office router, set a static IP address on the device you are configuring the router with (e.g. 192.168.1.10). You can find instructions on how to do that here:

Ubuntu

Windows

Note: make sure to switch back to automatic DNS and IP address obtaining when you are done configuring the router.

OpenVPN


LAN


Networking rutx configuration example openvpn bridge use case 8 v2.png

Go to Network → Interfaces and press Edit next to your LAN interface:


Networking rutx configuration example openvpn bridge use case 9 v2.png

Apply the following steps:

  1. Change your LAN IP address to: 192.168.1.2
  2. Disable DHCP.
  3. Save the changes.

Configuring OpenVPN client


Networking rutx configuration example openvpn bridge use case 6 v2.png

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.


Networking rutx configuration example openvpn bridge use case 7 v3.png

Now apply the following configuration:

  1. Enable instance.
  2. Set TUN/TAP to TAP (bridged).
  3. Enable LZO.
  4. Select Authentication: Static key.
  5. Write Remote host/IP address (RUTX OpenVPN server public IP).
  6. Add Keep alive interval: 10 120.
  7. Upload Static pre-shared key (use the .txt file you created in previous steps).
  8. Save the changes.

Results

Networking rut configuration example openvpn bridge use case 9 v2.png

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.