Release candidate 2 for v3.41.4 - pre-release
🙏 I know you'all busy playing GTA VI, but if you get some time, please go ahead and test out image tag :v3.41.4-rc2 to see if it works for you compared to v3.41.3! Report issues with v3.41.4-rc2 as part of your your issue title 🙏
This contains many (sometimes very large) fixes backported from the master branch to the v3.41 branch, and it's not that tested, I would appreciate if anyone finds a regression.
I will leave this for a few days, then release v3.41.4 if everyone's happy with the release candidate, and then release (finally duh!) v3.42.0 right after (master branch as it is, it's ready I think).
Doing exceptionally a pre-release since the master branch (aka v3.42.0) is basically 11 months of feature/maintenance ahead of v3.41, so it's getting tedious to do bugfixes for v3.41. After v3.42.0, I'll - I know, I know, I said that last time - do feature releases more often.
Release content for v3.41.4:
Fixed
- Wireguard:
- No transient traffic leaking when the tunnel goes down - IP rules are now removed only after the tunnel interface is deleted, so packets can no longer escape unencrypted during a disconnect or on shutdown (#3510).
- Both an IPv4 and an IPv6 address can be configured at once, and IPv6 support is only required for the IPv6 one (#3447).
- VPN port forwarding
- NAT-PMP port forwarding is retried when the router refuses the connection, not only on timeouts (#3464).
- Provider specific
- PureVPN updater fixed (#3165): refresh it yourself with command
update -enduser -providers purevpn(see wikiservers.md) - NordVPN:
- dedicated-IP servers are no longer selected by default (#3497) - they reject the credentials of a normal subscription, so a plain
SERVER_COUNTRIESsetup hitAUTH_FAILEDon roughly one server in five. They are now only used when explicitly requested withSERVER_CATEGORIES=Dedicated IPorSERVER_HOSTNAMES. - Configuration hint: entering a 48-byte key now tells you to use the NordVPN access token, which is what was actually expected (#3514).
- Updater keeps the servers that have no region instead of dropping them.
- dedicated-IP servers are no longer selected by default (#3497) - they reject the credentials of a normal subscription, so a plain
- ProtonVPN:
- Private Internet Access port forwarding: the forwarding API is now reached through the actual tunnel gateway, so forwarded ports work instead of timing out (#3472).
- PureVPN updater fixed (#3165): refresh it yourself with command
- Control server:
- HTTP proxy tunnels: bytes already buffered by the HTTP server when a connection is hijacked are forwarded, fixing stalled
CONNECTrequests for some clients (#3481) - Servers updater
- The periodic loop no longer hangs (#3473)
- Public IP:
- a banned or rate-limited fetcher no longer causes the remaining fetchers of the same round to be skipped (#3506).
- IPv6
- Neighbour discovery packets sent to the container are now accepted (#3475).
- Startup fixed on older kernels with IPv6 enabled: unreachable IPv6 routes are ignored instead of aborting the connection.
- Error messages are no longer occasionally truncated, output of sub-commands (for example OpenVPN) is fully captured before it is reported (#3465)
- Built-in TLS root certificates updated
- The account used to drop privileges is now written correctly to the system password file: its group identifier was missing, so the user was not recognised and was appended again at every start (#3533).
- File and directory permissions:
/gluetunand/tmp/gluetun(and the status files written into them) are created with usable permissions whatever the container umask is, which matters when running as a non-root user with mounted volumes (#3471). - Startup version check now reports the actual GitHub error instead of an opaque JSON decoding error.
- Housekeeping: migration from github.com/qdm12/gluetun to github.com/passteque/gluetun.
PS: as usual sorry for the spam of releases notification in case you're subscribed to github releases, the build pipeline has been capricious with me this evening...