this post was submitted on 18 Aug 2025
480 points (99.0% liked)
Technology
74265 readers
4188 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
WG was always so much better anyway.
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.
Yeah, to be honest, WG out of the box is really nice for tunneling and static IP road warriors. For larger deployments it's a bit of a PIA without DHCP.
Sadly.
But things like Netbird make it a bit easier.