2 ms·
Just to further clarify as I've recently gone down the rabbit hole of Tailscale...but isn't the idea that I can make any part of the device running on a private
by mbesto 4y ago
Just to further clarify as I've recently gone down the rabbit hole of Tailscale...but isn't the idea that I can make any part of the device running on a private, secure network? In other words, even if I'm connected to a node, I'm still running "on my network", whereas when I connect to a traditional VPN service it just kinda takes all of my traffic and puts it in that same network "space", the biggest difference meaning I no longer see a traffic hit when I'm reaching www.google.com because it doesn't mean all of that traffic has to get funneled through the VPN traffic.
As you can tell, not a network guy here! I could be totally wrong.
- e1g 4y agoBy default, and in the most common configuration, the Tailscale “idea” is to intercept all network requests made to a reserved IP range (100.x.x.x) that cannot have public services on it (similar to 192.168.x.x). Each of your devices gets a static IP and can reach any other of your devices using their static IP. All traffic will be encrypted, and it will work really really hard to get through all NAT gateways and firewalls in-between. As those static IPs are in a reserved range, they will never clash with a public service like a website and Tailscale does not mess with your regular traffic. You could make things more complicated by setting up exit nodes and exposing subnets, but that’s the general idea. So simple, it’s brilliant for their standard use-case.