headscale-routing

To advertise local subnets in a Headscale tailnet, you configure subnet routers on gateway nodes to broadcast local LAN subnets, allowing remote access to non-Tailscale devices like NAS boxes. You must then approve these advertised routes on the Headscale server.

Yes, you can route internet traffic through your home network using Headscale by configuring exit nodes on gateway nodes. This secures internet traffic and enhances privacy when connected to untrusted public Wi-Fi networks.

Managing Tailscale subnet routes with Headscale requires python3, tailscale, and curl installed. You also need access to the Headscale CLI or REST API and administrative privileges on the gateway nodes to approve routes.

You approve advertised routes across distributed infrastructure in Headscale by using automated tools to list and authorize network routes. This ensures only approved traffic flows through your network gateways during the route lifecycle.

Yes, this approach works for accessing non-Tailscale devices like printers remotely by advertising local LAN subnets to your tailnet. Subnet routing extends tailnet connectivity to local area networks without requiring Tailscale installation on every device.

Advertised subnet routes may not be working in Headscale because they require explicit approval on the Headscale server before traffic can flow. You must use the Headscale CLI or REST API to list and approve the routes advertised by your gateway nodes.