Upgrade to a version of "OpenVPN-gui" that is at least 22.214.171.124 this will allow for additional command line flags to allow for connect and disconnect.
The Commit... and details:
Merged to the main branch. April 23rd https://github.com/OpenVPN/openvpn-gui/pull/230
Until Devolutions fixes the OpenVPN Plugin:
Create a Custom VPN type with the Correct Data.
HOST: Whatever name(Its only displayed)
Executable: C:\Program Files\OpenVPN\bin\openvpn-gui.exe
Opening arguments: --command connect SOME_PROFILE_DEFINED_IN_CONFIG_DIR
Closing arguments: --command disconnect SOME_PROFILE_DEFINED_IN_CONFIG_DIR
Tested... works. against:
OpenVPN 2.4.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on May 11 2017
library versions: OpenSSL 1.0.2k 26 Jan 2017, LZO 2.10
Windows version 6.2 (Windows 8 or greater) 64bit
Sorry, but I am not sure to understand your feature request.
Could you elaborate on this request please?
The current OpenVPN Add-on (126.96.36.199) uses the OpenVPN-gui.exe to initiate a connection. Unfortunately, when you try to initiate an additional connection, the OpenVPN Add-on tries to open a NEW instance of the OpenVPN-gui.exe, then the application complains that its already open, and the connection fails.
The reason for this is due to the way your opening the connection using OpenVPN-GUI.exe It wont allow multiple instances of the GUI to run.
There has been an update that was MERGED into the source tree for OpenVPN-GUI that allows a command to be sent to the new process that will open a new connection, and more importantly close a SINGLE connection, instead of the killing of the process that you currently do.
I would like to have the NEW Feature in the OpenVPN Add-on to allow for this new connection parameter so that we can establish more than one connection, and close different connections, while leaving other connections still connected.
The details of the Modification to the code is located here: https://github.com/OpenVPN/openvpn-gui/pull/188
It was Added to the MAIN source tree here: https://github.com/OpenVPN/openvpn-gui/pull/230
Test Executable is here: https://github.com/selvanair/openvpn-gui/releases/tag/v11_testing1
This is indeed a really nice feature to have. It has been added to the todo list of our engineering department.
I will notify you as soon as I have any update on that matter.
Thank you for your patience on the implementation of this new feature. That being said, our engineering department would like to know the following:
1- What is the command line you are using to open two OpenVPNs inside the same executable?
2- What is the command line you are using to close only one of these OpenVPNs without closing the other?
James, see my post from yesterday in the Addon section;
I did not know it's now possible to also send multiple commands to an active openvpn-gui. Great find thomas09!
The most elegant option might be to make use of the OpenVPN Interactive Service, that gives RDM greater control of the VPN's (not just a 'send command and hope the GUI works and picks it up') but calling openvpn-gui multiple times would at least give us the option to open multiple vpn connections at once plus this way the Gui icon in the systray also shows the active VPN connections.
Multiple connections would be a very welcome addition, currently we have to constantly switch active VPN's when working on multiple sites at once
It is necessary to add more TAP interfaces, which can easily be achieved by running;
The OpenVPN will just use any available TAP interface, but it is also possible to specify a specific interface by using the dev-node operand
I presume RDM launches openvpn-gui.exe --connect somefile.ovpn --config_dir "somedir"
This does not allow for multiple instances.
If we want to achieve multiple active VPN-connection we would have to start openvpn.exe like such;
openvpn.exe --config somepath\somefile.ovpn --auth-user-pass somepath\somefile.txt
Where somefile.txt (if used) has the username on the first line, and the password on the second line.
It is however necessary to run this with elevated rights, and the commandline window remains open.
The Open-VPN GUI bypasses this by addressing the OpenVPN interactive service;
https://community.openvpn.net/openvpn/wiki/OpenVPNInteractiveService (bit outdated info)