this post was submitted on 02 Feb 2026
18 points (100.0% liked)

Linux

62172 readers
1554 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

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS
 

cross-posted from: https://discuss.online/post/34942012

I find everyone using different services, so unsure how to best manage (and balance) concurrent access in Ubuntu/Debian to:

  • Local network services
  • Tailscale services from userA
  • Tailscale services from userB
  • Wireguard (OpenVPN also option) from userC
  • Twingate from userD

Each user is wanting to share different services via VPN, and pressuring any to change their production setups to a different style of VPN is not going to happen.

  • Management via software
  • Possibly up a routing device along the lines of OpenWrt or OpnSense.
    • Could even distribute such devices between these friends.

Thanks for all thoughts!

you are viewing a single comment's thread
view the rest of the comments
[–] INeedMana@piefed.zip 2 points 17 hours ago

Personally, I would do this in docker. That way you can have clearer separation between services and networks. But it's not a hard requirement.

I would just do it, as you wrote. For example, on the account of jellyfin server, configure the tailscaleA client, then wireguard client, etc. Set those up as separate user services/processes/system services if root permissions needed and that's it. Then on other services set the needed connections separately.
It might be handy to set up traefik, so things served via vpns can go through the same routes as local traffic, so you use the same path as your users do

When you have a service that serves something on a port, you are not limited to only one connection. It can be accessed through different clients, the only needed part is that those clients connect to their respective vpn networks and pass the traffic correctly

I don't see a need for a separate device for that routing