stable

openvpn-2.4.1-1.fc25

FEDORA-2017-51ae70f9a0 created by dsommers 7 years ago for Fedora 25

Updates to upstream OpenVPN v2.4.1. Also adds newer upstream versions of systemd unit files (openvpn-client@.service, openvpn-server@.service).

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2017-51ae70f9a0

This update has been submitted for testing by dsommers.

7 years ago

This update has been pushed to testing.

7 years ago
User Icon dimitrisk commented & provided feedback 7 years ago
karma

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.

User Icon cserpentis commented & provided feedback 7 years ago
karma

works for me

This update has been submitted for stable by bodhi.

7 years ago

This update has been pushed to stable.

7 years ago
User Icon nucleo commented & provided feedback 7 years ago
karma
BZ#1435036 openvpn-2.4.1 is available
User Icon thm commented & provided feedback 7 years ago
karma

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.

User Icon dsommers commented & provided feedback 7 years ago

@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.

User Icon thm commented & provided feedback 7 years ago

@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.


Please login to add feedback.

Metadata
Type
enhancement
Karma
0
Signed
Content Type
RPM
Test Gating
Autopush Settings
Unstable by Karma
-1
Stable by Karma
2
Stable by Time
disabled
Dates
submitted
7 years ago
in testing
7 years ago
in stable
7 years ago
BZ#1435036 openvpn-2.4.1 is available
-1
0

Automated Test Results