<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IPv6 on Dad's a Nerd!</title><link>https://dadsanerd.com/tag/ipv6/</link><description>Recent content in IPv6 on Dad's a Nerd!</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 13 Aug 2026 12:28:44 -0400</lastBuildDate><atom:link href="https://dadsanerd.com/tag/ipv6/index.xml" rel="self" type="application/rss+xml"/><item><title>VLAN Segmentation on pfSense: Guest &amp; IoT Networks</title><link>https://dadsanerd.com/vlan-segmentation-on-pfsense-guest-iot-networks/</link><pubDate>Tue, 11 Aug 2026 17:31:22 -0400</pubDate><guid>https://dadsanerd.com/vlan-segmentation-on-pfsense-guest-iot-networks/</guid><description>&lt;h1&gt;&lt;/h1&gt;&#10;&lt;p&gt;Split one flat LAN into three isolated networks — trusted LAN, guest Wi-Fi, and IoT — each on its own VLAN and subnet, with firewall rules that actually enforce the isolation rather than just labeling it. Covers renumbering off the default &lt;code&gt;192.168.1.1&lt;/code&gt;, creating the VLANs, and the specific allow/block rules each network needs.&lt;/p&gt;&#10;&lt;h2 id="why-segment-at-all"&gt;Why segment at all&lt;/h2&gt;&#10;&lt;p&gt;A single flat network means every device — laptops, phones, guest devices, smart plugs, cameras, the TV — can see and reach every other device. That&amp;rsquo;s fine until one of them shouldn&amp;rsquo;t be trusted: a guest&amp;rsquo;s phone with unknown malware, or an IoT device with a firmware vulnerability the manufacturer never patched (both a genuine, ongoing category of problem, not a hypothetical). Segmentation means a compromised or just poorly-secured device on the Guest or IoT network can&amp;rsquo;t reach anything on the trusted LAN, because there&amp;rsquo;s no route there to begin with — not &amp;ldquo;we trust it not to,&amp;rdquo; but &amp;ldquo;the firewall doesn&amp;rsquo;t permit it.&amp;rdquo;&lt;/p&gt;</description></item><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><item><title>pfSense WireGuard IPv6 Setup: Full Tunnel and Split Tunnel Guide</title><link>https://dadsanerd.com/pfsense-wireguard-ipv6-setup-full-tunnel-and-split-tunnel-guide/</link><pubDate>Mon, 10 Aug 2026 21:08:26 -0400</pubDate><guid>https://dadsanerd.com/pfsense-wireguard-ipv6-setup-full-tunnel-and-split-tunnel-guide/</guid><description>&lt;h1&gt;&lt;/h1&gt;&#10;&lt;p&gt;Setting up a &lt;strong&gt;home WireGuard VPN&lt;/strong&gt; on pfSense gets you your own private, self-hosted VPN — no subscription, no third-party logging policy to trust, just your own router. This guide walks through a complete &lt;strong&gt;pfSense WireGuard setup with IPv6&lt;/strong&gt; covering both major connection modes (full tunnel and split tunnel), dual-stack &lt;strong&gt;IPv4 and IPv6&lt;/strong&gt; addressing, a stable hostname via Cloudflare Dynamic DNS, and the firewall/NAT rules that actually make traffic pass — not just handshake.&lt;/p&gt;</description></item><item><title>IPv6 Subnetting Explained: Full CIDR Prefix &amp; Usable Range Reference</title><link>https://dadsanerd.com/ipv6-subnetting-cidr-reference/</link><pubDate>Wed, 05 Aug 2026 21:57:48 -0400</pubDate><guid>https://dadsanerd.com/ipv6-subnetting-cidr-reference/</guid><description>&lt;h1&gt;&lt;/h1&gt;&#10;&lt;p&gt;If you learned &lt;strong&gt;IPv6 subnetting&lt;/strong&gt; by carrying over IPv4 habits, a few things break immediately. There&amp;rsquo;s no broadcast address, no &amp;ldquo;network address&amp;rdquo; burned out of every subnet, and the numbers involved are so large that thinking in individual host counts stops being useful past a certain point. This post is a practical IPv6 subnetting reference: what each CIDR prefix actually gives you, how to read the ranges, and a full table you can bookmark.&lt;/p&gt;</description></item></channel></rss>