| Manual section: | 8 |
|---|---|
| Manual group: | OpenVPN 3 Linux |
openvpn3-autoload [ OPTIONS ]openvpn3-autoload -h | --help- NOTE!
This feature is deprecated in favour of the
openvpn3-session@.servicesystemd unit.Please see openvpn3-systemd(1) for more details.
The openvpn3-autoload utility is used to automatically load and optionally start VPN configuration profiles from a specific directory. As the OpenVPN 3 Linux client provides fine grained control on both configuration profiles and VPN sessions which are managed outside the main configuration profile, the configuration profiles must be accompanied by a .autoload definition with local site-specific settings.
The openvpn3-autoload utility is provided with a openvpn3-autoload.service systemd unit file which can be enabled and will load configuration profiles located in /etc/openvpn3/autoload.
| -h, --help | Prints usage information and exits. |
| --directory DIR | |
| Required. Directory to look for configuration profiles | |
| --ignore-autostart | |
| Optional. Do not automatically start any VPN sessions which have been configured to start during loading. | |
Traditionally in the OpenVPN 2.x, configuration profiles can contains a lot of options which are both site/host independent and site/host specific. This creates a challenge when distributing configuration profiles, as a profile working for one device in one particular network might not work on a different device or network.
OpenVPN 3 provides a way how to split out the site/host dependent options from the main VPN configuration profile being provided by the VPN provider. In the OpenVPN 3 Linux client, these site/host specific settings are managed via openvpn3 config-manage for configuration profiles already imported. The .autoload configuration files is used to automate setting up these various options without any direct user interaction.
The file format is based on JSON formatting and will carry the
.autoload extension instead of .ovpn or .conf.
The .autoload file must be located in the same directory as the
main configuration file. The base part of filename must be identical with the
.ovpn/.conf file. Example: If the configuration profile is
named vpn-client.conf, the .autoload file must be named
vpn-client.autoload.
The basic layout of an .autoload file is like this:
{
"autostart": BOOLEAN,
"name": "string value",
"acl": {
...
},
"crypto": {
...
},
"remote": {
...
},
"tunnel": {
...
},
"user-auth": {
...
}
}The autostart boolean declares if the configuration profile should be
started once it has been imported into the OpenVPN 3 Configuration Manager.
(Default: false)
By default, all automatically imported configuration profiles will use the
complete profile filename, including the .conf or .ovpn file
extension. If this attribute is set, this string will be used for the profile
name instead of the filename on the filesystem. Beware that the configuration
manager will accept duplicate profile names.
The acl section declares several Access Control Level parameters of
the imported configuration profile. Valid settings are:
"acl": {
"public": BOOLEAN,
"locked-down": BOOLEAN,
"set-owner": UID
}The public element declares if this configuration profile is available
for all users on the system or not. (Default: false)
By setting the locked-down element to true, users granted
access can only start new tunnels with this profile but cannot look look at
the information stored in the configuration profile. (Default: false)
By default all processed configuration profiles will be owned by the user
who runs openvpn3-autoload. The root user on the system can re-assign
the ownership of configuration profiles it imports, like when running this
utility during the system boot. By providing the set-owner element
with the UID of the user who should own this configuration profile, the
ownership will be transferred. This is a feature only available by root.
The crypto section enables fine-tuning some of the configuration
parameters related to the crypto layers of a VPN session.
"crypto": {
"tls-params": {
...
}
}The tls-params sub-section further controls the TLS protocol parameters.
"tls-params": {
"cert-profile": [ "legacy" | "preferred" | "suiteb" ],
"min-version": [ "disabled" | "default" | "tls_1_0" | "tls_1_1" | "tls_1_2" | "tls_1_3" ]
}The cert-profile declares the security level of the TLS channel. Valid
values are:
legacy- Allows minimum 1024 bits RSA keys with certificates signed with SHA1.
preferred- Allows minimum 2048 bits RSA keys with certificates signed with SHA256 or higher.
suiteb- This follows the NSA Suite-B specification.
The min-version defines the minimum TLS version being accepted by the
client. Valid values are:
disabled- No minimum version is defined nor required
default- Uses the default minimum version the SSL library defines
tls_1_0- Requires at least TLSv1.0
tls_1_1- Requires at least TLSv1.1
tls_1_2- Requires at least TLSv1.2
tls_1_3- Requires at least TLSv1.3
Settings in this section is related to the connection to the remote server. It does not support different settings per remote server but is shared for all the remote servers enlisted in the main configuration file.
"remote": {
"proto-override": [ "udp" | "tcp" ],
"port-override": PORT_NUM,
"timeout": SECONDS,
"compression": [ "no" | "yes" | "asym" ],
"proxy": {
...
}
}This forces the VPN client to connect using the given protocol. Valid
values are tcp or udp.
Port number to use instead of the port number defined in the VPN
configuration profile. It must be an integer between 0 and
65535.
An unsigned integer defining how long to wait before trying the next remote entry enlisted in the VPN configuration profile.
Controls how compression settings for the data channel. Valid values are:
no- Compression is disabled
yes- Compression is enabled in both directions
asym- Compression is only enabled for traffic sent from the remote side to the local side.
This sub-section configures the client to start the connection via an HTTP proxy server.
"proxy": {
"host": "proxy-server-name",
"port": "proxy-port",
"username": "proxy-username",
"password": "proxy-password",
"allow-plain-text": BOOLEAN
}String containing the hostname of the HTTP proxy
Unsigned integer defining the port to use when connecting to the proxy server
If the proxy server requires user authentication, this need to contain a string with the proxy username to use.
If the proxy server requires user authentication, this need to contain a string with the password to use.
Boolean flag enabling or disabling the OpenVPN 3 client to transport
the proxy username/password unencrypted. Default: false
The tunnel section defines settings related to the tunnel interface. On some platforms this interacts directly with a tun/tap interface while other platforms may pass these settings via VPN API provided by the platform.
"tunnel": {
"ipv6": [ "yes" | "no" | "default" ],
"persist": BOOLEAN,
"dns-fallback": [ "google" ],
"dns-setup-disabled": BOOLEAN
}Enable or disable the IPv6 capability on the tunnel interface. This can be a string which must contain one of these values:
yes- IPv6 capability is enabled and will be configured if the server sends IPv6 configuration details
no- IPv6 capability is disabled and will not be configured, regardless of what the server provides of IPv6 configuration details
default- Make use of IPv6 if the platform supports it
Boolean flag which enables the persistent tunnel interface behaviour. This
is related to whether the tunnel interface will be torn down and
re-established during re-connections or restarts of the VPN tunnel.
If set to true, the tunnel interface is preserved during such events.
This makes the VPN client configure an additional fallback DNS server on the system. Valid strings are:
google- Configures the system to use
8.8.8.8and8.8.4.4as fallback DNS servers
Defines the DNS query scope. This is currently only supported when enabling the systemd-resolved(8) resolver support in openvpn3-service-netcfg(8). Supported values are:
global: (default)- The VPN service provided DNS server(s) will be used for all types of DNS queries.
tunnel:The VPN service provided DNS server(s) will only be used for queries for DNS domains pushed by the VPN service.
- NOTE
- The DNS domains pushed by the VPN service may be queried by DNS servers with systemd-resolved(8) service if their respective interfaces are configured to do global DNS queries. But other non-listed DNS domains will not be sent to this VPN service provider's DNS server.
Controls whether DNS configurations in the VPN configuration profile or
DNS settings sent from the server will be applied on the system or not.
(Default: false)
This section is only important if the server uses user authentication
methods other than certificate based authentication and this section is
only used if the autostart attribute is set to true.
This is used to automate the client connection as much as possible.
"user-auth": {
"autologin": BOOLEAN,
"username": "string value",
"password": "string value",
"pk_passphrase": "string value",
"dynamic_challenge": "string value"
}If set to true, the client will not ask for username/password as it is
expected that the VPN configuration profile carries the needed settings
providing the identity towards the server. (Default: false)
String containing the username to authenticate as.
String containing the password used for the authentication.
String containing the private key passphrase, which is needed if the private key in the VPN configuration profile is encrypted.
The server might ask the client for a dynamic challenge. If the expected
response is static, the static response can be put here. If the server
expects an OTP token code or similarly dynamic changing input, the
VPN configuration profile is not suitable for autostart.
openvpn3(1)
openvpn3-config-manage(1)
openvpn3-config-manage(1)
openvpn3-systemd(1)