Devolutions ForumDevolutions Forum

OpenVPN - an improved way

OpenVPN - an improved way

avatar
maayant

Hi,

We are evaluating RDM 10 enterprise.
While testing the application and reading posts here on the forum I've noticed you are invoking OpenVPN tunnels using the openvpn-gui.exe .

I was wondering why not use the openvpn.exe executable instead, as it has many more features and options, including allowing a better implementation for multi-user environments, and with the added benefit of bypassing known openvpn-gui bugs such as defaulting the passphrase window to RTL language (if an RTL language is installed), its annoying tray icon that never dies unless you move your cursor over it. This might also resolve the must run as administrator problems I've seen in some posts here.

As a very simple example that mimics the openvpn-gui connection:
C:\Program Files\OpenVPN\bin\openvpn.exe --config "C:\Program Files\OpenVPN\config\SITENAME\configname.ovpn" --pkcs12 "D:\Program Files\OpenVPN\config\SITENAME\pkcsfile.p12"
Now just pass the passphrase to it.

To see the full list of options: openvpn.exe --help

Thanks.
edited by maayant on 9/23/2014

All Comments (2)

avatar
David Hervieux

Hi,
You have a good point. I think it times for us to rework the OpenVPN add-on. For now you could use the Generic VPN add-on and use the command line to make it works.

David Hervieux

avatar
maayant

Thanks.

We've managed to use the basic OpenVPN addon for multi-user by naming the ovpn file for each site the same in every computer, and rename the pkcs12 file as [username].pkcs12, we then used the $USERNAME$ variable in the pkcs12 file name field in RDM.
This is a pretty ugly solution, and forces our RDM users to change file names for existing and new vpn tunnels. A much better way will be to be able to set "User Specific Settings" in the RDM OpenVPN module of course.