Loading...
Loading...
&#32; submitted by &#32; <a href="https://www.reddit.com/user/gastao_s_s"> /u/gastao_s_s </a> <br/> <span><a href="https://gsstk.gem98.com/en-US/blog/a0090-tailscale-agentic-infrastructure-mesh-networking">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/artificial/comments/1rt899q/the_invisible_wire_175000_naked_ai_agents_a/">[comments]</a></span>
I Traced My Traffic Through a Home Tailscale Exit Node
A blogger describes setting up a Tailscale home exit node and tracing traffic to understand how it differs from a typical VPN. They deployed the exit node as a small LXC container on a Proxmox host (1 vCPU, 512 MB RAM) and used traceroute to github.com, observing the path ultimately egressing via their home ISP public IP. The article explains that without an exit node, Tailscale only routes traffic to other Tailscale devices, while normal internet traffic uses the local network. Enabling an exit node changes the device’s default route so internet traffic is tunneled (WireGuard-encrypted) to the chosen node, which then NATs it to the internet. It emphasizes exit nodes are not anonymity: trust shifts to the exit node, while Tailscale mainly provides a control plane for identity, peer discovery, NAT traversal, and route distribution.
Tailscale’d Into Homelabbing
&#32; submitted by &#32; <a href="https://www.reddit.com/user/gastao_s_s"> /u/gastao_s_s </a> <br/> <span><a href="https://gsstk.gem98.com/en-US/blog/a0090-tailscale-agentic-infrastructure-mesh-networking">[link]</a></span> &#32; <span><a href="https://www.reddit.com/r/artificial/comments/1rt899q/the_invisible_wire_175000_naked_ai_agents_a/">[comments]</a></span>