<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Homelab / RockLAN &#8211; Tatom Enterprises HQ</title>
	<atom:link href="https://blog.tatomenterprises.com/category/homelab-rocklan/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.tatomenterprises.com</link>
	<description>Builders from the Ground Up — rooted in Tatom: Father + Homestead.</description>
	<lastBuildDate>Sun, 18 Jan 2026 21:01:55 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
	<item>
		<title>Networking</title>
		<link>https://blog.tatomenterprises.com/networking/</link>
					<comments>https://blog.tatomenterprises.com/networking/#respond</comments>
		
		<dc:creator><![CDATA[Paul Tatom]]></dc:creator>
		<pubDate>Sun, 18 Jan 2026 21:01:53 +0000</pubDate>
				<category><![CDATA[Homelab / RockLAN]]></category>
		<guid isPermaLink="false">https://blog.tatomenterprises.com/?p=27</guid>

					<description><![CDATA[Extending &#38; Future Upgrades PurposeThis runbook captures the correct architecture, terminology, decision points, and upgrade paths for extending RockLAN networking to outbuildings (shop, sheds, barns) using wireless bridges, VLAN isolation, and roaming Wi‑Fi, without trenching or legacy technical debt. 1. Core Principles (Non‑Negotiable) If any design violates these principles, stop and reassess. 2. Correct Terminology [&#8230;]]]></description>
										<content:encoded><![CDATA[
<div class="wp-block-group is-layout-flow wp-block-group-is-layout-flow">
<div class="wp-block-group has-global-padding is-layout-constrained wp-container-core-group-is-layout-2837dcf3 wp-block-group-is-layout-constrained">
<h1 class="wp-block-heading">Extending &amp; Future Upgrades</h1>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>Purpose</strong><br>This runbook captures the <em>correct architecture, terminology, decision points, and upgrade paths</em> for extending RockLAN networking to outbuildings (shop, sheds, barns) using <strong>wireless bridges, VLAN isolation, and roaming Wi‑Fi</strong>, without trenching or legacy technical debt.</p>
</blockquote>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">1. Core Principles (Non‑Negotiable)</h2>



<ul class="wp-block-list">
<li><strong>No buried copper between buildings</strong></li>



<li><strong>Wireless bridge replaces underground conduit</strong></li>



<li><strong>Isolation is enforced centrally (OPNsense + VLANs)</strong></li>



<li><strong>Backhaul ≠ Wi‑Fi mesh</strong></li>



<li><strong>AP roaming ≠ mesh backhaul</strong></li>



<li><strong>10/100 gear is scaffolding only, never infrastructure</strong></li>
</ul>



<p>If any design violates these principles, stop and reassess.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">2. Correct Terminology (Canonical Definitions)</h2>



<h3 class="wp-block-heading">Wireless Bridge (PtP / PtMP)</h3>



<ul class="wp-block-list">
<li>A <strong>Layer‑2 Ethernet replacement</strong> over RF</li>



<li>Transparent to VLANs and protocols</li>



<li>Example: <em>Ubiquiti airMAX NanoStation / LiteBeam</em></li>
</ul>



<h3 class="wp-block-heading">Backhaul</h3>



<ul class="wp-block-list">
<li>The link <strong>between buildings</strong></li>



<li>In RockLAN: <strong>wireless bridge = wired backhaul equivalent</strong></li>
</ul>



<h3 class="wp-block-heading">Wi‑Fi Roaming (What users usually mean by “mesh”)</h3>



<ul class="wp-block-list">
<li>Multiple APs</li>



<li>Same SSID / security</li>



<li>Client devices roam automatically</li>



<li><strong>Preferred with wired (or bridged) backhaul</strong></li>
</ul>



<h3 class="wp-block-heading">Mesh Backhaul (Not Recommended Here)</h3>



<ul class="wp-block-list">
<li>APs relay traffic wirelessly between themselves</li>



<li>Each hop reduces throughput</li>



<li>Higher latency and instability</li>
</ul>



<h3 class="wp-block-heading">VLAN Trunk</h3>



<ul class="wp-block-list">
<li>Multiple tagged networks carried over one physical/bridge link</li>



<li>Required for central isolation</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">3. Architecture Overview</h2>



<h3 class="wp-block-heading">3.1 Current State (Baseline / Transitional)</h3>



<p><strong>Goal:</strong> Extend connectivity quickly with zero trenching and minimal spend while avoiding technical debt.</p>



<ul class="wp-block-list">
<li>Core routing, DHCP, DNS handled by <strong>OPNsense</strong> at the house</li>



<li>Temporary or legacy switches/APs allowed <em>only</em> at the edge</li>



<li>10/100 gear permitted <strong>only</strong> for non‑critical devices</li>



<li>No permanent reliance on consumer mesh backhaul</li>
</ul>



<pre class="wp-block-code"><code>House/Core ──(existing LAN)── Temporary switch/AP ── Devices</code></pre>



<p>This state is acceptable <strong>only as a stopgap</strong>.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h3 class="wp-block-heading">3.2 Future State (Target / Locked‑In Design)</h3>



<p><strong>Goal:</strong> Treat every outbuilding as if it were connected by a short Ethernet cable, with full VLAN support and centralized security.</p>



<h4 class="wp-block-heading">Core / House</h4>



<ul class="wp-block-list">
<li>OPNsense router</li>



<li>VLANs + firewall rules</li>



<li>Central DHCP + DNS (Pi‑hole VIP)</li>
</ul>



<h4 class="wp-block-heading">Inter‑Building Backhaul</h4>



<ul class="wp-block-list">
<li><strong>Ubiquiti airMAX NanoStation M5 (or AC equivalent)</strong></li>



<li>Configured as <strong>transparent Layer‑2 bridge (WDS)</strong></li>



<li>One <strong>Point‑to‑Point (PtP)</strong> link per building (preferred)</li>
</ul>



<h4 class="wp-block-heading">Outbuilding Edge</h4>



<ul class="wp-block-list">
<li>1 GbE switch (<strong>managed preferred</strong>)</li>



<li>AP(s) in <strong>AP / bridge mode</strong></li>



<li>No routing, no NAT, no DHCP</li>
</ul>



<pre class="wp-block-code"><code>House/Core ── NanoStation ))))) NanoStation ── GbE Switch ── AP / Cameras / PCs</code></pre>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">4. VLAN &amp; Isolation Model (Authoritative)</h2>



