Mullvad will drop OpenVPN support

[serf]

so long and thanks for all the fish.

I love wireguard and the configuration methods compared to openvpn.

[big-green-man]

This is a good decision all things considered, but there are plenty of hardware vendors with proprietary firmware that only support ovpn and now mullvad is unusable for them. I suppose the onus is on them to support wireguard, but still think of how long it took python3 to become standard after it was released, I hope to see wireguard become the standard soon but I expect lots of vendors will take their time on the transition.

[Arnt]

By "now" you mean "starting in 2026".

Which raises the question: how much warning do you think is reasonable?

[jauntywundrkind]

Never been a Mullvad user, but namespaced-openvpn (https://github.com/slingamn/namespaced-openvpn) was one of the only ways to torrent-over-proxies that I found (years ago); user namespace with the torrent client & openvpn as it's only link out.

Not sure what else folks do for this use case.

[c0balt]

There is gluetun, https://github.com/qdm12/gluetun, which servers a similar purpose whole supporting ovpn and wireguard (including prepared configs for various commercial VPN providers). It's usable with, e. g., Docker to have namespace-based proxying of traffic for a container.

[duskwuff]

Wireguard can be used in a network namespace.

https://www.wireguard.com/netns/