Works for me, client and server side, over UDP and TCP. Not sure about the backwards compatibility issues from the previous 2.4 build re: .ovpn files - I'm only using via the NetworkManager plugin.
This does not work for me: There's a semantic change in --proto udp meaning IPv4 and IPv6 now. As our company's server can be reached via IPv6, but doesn't offer OpenVPN via IPv6, no connection can be established - and OpenVPN doesn't fall back to IPv4.
Now, I could use --proto udp4 instead, alas NetworkManager doesn't offer that as far as I can see.
@thm, that is hardly an OpenVPN package issue. That is an issue which needs to be solved by NetworkManager-openvpn plug-in, which is outside maintained by the NetworkManager team.
You can also "workaround" this by either adding just the IPv4 addresses to the appropriate hostname in /etc/hosts ... or by using an IPv4 address instead of a hostname in NetworkManager.
@dsommers Sorry, but I tend to disagree. This is a change in behavior. The Updates Policy mandates that packages must "avoid changing the user experience if at all possible". Changing the meaning of an option (--proto in that case) is such a change.
This update has been submitted for testing by dsommers.
This update has been pushed to testing.
Works for me, client and server side, over UDP and TCP. Not sure about the backwards compatibility issues from the previous 2.4 build re: .ovpn files - I'm only using via the NetworkManager plugin.
works for me
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
openvpn@.service can't start, see https://bugzilla.redhat.com/show_bug.cgi?id=1435036#c15
This does not work for me: There's a semantic change in
--proto udpmeaning IPv4 and IPv6 now. As our company's server can be reached via IPv6, but doesn't offer OpenVPN via IPv6, no connection can be established - and OpenVPN doesn't fall back to IPv4.Now, I could use
--proto udp4instead, alas NetworkManager doesn't offer that as far as I can see.@thm, that is hardly an OpenVPN package issue. That is an issue which needs to be solved by NetworkManager-openvpn plug-in, which is outside maintained by the NetworkManager team.
You can also "workaround" this by either adding just the IPv4 addresses to the appropriate hostname in /etc/hosts ... or by using an IPv4 address instead of a hostname in NetworkManager.
@dsommers Sorry, but I tend to disagree. This is a change in behavior. The Updates Policy mandates that packages must "avoid changing the user experience if at all possible". Changing the meaning of an option (
--protoin that case) is such a change.