<h3 class="wp-block-heading">VLANs Live Here</h3>



<ul class="wp-block-list">
<li><strong>OPNsense ONLY</strong></li>
</ul>



<h3 class="wp-block-heading">VLAN Table (Example / Reference)</h3>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th class="has-text-align-right" data-align="right">VLAN ID</th><th>Name</th><th>Purpose</th><th class="has-text-align-center" data-align="center">DHCP</th><th class="has-text-align-center" data-align="center">Internet</th><th class="has-text-align-center" data-align="center">LAN Access</th></tr></thead><tbody><tr><td class="has-text-align-right" data-align="right">10</td><td>LAN</td><td>Trusted clients, admins, servers</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">Yes</td></tr><tr><td class="has-text-align-right" data-align="right">20</td><td>IoT</td><td>Cameras, hubs, appliances</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">No</td></tr><tr><td class="has-text-align-right" data-align="right">30</td><td>Guest</td><td>Guests, contractors</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">No</td></tr><tr><td class="has-text-align-right" data-align="right">40</td><td>Shop</td><td>Work PCs, tools, shop equipment</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">Yes</td><td class="has-text-align-center" data-align="center">Limited</td></tr></tbody></table></figure>



<h3 class="wp-block-heading">Firewall Rule Matrix (Simplified)</h3>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Source VLAN</th><th>Destination</th><th>Action</th><th>Notes</th></tr></thead><tbody><tr><td>LAN (10)</td><td>IoT (20)</td><td>Allow</td><td>Management access</td></tr><tr><td>IoT (20)</td><td>LAN (10)</td><td>Deny</td><td>Isolation</td></tr><tr><td>Guest (30)</td><td>LAN (10)</td><td>Deny</td><td>Isolation</td></tr><tr><td>Any</td><td>DNS (Pi‑hole VIP)</td><td>Allow</td><td>Central DNS</td></tr><tr><td>Any</td><td>Internet</td><td>Allow</td><td>As policy dictates</td></tr></tbody></table></figure>



<h3 class="wp-block-heading">Bridge Behavior</h3>



<ul class="wp-block-list">
<li>NanoStations pass <strong>tagged VLAN frames transparently</strong></li>



<li>Treat every PtP link as an Ethernet cable</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">5. Wi‑Fi Design (Roaming, Not Mesh)</h2>



<h3 class="wp-block-heading">Configuration Rules</h3>



<ul class="wp-block-list">
<li>Same SSID across APs (per VLAN if needed)</li>



<li>Same security + passphrase</li>



<li>Different channels (avoid overlap)</li>
</ul>



<h3 class="wp-block-heading">Optional Enhancements</h3>



<ul class="wp-block-list">
<li>Enable 802.11k / 802.11v</li>



<li>Use 802.11r <strong>only if clients tolerate it</strong></li>
</ul>



<h3 class="wp-block-heading">Result</h3>



