OpenVPN traffic split: Difference between revisions

Latest revision as of 13:56, 2 August 2023

Main Page > General Information > Configuration Examples > VPN > OpenVPN traffic split

Introduction

OpenVPN is an open-source software application that implements virtual private network (VPN) techniques for creating secure point-to-point or site-to-site connections in routed or bridged configurations and remote access facilities.

This article provides a guide on how to configure an OpenVPN client on a RUTxxx router in such a way that a part of the router's LAN clients reach the Internet through the OpenVPN server (web proxy) and the other part reaches the Internet through the router's WAN (mobile, wired or WiFi connection). It should also be noted that this guide is aimed at more advanced users and, therefore, skips some of the more self-explanatory steps in order to preserve the overall coherence of the article. For example, the step-by-step configuration of the OpenVPN client instance will be left out and only comments on certain relevant parameters will be provided. If you feel this lack of information impedes your ability to configure the setup, we suggest you check out our OpenVPN configuration examples for reference and our guide on generating TLS certificates.

Configuration overview and prerequisites

Before we begin, let's overview the configuration that we are attempting to achieve and the prerequisites that make it possible.

Prerequisites:

Working OpenVPN connection with OpenVPN server with zone allowing traffic to internet
At least one end device (PC, Laptop) to configure the routers and test the set up

Topology scheme:

The figure above depicts the OpenVPN traffic split scheme. A RUTxxx router acts as an OpenVPN client (virtual IP: 172.16.0.2) that is connected to a remote OpenVPN server (virtual IP 172.16.0.1). The routers LAN/WiFi LAN IP addresses range from 192.168.1x.1 to 192.168.1x.254.

When the scheme is realized, Devices in the LAN range reach the Internet via the router's WAN and devices in the WiFi LAN 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 be done via a command line interface. You can find detailed instruction on all command line interfaces supported by RUTxxx routers 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 as this will make troubleshooting easier later on. The easiest way to do so is to login to the router's WebUI and check OpenVPN status in Status → Services::

If the connection was successful, we can start the traffic split configuration. First, we'll need to Edit LAN network to use IP address 192.168.10.1. It can be done in section Network → Interfaces → General settings:

Wireless LAN interface

Next, we'll need to create wireless interface to use a custom network (wifi_lan) and disable encryption for convenience. In order to do this, navigate Network → Wireless and click edit:

In section Network select Custom and add your preferred interface name. In this example we use WIFI_LAN:

Disable wifi encryption in Wireless security section, by choosing encryption type No encryption. Once you're finished, press Save & Apply and interface configuration windows will appears.
In general settings edit wifi_lan interface to specify IPv4 address (e.g. 192.168.11.1). Press Save & Apply.

VPN interface

Next, we'll need to create new interface ( e.g named VPN). In Physical settings add a tunnel interface name as custom. Tunnel interface name can be checked via ifconfig command via SSH/CLI. In this case it is named "tun_c_Testas". Don’t forget to save configuration.

When your done with the configuration run SSH client or CLI and connect to the router. Once connected execute these commands:

opkg update

This command will update all opkg packages in router. Once update is finished install VPN policy routing using command:

opkg install vpn-policy-routing

After successful installation time to configure VPN traffic splitting. In order to do so one by one execute the following uci commands (be aware that your configuration may vary):

uci set vpn-policy-routing.config.enabled="1"
while uci -q delete vpn-policy-routing.@policy[0]; do :; done
uci add vpn-policy-routing policy
uci set vpn-policy-routing.@policy[-1].dest_addr="192.168.10.0/24 192.168.11.0/24"
uci set vpn-policy-routing.@policy[-1].interface="ignore"
uci add vpn-policy-routing policy
uci set vpn-policy-routing.@policy[-1].src_addr="192.168.11.0/24"
uci set vpn-policy-routing.@policy[-1].interface="VPN"
uci commit

When your done with the configuration, restart VPN policy routing service using:

/etc/init.d/vpn-policy-routing restart

Testing the setup

If you've followed the steps presented above, your configuration should be finished. But as with any other configuration, it is always wise to test the setup in order to make sure that it works properly.

