Because OpenVPN is fiddly to set up and modern Wireguard setups seem to scale well enough.
I remember maybe 12-15 years ago, setting OpenVPN on my TomatoUSB flashed router, invoking all kind of openssl command to generate certificates, keys, signing stuff, setting the router, setting the TAP/TUN clients etc. but once setup it works for years on my laptop, phone, etc.
Now with WG I basically scan on my phone a QR code generated on my Merlin router and that’s it.
merlin has built-in wireguard support??
yes for a long time now
Try openwrt, ddwrt is cancer.
can’t with broadcom
I hear you, I also have broadcom ewaste, a Trident 2+ switch running open switch and I can never upgrade the debian 9 OS running kernel 4.9.
I had to create a QEMU VM, put proxmox on it and put openwrt into an LXC in that to make it work. Our technology landscape is completely ducked.
EDIT: it’s been pointed out to me that using NetworkManager for Wireguard setup is shit. Instead use nmcli, this seems to have solved my problem.
I’m using Bazzite Linux with KDE, and for me Wireguard setup is copy/pasting several bits of information on multiple settings pages. OpenVPN is just downloading a single config file and inputting my user/pass.
Also, Wireguard disconnects so often, no matter which distro I’m on, that it’s a pain in the butt having to reconnect a few times an hour. Not to mention that I can’t have it set to autoconnect on login, or my internet doesn’t work until I disconnect and reconnect.
Wireguard disconnects so often
Wireguard is udp, it never “connects”, there’s no session.
Wireguard disconnects the WiFi.
However, it has been pointed out to me that my problem was using the GUI for NetworkManager to add the VPN, which apparently is shit for Wireguard. I added the VPN using nmcli instead and so far it’s working as intended.
WG was always so much better anyway.
Well it was written to replace open VPN right? So that makes sense
deleted by creator
Not sure about that. I set up a wg vpn server on a system which then became unresponsive whenever wg was fully saturating the network. Turns out there is apparently no way to throttle or prioritize a wg server, the only way I could think of would be to dedicate a vm to solely the wg vpn and throttle that vm in its networking.
I instead switched to openvpn which can simply be throttled via a line in its configuration.Besides that missing feature, openvpn also doesn’t require figuring out the right iptables commands to verbatim paste into its config as startup and shutdown commands. Setting it up was way easier than wg (though openvpn too wasn’t exactly user-friendly).
WG to me seems too clunky and unfinished for more mainstream usage, though I am sure it wouldn’t be an issue for a large commercial user like mullvad that will have no issue with all that.
Urgh, I don’t really have time to do this migration but guess I’m planning it in anyway.
Past me was a lazy bum. But I’m confident that future me is all over this. Time for a nap.
Damn you sir, you didn’t need to call me out with that last paragraph.
No, I know it wasn’t my shoe, but look at how well it fits!
A bit annoying for all the things that don’t support openvpn, like old Synology NAS devices.
You can install a wireguard spk from blackvoid - Wireguard SPK for your Synology NAS.
Oh that’s interesting, though my model isn’t on the list ;(
Bummer. For whatever reason I always get much better speeds on openvpn servers.
That’s not something you hear very often.
Sounds like an issue with your network or routes. By design, WG is faster.
I’m sure it is, Im just not sure where to start and I get pretty decent speeds on open vpn. I guess now I’m going to have to try to figure it out
Try lowering MTU, just don’t lower it too much.
You got this!
Still just wish mullvad would stop subtracting. First port forwarding and now this. 😕
This post makes it look like there’s something serious ly wrong with openvpn, but it’s just them not wanting to deal with it and deprecating it.
Oh well, guess Ill put a note not to use them. My country blocks VPN protocols and wg specifically, so for my usecase I need as many protocols supported as possible, preferrably mimicking other innocuous protocols.
Good! That shit needs to be phased out.
