I have great news to share with everyone! You asked and we listened, OpenVPN client mode will be officially supported in the 8.1.1 firmware build and the license key will only cost $20!
8.1.0 should be going GA by the end of July and after that we should be able to create a special build of it with this feature supported for those who can’t wait to try it out.
OpenVPN WAN is standalone “WAN” (i.e. a new WAN show on Dashboard). You can configure the priority of the physical WANs to connect to OpenVPN server (similar to IPsec’s “WAN Connection Priority”). You can apply outbound policy, firewall, etc on OpenVPN WAN.
If you added OpeVPn client support to Fusionhub, then we could do Speedfusion Bonding to Fusionhub from Peplink hardware and use a third party commercial VPN provider for anonymous and/or geographic routing of more sensitive/vpn aware traffic like Netflix bbc iplayer etc.
A license for an open standard VPN even if $20 is abit of a harsh. Since it was requested back in 2016 and almost any premium home router has support for both client and server mode nowadays. I was going to suggest you start focusing on new wireguard VPN protocol. Ultra efficient, secure and now core in Linux kernel. A great benchmark for future work related VPNs
The OpenVPN client license is working, however request that you add password support for an encrypted private key. Many OpenVPN servers encrypt the private key by default, and currently the only way to add these profiles to Peplink is to manually decrypt the private key and put the decrypted key back into the OpenVPN profile before adding to Peplink.
The private key password should be able to be saved when the profile is loaded (similar to username/password), or if not saved, then prompted upon login.
For clarification, the encrypted private key is not the same as an OpenVPN username/password.
This feature is standard on OpenVPN Connect client software as shown below.