It's possible to set up tailscale with exit node routing (ie: similar to what Mullvad does) - but it will be your exit node (eg: an on-prem server, a vm you man

It's possible to set up tailscale with exit node routing (ie: similar to what Mullvad does) - but it will be your exit node (eg: an on-prem server, a vm you manage). So that basically allows you to do legacy access control via ip whitelists (only allow IP our.office to talk to your.dmz.service that we develop manage for you). If possible, just bringing the node/servicenin question "into" the wireguard/tailscale network would be better. But good luck getting a hospital to allow you to connect your tailscale to their patient record db (or what have you - obviously in this case you'd hope they have a solid vpn and give you access.. ). For the use case of "talk via vm through mullvad exit node" i suppose you could set up Mullvad on the vm, and tailscale on the vm with Mullvad vpn as exit node, then join all your other nodes to tailscale. Tailscale would replace how you connect to your vm, not mullvad. https://tailscale.com/kb/1103/exit-nodes/ https://tailscale.com/kb/1103/exit-nodes/ https://tailscale.com/kb/1019/subnets/ https://tailscale.com/kb/1019/subnets/