<ul class="wp-block-list">
<li>Seamless roaming across house + shop + sheds</li>



<li>No throughput halving</li>



<li>No wireless relay hops</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">6. Hardware Recommendations (By Tier)</h2>



<h3 class="wp-block-heading">Backhaul (Primary Recommendation)</h3>



<ul class="wp-block-list">
<li><strong>Ubiquiti airMAX NanoStation M5</strong></li>



<li><strong>Ubiquiti LiteBeam 5AC / NanoBeam AC</strong> (more headroom)</li>
</ul>



<h3 class="wp-block-heading">Avoid</h3>



<ul class="wp-block-list">
<li>No‑name Amazon bridge kits (inflated specs)</li>



<li>Consumer mesh systems for inter‑building links</li>
</ul>



<h3 class="wp-block-heading">Extreme Upgrade (Only if Needed)</h3>



<ul class="wp-block-list">
<li>60 GHz bridges (airMAX / UniFi Building Bridge)</li>



<li>Use <strong>only</strong> if sustained >500 Mbps is required</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">7. Wired vs Wireless: When to Use Each</h2>



<h3 class="wp-block-heading">Wireless Bridge (Default)</h3>



<p>Use when:</p>



<ul class="wp-block-list">
<li>Buildings have line of sight</li>



<li>Separate power systems exist</li>



<li>Lightning risk is a concern</li>



<li>You want zero trenching</li>
</ul>



<h3 class="wp-block-heading">Trench Fiber (Rare)</h3>



<p>Only when:</p>



<ul class="wp-block-list">
<li>You are already trenching for utilities</li>



<li>You require multi‑gig sustained throughput</li>



<li>You want 20‑year infrastructure</li>
</ul>



<p><strong>Never trench copper Ethernet. Ever.</strong></p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">8. Legacy 10/100 Gear Policy</h2>



<h3 class="wp-block-heading">Allowed Uses</h3>



<ul class="wp-block-list">
<li>Temporary bootstrap</li>



<li>Cameras</li>



<li>Controllers</li>



<li>Non‑critical IoT</li>
</ul>



<h3 class="wp-block-heading">Forbidden Uses</h3>



<ul class="wp-block-list">
<li>Backhaul</li>



<li>NAS access</li>



<li>Proxmox nodes</li>



<li>Permanent installs</li>
</ul>



<h3 class="wp-block-heading">Rule</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p>If it matters later, start at gig now.</p>
</blockquote>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">9. Bill of Materials (BOM) – Per Outbuilding</h2>



<h3 class="wp-block-heading">Required (Per Building)</h3>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Item</th><th class="has-text-align-right" data-align="right">Qty</th><th>Notes</th></tr></thead><tbody><tr><td>Ubiquiti airMAX NanoStation M5</td><td class="has-text-align-right" data-align="right">2</td><td>One at house, one at outbuilding</td></tr><tr><td>PoE Injectors (included)</td><td class="has-text-align-right" data-align="right">2</td><td>Indoor power</td></tr><tr><td>Outdoor‑rated Cat6 patch cables</td><td class="has-text-align-right" data-align="right">2</td><td>Short runs only</td></tr><tr><td>Gigabit Ethernet switch</td><td class="has-text-align-right" data-align="right">1</td><td>Managed preferred</td></tr><tr><td>Wi‑Fi Access Point</td><td class="has-text-align-right" data-align="right">1–2</td><td>AP/bridge mode</td></tr><tr><td>Mounting hardware</td><td class="has-text-align-right" data-align="right">1 set</td><td>Eave / pole / fascia</td></tr></tbody></table></figure>



<h3 class="wp-block-heading">Optional / Nice‑to‑Have</h3>



<ul class="wp-block-list">
<li>Managed switch (VLAN breakout)</li>



<li>UPS (small) for bridge + switch</li>



<li>Surge protection (indoor side)</li>
</ul>



<p><strong>Estimated cost per outbuilding:</strong> ~$200–250</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">10. Validation Checklist</h2>



<ul class="wp-block-list">
<li>Bridge latency &lt; 3 ms</li>



<li>Stable RSSI (~‑50 to ‑60 dBm)</li>



<li>Shop speed ≈ house speed</li>



<li>VLAN isolation confirmed</li>



<li>No double NAT</li>



<li>No buried copper</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">11. Rollback &amp; Upgrade Paths</h2>



<h3 class="wp-block-heading">Speed Upgrade</h3>



<ul class="wp-block-list">
<li>Replace NanoStation with <strong>NanoBeam AC / LiteBeam 5AC</strong></li>
</ul>



<h3 class="wp-block-heading">Bandwidth Upgrade</h3>



