Feature #2646
closed
Seems too limited, not allowing multiple configs. I wouldn't want that as the default.
Other solutions like surun also work. http://forums.openvpn.net/topic9030.html
Now sure what we can do about that in the export setup... It's really up to the end user to set that up, since it varies from machine to machine.
- Status changed from New to Rejected
People can implement that hack on their own, or use surun. The proper solution is coming with the new OpenVPN client which we'll implement when it's available.
Stumbled upon this one:
http://openvpn-mi-gui.inside-security.de/
Description
OpenVPN MI GUI is a Windows graphical user interface for the OpenVPN client management interface.
It is based on the OpenVPN GUI by Mathias Sundman (version 1.0.3 from August 2005) which is shipped with OpenVPN, but had large parts of the backend adapted by Boris Wesslowski from Inside Security GmbH, commissioned by Conergy AG.
OpenVPN versions 2.1.x and 2.2.x are supported.
Purpose
The original OpenVPN GUI encounters the following problems especially in enterprise or high security environments:
Users have no administrative rights, but unprivileged users do not have enough permissions to add and delete routes.
The GUI will exit on user logout closing all VPN tunnels and preventing e.g. remote VNC logins by an administrator.
The OpenVPN service wrapper can start one or more OpenVPN instances with enough rights, but the GUI has no control over them.
OpenVPN running as a service can not request passwords for certificates or user authentication data from the user directly or through the GUI.
The OpenVPN MI GUI talks to the management interfaces of OpenVPN instances started through the service wrapper and can overcome the above problems.
Someone has already added code to the export package for OpenVPNManager as an option, which does the same thing that does. (Might even be the same software, I haven't tried it much)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by