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

Linux

63003 readers
417 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
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
19
Help managing access to other people's VPN services (Tailscale, Wireguard, Twingate) to access services from friends (discuss.online)
submitted 2 weeks ago* (last edited 1 week ago) by kiol@discuss.online to c/linux@lemmy.ml
14 comments fedilink hide all child comments
 

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
[–] Haradion@lemmy.ml 3 points 1 week ago

Assuming all the networks are on independent subnets, the kernel's routing tables should mostly send IP traffic in the right direction. For instance, if your LAN is on 192.168.0.0/24, Network A is 192.168.32.0/24, and Network B is 10.0.16.0/16, then on a machine directly connected to all the networks, packets will basically just go to the right place. However:

  • If you want devices on your LAN to be able to reach those other networks without directly connecting, you'll need to set up a routing table for those devices. That's where an OpenWrt (or similar) device comes in.
  • If the networks' subnets overlap, it'll be a rough time. Let's say that Network C is on the same range as your LAN; now you can't directly route to it because your computer doesn't know which instance of 192.168.0.13 you actually wanted to connect to. There are ways around this, but they get more complicated. It's better (if possible) to just have everyone pick non-overlapping subnets.
  • This is just the IP layer. If you want to access services through a domain name, you'll probably want a DNS server (e.g. dnsmasq) that forwards requests to the appropriate name servers for each network. If you have service names or auto-discovery through multicast DNS, you'll need an mDNS reflector to forward the traffic across network boundaries.