<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Headscale - vo.rs</title><link>https://vo.rs/tags/headscale/</link><description>Latest from the Headscale desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 13 Feb 2024 10:20:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/headscale/" rel="self" type="application/rss+xml"/><item><title>Headscale: Self-Hosting Tailscale's Control Plane</title><link>https://vo.rs/story/headscale-self-hosting-tailscales-control-plane/</link><description>&lt;p&gt;Tailscale&amp;rsquo;s pitch has always been that the hard part of a mesh VPN — key exchange, NAT traversal, relay fallback — is handled by a coordination server you never have to think about. I&amp;rsquo;ve written before about &lt;a href="https://vo.rs/story/tailscale-a-zero-config-mesh-vpn/"&gt;what Tailscale actually is&lt;/a&gt; and why that model is such a relief after a decade of hand-rolled WireGuard configs. The catch is that &amp;ldquo;you never have to think about it&amp;rdquo; also means &amp;ldquo;someone else&amp;rsquo;s infrastructure is a required dependency of your home network,&amp;rdquo; which sits uneasily on a site that otherwise argues for self-hosting everything it reasonably can. Headscale is the answer: an open-source, largely API-compatible reimplementation of Tailscale&amp;rsquo;s control plane that you run yourself. The clients don&amp;rsquo;t change at all — you point the standard Tailscale app at your own server instead of &lt;code&gt;login.tailscale.com&lt;/code&gt;, and everything else about the mesh behaves the same.&lt;/p&gt;</description><pubDate>Tue, 13 Feb 2024 10:20:00 +0000</pubDate></item></channel></rss>