GNOME Bugzilla – Bug 773623
OpenVPN plugin doesn't support connection profiles
Last modified: 2020-11-12 14:34:51 UTC
OpenVPN supports multiple connection profiles within the same file and will try them sequentially until one succeeds. From the openvpn man page: Here is an example of connection profile usage: client dev tun <connection> remote 198.19.34.56 1194 udp </connection> <connection> remote 198.19.34.56 443 tcp </connection> <connection> remote 198.19.34.56 443 tcp http-proxy 192.168.0.8 8080 http-proxy-retry </connection> <connection> remote 198.19.36.99 443 tcp http-proxy 192.168.0.8 8080 http-proxy-retry </connection> persist-key persist-tun pkcs12 client.p12 ns-cert-type server verb 3 [...] The following OpenVPN options may be used inside of a <connection> block: bind, connect-retry, connect-retry-max, connect-timeout, explicit-exit-notify, float, fragment, http-proxy, http-proxy-option, http-proxy-retry, http-proxy-timeout, link-mtu, local, lport, mssfix, mtu-disc, nobind, port, proto, remote, rport, socks-proxy, socks-proxy-retry, tun-mtu and tun-mtu-extra. --- Since our VPN configuration is a dictionary and can't have nested sections, we should probably define an encoding that uses prefixes to represent the profiles; for example: dev = tun connection0_remote = 198.19.34.56 connection0_proto = udp connection0_port = 1194 connection1_remote = 198.19.34.56 connection1_proto = tcp connection1_port = 443 ... See also: https://mail.gnome.org/archives/networkmanager-list/2016-October/msg00039.html
Are there any plans to include this feature in future versions?
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).