In order to test this particular configuration, check whether devices with IPs from different interfaces reach the Internet through the default gateway. According to our configuration, if a device are connected to WAN interface, its Public IP should be that of the router's or SIM; if the device connected to WiFi LAN, its Public IP should be that of the OpenVPN server. You can check the Public IP address in this website.

If all of the above is in order, congratulations, your configuration works!

External links

http://www.whatsmyip.org/ - for checking your Public IP address

@@ Line 1: / Line 1: @@
 ==Introduction==
-OpenVPN is an open-source software application that implements virtual private network (VPN) techniques for creating secure point-to-point or site-to-site connections in routed or bridged configurations and remote access facilities.
+{{Template:openvpn introduction}}
-This article provides a guide on how to configure an OpenVPN client on a RUTxxx router in such a way that a part of the router's LAN clients reach the Internet through the OpenVPN server (web proxy) and the other part reaches the Internet through the router's WAN (mobile, wired or WiFi connection). It should also be noted that this guide is aimed at more advanced users and, therefore, skips some of the more self-explanatory steps in order to preserve the overall coherence of the article. For example, the step-by-step configuration of the OpenVPN client instance will be left out and only comments on certain relevant parameters will be provided. If you feel this lack of information impedes your ability to configure the setup, we suggest you check out our configuration guides on '''[[How to generate TLS certificates?|how to generate TLS sertificates]]''' and '''[[OpenVPN configuration examples]]''' for reference.
+This article provides a guide on how to configure an OpenVPN client on a RUTxxx router in such a way that a part of the router's LAN clients reach the Internet through the OpenVPN server (web proxy) and the other part reaches the Internet through the router's WAN (mobile, wired or WiFi connection). It should also be noted that this guide is aimed at more advanced users and, therefore, skips some of the more self-explanatory steps in order to preserve the overall coherence of the article. For example, the step-by-step configuration of the OpenVPN client instance will be left out and only comments on certain relevant parameters will be provided. If you feel this lack of information impedes your ability to configure the setup, we suggest you check out our '''[[OpenVPN configuration examples]]''' for reference and our guide on '''[[How to generate TLS certificates (Windows)?|generating TLS certificates]]'''.
 ==Configuration overview and prerequisites==
@@ Line 11: / Line 10: @@
 '''Prerequisites''':
-* A single RUTxxx router (excluding [[RUT850]]) with an active internet connection that will act as the OpenVPN client
+* Working OpenVPN connection with OpenVPN server with zone allowing traffic to internet
 * At least one end device (PC, Laptop) to configure the routers and test the set up
 ----