<ul class="wp-block-list">
<li>Replace 5 GHz PtP with <strong>60 GHz bridge</strong> (short range, clear LOS)</li>
</ul>



<h3 class="wp-block-heading">Ultimate Upgrade</h3>



<ul class="wp-block-list">
<li>Trench <strong>fiber only</strong> (leave bridges in place until fiber is proven)</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">12. Site‑Specific Topology Diagram (House → Shop → Sheds)</h2>



<h3 class="wp-block-heading">Speed Upgrade</h3>



<ul class="wp-block-list">
<li>Replace NanoStation with NanoBeam / LiteBeam</li>
</ul>



<h3 class="wp-block-heading">Bandwidth Upgrade</h3>



<ul class="wp-block-list">
<li>Replace 5 GHz with 60 GHz bridge</li>
</ul>



<h3 class="wp-block-heading">Ultimate Upgrade</h3>



<ul class="wp-block-list">
<li>Trench <strong>fiber</strong> only (leave bridges intact until proven)</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">11. Site-Specific Topology Diagram (House → Shop → Sheds)</h2>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>Topology goal</strong>: Treat every outbuilding as if it were connected by a short Ethernet cable, while keeping routing, security, and policy centralized at the house (OPNsense).</p>
</blockquote>



<pre class="wp-block-code"><code>                              ┌─────────────────────────┐
                              │        INTERNET         │
                              └─────────────┬───────────┘
                                            │
                                   ISP Modem / ONT
                                            │
                              ┌─────────────▼───────────┐
                              │        OPNsense          │
                              │  VLANs + Firewall + DNS │
                              │  (Pi-hole VIP .7)       │
                              └─────────────┬───────────┘
                                            │
                                   Core LAN / Trunk
                                            │
                         ┌──────────────────┴──────────────────┐
                         │                                     │
                NanoStation (PtP)                       NanoStation (PtP)
                  House Side                              House Side
                         ))))))))))))))))))))))))))))))))))))))))))
                         ))))))))))))))))))))))))))))))))))))))))))
                NanoStation (PtP)                       NanoStation (PtP)
                 Shop Side                               Shed Side
                         │                                     │
                 ┌───────▼────────┐                   ┌───────▼────────┐
                 │  GbE Switch     │                   │  GbE Switch     │
                 │ (Managed pref) │                   │ (Managed pref) │
                 └───────┬────────┘                   └───────┬────────┘
                         │                                     │
               ┌─────────┴─────────┐               ┌─────────┴─────────┐
               │                   │               │                   │
            AP (SSID/VLANs)     Cameras          AP (SSID/VLANs)     Cameras
               │                                   │
         PCs / Tools / IoT                  IoT / Sensors / Tools</code></pre>



<h3 class="wp-block-heading">Key Notes</h3>



<ul class="wp-block-list">
<li><strong>Each PtP link is independent</strong> (preferred): failure or congestion in one outbuilding does not affect others.</li>



<li><strong>NanoStations act as Layer-2 bridges</strong>: VLAN tags pass transparently.</li>



<li><strong>Routing, DHCP, DNS, and isolation live ONLY at OPNsense</strong>.</li>



<li><strong>Outbuildings never route or NAT by default</strong>.</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">12. Topology Variants (When Needed)</h2>



<h3 class="wp-block-heading">Hub-and-Spoke (Acceptable)</h3>



<p>Use only if buildings are close and radio count must be minimized.</p>



<pre class="wp-block-code"><code>House (Hub)
   ├── PtP → Shop
   ├── PtP → Shed A
   └── PtP → Shed B</code></pre>



<p>Tradeoff: shared airtime at the hub.</p>



<h3 class="wp-block-heading">Daisy-Chain / Relay (Avoid)</h3>



<pre class="wp-block-code"><code>House → Shop → Shed</code></pre>



<ul class="wp-block-list">
<li>Increases latency</li>



<li>Reduces throughput</li>



<li>Harder to troubleshoot</li>
</ul>



<p>Only use if <strong>line-of-sight makes direct links impossible</strong>.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">13. Final Guidance (Lock-In)</h2>



<p>(Lock‑In)</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>Wireless bridges are infrastructure, not a compromise.</strong><br><strong>Roaming is solved with APs, not mesh backhaul.</strong><br><strong>Isolation belongs at OPNsense, not at the edge.</strong></p>
</blockquote>



<p>This design eliminates technical debt, trenching, lightning risk, and legacy hardware — while remaining fully upgradeable.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p><em>Document intended for Obsidian vault and WordPress publishing. Headings are stable anchors.</em></p>
</div>
</div>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.tatomenterprises.com/networking/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
