On selecting server/remote from the GUI

An experimental support for using --management-query-remote with the GUI is here:

https://github.com/selvanair/openvpn-gui/tree/query-remote-v2

Comments / tests would be much appreciated.

Depends on two proposed changes to OpenVPN core:

(i) Have an option to query the daemon for the list of remotes available
We could work around this by parsing the connection entries / remotes in the config file , but querying this via management looks more logical, and more reliable to me. If remote-random is in use, parsing the config is not an option as ordering consistent with the daemon is important for an efficient implementation (see (ii) below).

https://patchwork.openvpn.net/patch/1942/

(ii) Extend the "remote SKIP" management command to take an argument for skipping multiple remotes.
Without this, --management-query-remote is pretty much unusable when there are more than couple of remote entries. Each command sent to the management takes up to a second to get acted on causing long delays if a large number of remotes have to be skipped one by one. This also requires a consistent ordering of the remote entries in the daemon and the GUI.

https://patchwork.openvpn.net/patch/1945/

OpenVPN feature branch including these patches: https://github.com/selvanair/openvpn/tree/query-remote

The list could be sorted alphabetically by clicking on any column header. A location icon could be added to the list but currently there is no support in the config file for such metadata in connection entries.

Start by reviewing the query-remote-v2 branch and the linked OpenVPN core patches 1942 and 1945. Test selecting a server or remote from the GUI against the query-remote core branch, including configurations with multiple remotes; done means the experimental flow works without long per-remote delays.