-'''Configuration scheme''':
+'''Topology scheme''':
-[[File:Openvpn traffic split configuration scheme.jpg|1200px]]
+[[File:OpenVpn schema.png|alt=|749x749px|border]]
-The figure above depicts the OpenVPN traffic split scheme. A RUTxxx router acts as an OpenVPN client (virtual IP: '''10.0.0.6'''; P-t-P: '''10.0.0.5''') that is connected to a remote OpenVPN server. The routers LAN IP addresses range from 192.168.1.1 to 192.168.1.254.
+The figure above depicts the OpenVPN traffic split scheme. A RUTxxx router acts as an OpenVPN client (virtual IP: '''172.16.0.2''') that is connected to a remote OpenVPN server (virtual IP '''172.16.0.1'''). The routers LAN/WiFi LAN IP addresses range from 192.168.1x.1 to 192.168.1x.254.
-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 LAN range reach the Internet via the router's WAN and devices in the WiFi LAN 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.
+Most of the router's configuration will be done via a command line interface. You can find detailed instruction on all command line interfaces supported by 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===
+=== 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.
+*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 as this will make troubleshooting easier later on. The easiest way to do so is to login to the router's WebUI and check OpenVPN status in '''Status → Network → OpenVPN''':
+*Once you have configured your OpenVPN client, you should probably test whether the OpenVPN connection is operational as this will make troubleshooting easier later on. The easiest way to do so is to login to the router's WebUI and check OpenVPN status in '''Status → Services:''':
-[[File:How to check openvpn status.png]]
+[[File:OpenVPN.png|alt=|859x859px]]
 ----
-* If the connection was successful, we can start the traffic split configuration. First, we'll need to add an additional routing table. This can done by issuing the following command:
+*If the connection was successful, we can start the traffic split configuration. First, we'll need to Edit LAN network to use IP address 192.168.10.1. It can be done in section '''Network''' '''→ Interfaces → General settings:''' [[File:LAN.png]]
- echo "<span style="color:red>5 rt</span>" >> <span style="color:red>/etc/iproute2/rt_tables</span>
+===Wireless LAN interface===
-This adds a new routing table called ''rt''. ''/etc/iproute2/rt_tables'' is a file used by the ''iproute2'' utilities which translate user friendly names given on the command line into integer values used by the kernel. So the number ''5'' is just the way for the ''iproute'' to identify the table.
 ----
-* Next, we'll need to some entries to the network configuration file ''/etc/config/network''. You can edit the file with the ''vi'' command. Type '''vi /etc/config/network''' and press the "I" button on your keyboard to begin editing. Add the following lines:
+*Next, we'll need to create wireless interface to use a custom network (wifi_lan) and disable encryption for convenience. In order to do this, navigate '''Network''' '''→ Wireless''' and click '''edit:'''
+[[File:WIFI.png|884x884px]]
- config interface 'vpnas'
-        option proto 'none'
-        option ifname '<span style="color:red>tun_c_MyClient</span>'
- config route
-        option interface 'vpnas'
-        option target '0.0.0.0'
-        option netmask '0.0.0.0'
-        option table 'rt'
-        option gateway '<span style="color:red>10.0.0.5</span>'
- config rule
-        option in 'lan'
-        option src '<span style="color:red>192.168.1.128/25</span>'
-        option lookup 'rt'
-        option priority '10'
 <ul>
 <li>
-When you're finished, press the "Esc" button and type ''':wq''' to save the changes and exit the editor. The values highlighted in red are dependent on your configuration and will most likely need to be changed:
+In section '''Network''' select '''Custom''' and add your preferred interface name. In this example we use WIFI_LAN:
 </li>
-<ul>
+</ul>[[File:Wifi network.png|877x877px]]
-<li>
-option ifname '<span style="color:red">tun_c_MyClient</span>' - your OpenVPN interface's name. You can check it with this command: '''ifconfig | grep tun'''. The response should look something like this (''ifname'' highlighted in red):
+*Disable wifi encryption in '''Wireless security''' section, by choosing encryption type '''No encryption.''' Once you're finished, press '''Save & Apply''' and interface configuration windows will appears.
-<pre>
+*In '''general settings''' edit wifi_lan interface to specify IPv4 address (e.g. 192.168.11.1). Press '''Save & Apply.'''
-<span style="color:red">tun_c_MyClient</span> Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-</pre>
+=== VPN interface===
-</li>
+----
-<li> option gateway '<span style="color:red">10.0.0.5</span>' - your virtual remote endpoint. You can check it with this command: '''ifconfig tun_c_MyClient'''. Replace ''MyClient'' with your own OpenVPN interface name. The response should look something like this:
+*Next, we'll need to create new interface ( e.g named VPN). In '''Physical settings''' add a tunnel interface name as custom. Tunnel interface name can be checked via ''ifconfig'' command via SSH/CLI. In this case it is named "tun_c_Testas". Don’t forget to save configuration.
-<pre>
+[[File:Testas.png|877x877px]]
-tun_c_MyClient Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
-               inet addr:10.0.0.6  P-t-P:<span style="color:red">10.0.0.5</span>  Mask:255.255.255.255
-               UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
-               RX packets:62249 errors:0 dropped:0 overruns:0 frame:0
-               TX packets:62698 errors:0 dropped:1 overruns:0 carrier:0
-               collisions:0 txqueuelen:100
-               RX bytes:53341014 (50.8 MiB)  TX bytes:11974147 (11.4 MiB)
-</pre>
-</li>
-<li>
-option src '<span style="color:red">192.168.1.128/25</span>' - devices from this IP range will reach the Internet via the OpenVPN server
-</li>
-</ul>
-</ul>
 ----
-* Finally, we'll need to add a short custom script to ''/etc/hotplug.d/iface/55-vpn'' that adds a route which makes the specified LAN range reach the Internet via the OpenVPN server:
+*When your done with the configuration run SSH client or CLI and connect to the router. Once connected execute these commands:
+ opkg update
- echo '[ "$ACTION" = "ifup" ] && { ip route add default via 10.0.0.5 table rt }' > /etc/hotplug.d/iface/55-vpn
+*This command will update all opkg packages in router. Once update is finished install VPN policy routing using command:
+ opkg install vpn-policy-routing
+*After successful installation time to configure VPN traffic splitting. In order to do so '''one by one''' execute the following uci commands (be aware that your configuration may vary):
+ uci set vpn-policy-routing.config.enabled="1"
+ while uci -q delete vpn-policy-routing.@policy[0]; do :; done
+ uci add vpn-policy-routing policy
+ uci set vpn-policy-routing.@policy[-1].dest_addr="192.168.10.0/24 192.168.11.0/24"
+ uci set vpn-policy-routing.@policy[-1].interface="ignore"
+ uci add vpn-policy-routing policy
+ uci set vpn-policy-routing.@policy[-1].src_addr="192.168.11.0/24"
+ uci set vpn-policy-routing.@policy[-1].interface="VPN"
+ uci commit
+* When your done with the configuration, restart VPN policy routing service using:
+ /etc/init.d/vpn-policy-routing restart
+----
 ==Testing the setup==
-If you've followed the steps presented above, your configuration should be finished. But as with any other configuration, it is always wise to test the setup in order to make sure that it works properly. In order to test this particular configuration, a few steps have to be taken:
+If you've followed the steps presented above, your configuration should be finished. But as with any other configuration, it is always wise to test the setup in order to make sure that it works properly.
-* Check the newly created routing table with the '''ip route show table rt''' command (where ''rt'' is table's name). If everything is in order, the response should contain this line: <br> <pre>default via 10.0.0.5 dev <span style="color:red">tun_c_MyClient</span> proto static </pre>
+In order to test this particular configuration, check whether devices with IPs from different interfaces reach the Internet through the default gateway. According to our configuration, if a device are connected to WAN interface, its Public IP should be that of the router's or SIM; if the device connected to WiFi LAN, its Public IP should be that of the OpenVPN server. You can check the Public IP address in '''[http://www.whatsmyip.org/ this website].'''
+----
-*ip rule
+If all of the above is in order, congratulations, your configuration works!
-: from all lookup local
- <span style="color:red">10: from 192.168.2.128/25 iif br-lan lookup rt</span>
-: from all lookup main
-: from all lookup default
-</li>
-<li>
-Check whether devices with IPs from different ranges reach the Internet through the default gateway. If you only have one device at your disposal at the time, you can configure a static IP address (guide for Linux users '''[[Setting up a Static IP address on a Ubuntu 16.04 PC|here]]'''; for Windows '''[[Setting up a Static IP address on a Windows 10 PC|here]]''') for that device in one range and later in the other. According to our configuration, if a device's IP falls in the range of 192.168.1.1 - 192.168.1.127, its Public IP should be that of the router's; if the IP falls in the range of 192.168.1.128 - 192.168.1.254, its Public IP should be that of the OpenVPN server. You can check the Public IP address in '''[http://www.whatsmyip.org/ this website].
-</li>
-</ul>
-==See also==
+== See also==
-* [[How to generate TLS certificates?]]
+* Other OpenVPN related articles from our wiki:
-* [[OpenVPN configuration examples]]
+**[[How to generate TLS certificates (Windows)?]] - a guide on generating TLS certificates for Windows users
-* [[VPN#OpenVPN|OpenVPN manual section]]
+**[[VPN#OpenVPN|OpenVPN Manual section]] - OpenVPN section of the router's manual
+**[[OpenVPN configuration examples]] - basic OpenVPN configuration scenarios with detailed examples
+**[[OpenVPN client on Windows]] - an example describing how to configure an OpenVPN client on a Windows computer
+**[[OpenVPN server on Windows]] - an example describing how to configure an OpenVPN server on a Windows computer
 ==External links==
-http://www.whatsmyip.org/ - for checking your Public IP address
+*http://www.whatsmyip.org/ - for checking your Public IP address
+[[Category:VPN]]