Quick Start Guide for OpenVPN WAN with special firmware 8.1.0s024
NOTE:
The OpenVPN WAN is available as a standard feature (*with optional license) started from firmware 8.1.1GA, you may download the latest GA from the firmware download page.
Step 1: Prior to the configuration, please upgrade the device with the special firmware 8.1.0s024, this firmware version specifically includes our new OpenVPN WAN feature. Next, please visit Store (or via other purchase channels) to acquire the OpenVPN WAN License.
Step 2: Once the license obtained, you can choose to let InControl2 push the license key to the device automatically provided that the device is connected/online in IC2. Or, if you opt to enter the feature activation key manually, please go to System > Feature Add-ons to paste the license key, then click the [Activate] button.
Step 4: The new WAN (default name “OpenVPN WAN 1”) will appear after the device rebooted (firmware 8.1.0s024). Click on that WAN to continue with configuration.
Step 5: Follow the highlighted instructions for the mandatory parameters, you may leave other settings on default. Click [Save] once you are finished filling in the highlighted settings. Click on the [Apply Changes] button to save your settings and to activate the OpenVPN WAN.
Step 6: The router will attempt to contact the OpenVPN server and negotiate to establish the connection. Once negotiation is successful, it will be connected (as shown below). The router is now connected to OpenVPN WAN.
If I bind the OpenVPN to a certain uplink, e.g. Wi-Fi WAN on 2.4Ghz, then both (WiFi WAN on 2.4 GHz, and OpenVPN WAN 1) will be active in the connection status – how can I be sure that all traffic using this uplink is going through the VPN and not directly through the WiFi WAN on 2.4 GHz?
I realize this is a 2021 post, but I wonder if these instructions are current in 2024 with firmware 8.4.1 build 5274 ?
I have a Balance 305 with the a/m firmware. I don’t have an “openVPN license”, or at least I never bought it or installed it (unless something came with the Balance?).
However, going to Advance-OpenVPN I can still setup the openvpn by ingesting the .opvn file generated by my openVPN server (router in another country).
When I then go to Status-OpenVPN, it says “Connected” in green, even if no “OpenVPN WAN” ever appears among the WAN’s or in the dashboard.
Why is it allowing me to do this, and differently from the instructions of this original post?
In any case things are not working properly: when OpenVPN is connected this way, all the devices in the LAN, regardless to which physical WAN they are connected, see the public IP of the openVPN server, with consequent ping delays, no matter what I do with the outbound policy (as I don’t have an "openVPN WAN to route through?).
Also, VPN appears to leak: dnsleaktest.com shows several servers of the various physical WAN’s in different countries.
I am confused, which is the right approach with Balance 305 in 2024 to run openVPN and make sure it does not leak?