<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Nebula - vo.rs</title><link>https://vo.rs/tags/nebula/</link><description>Latest from the Nebula 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>Fri, 16 Feb 2024 14:45:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/nebula/" rel="self" type="application/rss+xml"/><item><title>Nebula: A Mesh Overlay When Tailscale Isn't Enough</title><link>https://vo.rs/story/nebula-a-mesh-overlay-when-tailscale-isnt-enough/</link><description>&lt;p&gt;Tailscale is the right answer for most people who want their devices to reach each other over an encrypted mesh without port-forwarding. I recommend it constantly. It&amp;rsquo;s WireGuard underneath, the client is excellent, and the magic that lets two devices behind separate NATs find each other just works. There&amp;rsquo;s one thing it asks of you that some of us eventually stop wanting to give: trust in a coordination server you don&amp;rsquo;t run. Tailscale&amp;rsquo;s control plane — the thing that tells your devices about each other and hands out keys — is hosted by Tailscale. For a homelab that&amp;rsquo;s usually fine. But if you want the entire system to keep working when a company&amp;rsquo;s servers don&amp;rsquo;t, or you simply want to own the control plane end to end, you reach a point where you want something else. That something is &lt;strong&gt;Nebula&lt;/strong&gt;.&lt;/p&gt;</description><pubDate>Fri, 16 Feb 2024 14:45:00 +0000</pubDate></item></channel></rss>