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!


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 is192.168.32.0/24, and Network B is10.0.16.0/16, then on a machine directly connected to all the networks, packets will basically just go to the right place. However:192.168.0.13you 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.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.