Closed dsommers closed 4 months ago
@dsommers cool, thanks a lot for pointing out that. I'll work on updating this gh action to follow the new approach.
If it makes it easier for you, OpenVPN 3 Linux is based on D-Bus so you can manage it directly this way. It also ships with an openvpn3
Python 3 module, where you can do all the things you do with the openvpn3
command line tool.
A few examples:
@dsommers thanks for the docs. Actually, for this project I want to keep it simple using bash and exposing a way to run any command, so people can use that for simple and complex things.
Hi,
I'm the upstream maintainer of the OpenVPN 3 Linux project and I just stumbled across this project. I just wanted to give a heads up that the
openvpn3-autoload
approach is being deprecated and will at some point be removed in a later release.The approach to use now is:
Import the configuration profile using
$ openvpn3 config-import --persistent --config ${CONFIG_FILE} --name ${CONFIG_NAME}
Start the VPN session using either:
systemctl enable --now openvpn3-session@${CONFIG_NAME}
or
openvpn3 session-start --config ${CONFIG_NAME}
The former will automatically start the connecting on each boot, the latter needs to be run each time you want to start the VPN connection.
The
${CONFIG_FILE}
itself may now also contain<auth-user-pass>...</auth-user-pass>
tags if username/password auth is required; this will be further hardened with support for keyring services and such.If there are additional settings which was configured via the
.autoload
file, they can now be set properly viaopenvpn3 config-manage --config ${CONFIG_NAME}
. See theopenvpn3-config-manage
(1) man page for details