<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Tailscale on Network Haven</title>
		<link>https://dev.networkhaven.org/tags/tailscale/</link>
		<description>Recent content in Tailscale on Network Haven</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sun, 01 Feb 2026 23:10:03 +0200</lastBuildDate>
		
			<atom:link href="https://dev.networkhaven.org/tags/tailscale/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Hardening your Tailscale VPN for your homelab</title>
				<link>https://dev.networkhaven.org/posts/hardening-your-tailscale-vpn-for-your-homelab/</link>
				<pubDate>Sun, 01 Feb 2026 23:10:03 +0200</pubDate>
				<guid>https://dev.networkhaven.org/posts/hardening-your-tailscale-vpn-for-your-homelab/</guid>
				<description>&lt;p&gt;Tailscale makes it easy to connect devices securely, but its default settings are designed for convenience rather than strict security. Without a few adjustments, every device in your Tailnet can talk to every other one which in my case I don&amp;rsquo;t wanted. So I looked into how to raise my security in using Tailscale for accessing my homelab and now share my findings and results.&lt;/p&gt;&#xA;&lt;h2 id=&#34;general-security-advice&#34;&gt;General Security Advice&lt;/h2&gt;&#xA;&lt;p&gt;Because Tailscale relies on an external identity provider—such as Apple, Microsoft, or Google—it’s essential to secure that account properly.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
