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.

Regarding link saturation - have you tried tc/wondershaper? https://unix.stackexchange.com/questions/28198/how-to-limit-network-bandwidth#28203

Iptables commands - that was needed at the very launch of wg, I've not had to deal with it for some time now.

Personal/commercial use - I'm on a completely opposite side. It's perfect for personal use, but its lack of dhcp support makes me question its capability in a commercial setting. Many providers offer it, so clearly that's not an insurmountable task, but I'm still curious how they sort out their backend.

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

You got this!

Interesting, I also use KDE (on arch btw) and I definitely have had hours-long work sessions with ssh over a wireguard vpn to access my home PC from abroad, so I imagine the issue is probably not on the KDE side of the stack

These immutable distros always create a thousand little problems like that.

why yall need a vpn?

What? Why?

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.

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

I used to use ddwrt until I didn't have a router (forced by cablemodem that I couldn't modify)
But then I got fiber with a bridge and discovered OpenWRT and it was so incredible.
So much more capable and such a better more competent community.
Much more competent and ethical leadership that doesn't violate the GPL.

How it works, just made more sense to me, there are so many feature I never want to lack in a router and frankly I wish I had in every linux distro.
One of my absolute favorite thing about it, is that anything you click in the web interface, is a command run in the underlying system.

Here I am setting a DHCP tag, which makes it so that all computers with a certain MAC address will receive a non-routing gateway, cutting them off from the internet. I use this to stop my TVs and VMs from connecting to the internet without having to deal with a bunch of static IP addresses and that whole firewall tedium.

Notice how it's giving me the exact commands

And the WebUI shows you all the commands before they run it.
Not only that makes understanding how the system works underneath.
It makes it very easy to reproduce all the same configuration using bunch of commands you can paste from a text file !

Recently I wanted to turn older such routers into dumb wifi access points and they were all mostly the same, so I just flashed them and then ran a series of commands that I learned from the Web UI, with just some things tweaked for each device.

For me that feature alone makes the difference, but also the sketchiness of ddwrt with regards

I think ddwrt gets love because ANYTHING is better than the awful, unreliable stock and locked down web user interfaces on routers. But between ddwrt and openwrt, I think it is no-contest, openwrt is the best choice between those two.

Here is a bunch of articles more about this

https://wi-fiplanet.com/the-dd-wrt-controversy/
https://hackaday.com/2011/09/21/modifying-dd-wrts-protected-gui/
https://ebb.org/bkuhn/blog/2009/12/06/anatomy-gpl-violation.html
https://www.linksysinfo.org/index.php?threads/fresh-tomato-vs-openwrt-vs-dd-wrt.76178/
https://old.reddit.com/r/openwrt/comments/ld05u6/whats_the_difference_openwrt_ddwrt_tomato_opensan/
https://old.reddit.com/r/HomeNetworking/comments/9hk0lm/is_ddwrt_no_longer_recommendedgeneral_opinions_on/
https://www.raspberrypibox.com/dd-wrt-vs-openwrt/
https://news.ycombinator.com/item?id=8060911
https://old.reddit.com/r/HomeNetworking/comments/j5u3kf/why_is_ddwrt_such_a_pain/
https://old.reddit.com/r/linux/comments/3skn25/fcc_we_will_not_ban_ddwrt_on_wifi_routers/

Try openwrt, ddwrt is cancer.

can't with broadcom

Wireguard disconnects so often

Wireguard is udp, it never "connects", there's no session.