<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Multi-Site on Dad's a Nerd!</title><link>https://dadsanerd.com/tag/multi-site/</link><description>Recent content in Multi-Site on Dad's a Nerd!</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 13 Aug 2026 12:27:32 -0400</lastBuildDate><atom:link href="https://dadsanerd.com/tag/multi-site/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi-Site VPN on pfSense: Connect Multiple Locations with WireGuard (No Vendor Fees)</title><link>https://dadsanerd.com/multi-site-vpn-pfsense-wireguard/</link><pubDate>Tue, 11 Aug 2026 16:11:27 -0400</pubDate><guid>https://dadsanerd.com/multi-site-vpn-pfsense-wireguard/</guid><description>&lt;p&gt;Connects multiple pfSense-routed locations into one routed, dual-stack (IPv4 + IPv6) network using WireGuard — a self-hosted &lt;strong&gt;multi-site VPN on pfSense&lt;/strong&gt; in a hub-and-spoke topology. No NAT, no per-site static IP requirement, no recurring vendor fee.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Terminology note:&lt;/strong&gt; the underlying technique here is a &lt;strong&gt;site-to-site VPN&lt;/strong&gt; — a permanent, routed tunnel connecting two networks. &amp;ldquo;Multi-site&amp;rdquo; just means using that same technique more than once: a hub site runs a separate site-to-site tunnel to each additional location. Two sites is the base case (one tunnel, one peer on each end); three or more is that same setup repeated, with the hub acting as the common point. Nothing about the core configuration changes as sites are added — Step 2 through Step 5 are simply repeated per additional spoke.&lt;/p&gt;</description></item></channel></rss>