Changes

1,348 bytes added ,  10:37, 14 June 2018
no edit summary
Line 21: Line 21:     
When the scheme is realized, Devices in the 192.168.1.1 to 192.168.1.127 IP range reach the Internet via the router's WAN and devices in the 192.168.1.128 to 192.168.1.254 IP range reach the Internet via the OpenVPN server effectively "adopting" the server's Public IP address.
 
When the scheme is realized, Devices in the 192.168.1.1 to 192.168.1.127 IP range reach the Internet via the router's WAN and devices in the 192.168.1.128 to 192.168.1.254 IP range reach the Internet via the OpenVPN server effectively "adopting" the server's Public IP address.
 +
 +
==Router configuration==
 +
 +
Most of the router's configuration will done via a command line interface by executing SSH commands. For examples provided in this guide, we will be using the Linux '''Terminal''' application. This is not the only available method. You can find detailed instruction on all command line interface available in RUTxxx routers '''[[Command line interfaces|here]]'''. Choose one that is available or most preferred by you and you will still be able to follow the guide step-by-step regardless of which method you chose as the commands used will remain identical.
 +
 +
===OpenVPN client===
 +
 +
* First, you must create an OpenVPN client instance on your router. You can do this either via command line or from the router's WebUI, '''Services → VPN → OpenVPN''' section. We will not go into further detail on this because the client's configuration will depend on the OpenVPN server that you are connecting to. You can find detailed instructions on how to create and configure an OpenVPN client instance in our '''[[OpenVPN configuration examples]]''' article, which also contains information on how to configure an OpenVPN server on a RUTxxx router, if that is what you are using for this configuration.
 +
----
 +
* Once you have configured your OpenVPN client, you should probably test whether the OpenVPN connection is operational.

Navigation menu