this post was submitted on 02 Apr 2025
10 points (81.2% liked)
Linux
52752 readers
530 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So in summary you have your device A and services running on B, you connect to a vpn service using A, and you want the services running on B to use the same vpn connection?
I encountered this problem with torrenting and private trackers.
I solved it the other way around, by having the remote connect to the vpn and routing traffic from my device through that remote.
For bonus points you can create a squid (proxy service) container and attach that to wireguard-outbound, then create a firefox profile that connects to that proxy. That way your device isn't routing all traffic through the vpn, only the traffic from that firefox profile.
I've had this set up for several years now and for the most part it works very well. Occasionally I have to restart the containers but for the most part it's great.
I see that containers get lot of love, but really setting up wireguard is writing a text config file, why would you need containers for that?
Well, you don't need containers for wireguard the same way you don't need containers for anything.
I personally prefer docker containers for everything that can be containerised because it provides a consistent abstraction layer. As in, I always know how to find configurations and paths and manage network infrastructure for anything that resides in a container.
In the case I outlined above with the wireguard containers, I'm more confident I'm not going to upset any other services on my server, and I understand the configuration.
Maybe it's a bit like using ufw to manage iptables rules, unnecessary but helpful.
Of course, I freely admit that my way is not necessarily the best way and if someone wants to run wireguard on the host then great.
Thanks for the clarification, it make sense indeed, specially if you don't come from a long term Unix background.
Today Linux world feels more and more unnecessarily complicated somehow. I am getting old.