<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on heezy.blog</title><link>https://heezy.blog/tags/networking/</link><description>Recent content in Networking on heezy.blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://heezy.blog/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>Pi-hole on Kubernetes with MetalLB and a Ruckus SSID</title><link>https://heezy.blog/posts/pihole-metallb-ruckus/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/pihole-metallb-ruckus/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;🚧 UNDER CONSTRUCTION 🚧&lt;/strong&gt;
Switch and Ruckus configuration pending. Screenshots to be added.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Pi-hole was already running on the cluster. It worked fine from inside the cluster and via NodePort on weird high ports. The problem was that no actual client device could use it as a DNS server, because DNS clients expect port 53 and NodePort gives you 30054.&lt;/p&gt;
&lt;p&gt;What started as &amp;ldquo;just give Pi-hole a real IP&amp;rdquo; turned into a new VLAN, a new DHCP server, firewall policy changes, switch configuration, and a Ruckus SSID. The usual homelab scope creep.&lt;/p&gt;</description></item><item><title>Split DNS, MetalLB, and the dnsmasq Debugging Saga</title><link>https://heezy.blog/posts/internal-dns-rollout-dnsmasq-metallb/</link><pubDate>Sun, 12 Apr 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/internal-dns-rollout-dnsmasq-metallb/</guid><description>&lt;p&gt;This is the story of building split-horizon DNS for a homelab with four VLANs, a FortiGate firewall, a 5-node MicroK8s cluster, and a Cloudflare tunnel. Then spending hours debugging why dnsmasq wouldn&amp;rsquo;t answer queries despite the port being open, the firewall allowing traffic, and the container running fine. The entire implementation and debugging session was driven through MCP tooling.&lt;/p&gt;</description></item><item><title>Networking the Heezy: VLANs, Firewall Zones, and How Traffic Moves</title><link>https://heezy.blog/posts/networking-vlans-and-firewall/</link><pubDate>Thu, 12 Mar 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/networking-vlans-and-firewall/</guid><description>&lt;p&gt;The network is the foundation of everything in the lab. Four VLANs, a FortiGate doing all the routing, a Cisco 3560 doing the switching, and a set of rules about what can talk to what. This post covers how it&amp;rsquo;s all wired together, how DNS works across zones, and how remote access gets in without exposing anything to the internet.&lt;/p&gt;</description></item><item><title>The Heezy: A Homelab That Got Out of Hand</title><link>https://heezy.blog/posts/the-heezy-architecture/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/the-heezy-architecture/</guid><description>&lt;h2 id="contents"&gt;Contents&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#what-even-is-a-heezy"&gt;What Even Is a Heezy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-network"&gt;The Network&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-kubernetes-cluster"&gt;The Kubernetes Cluster&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#what-runs-on-the-cluster"&gt;What Runs on the Cluster&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-dmz"&gt;The DMZ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#monitoring"&gt;Monitoring&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#dns"&gt;DNS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#infrastructure-as-code"&gt;Infrastructure as Code&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-aws-bootstrap-cdk-first-everything-else-after"&gt;The AWS Bootstrap: CDK First, Everything Else After&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#secrets"&gt;Secrets&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#what-id-do-differently"&gt;What I&amp;rsquo;d Do Differently&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-name"&gt;The Name&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-even-is-a-heezy"&gt;What Even Is a Heezy&lt;/h2&gt;
&lt;p&gt;If you grew up in the early 2000s, you probably remember when Snoop Dogg had everyone adding &amp;ldquo;-izzle&amp;rdquo; to everything. &amp;ldquo;For sheezy&amp;rdquo; was peak vocabulary for a 12-year-old who spent too much time on Counter-Strike and not enough time on homework. &amp;ldquo;Heezy&amp;rdquo; rhymes with &amp;ldquo;easy,&amp;rdquo; which is what I told myself this project would be. It was not easy. But the name stuck, and now my entire infrastructure is named after slang that peaked in 2003. No regrets.&lt;/p&gt;</description></item><item><title>Tailscale, FortiGate CVEs, and Remote Access That Doesn't Suck</title><link>https://heezy.blog/posts/tailscale-remote-access/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/tailscale-remote-access/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;🚧 UNDER CONSTRUCTION 🚧&lt;/strong&gt;
This post is a work in progress.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id="the-problem"&gt;The Problem&lt;/h2&gt;
&lt;p&gt;I need to reach into my home network from anywhere. SSH into nodes, check Grafana dashboards, access services that aren&amp;rsquo;t exposed through Cloudflare. The traditional answer is a VPN, and I have a FortiGate sitting right there with IPSec and SSL VPN capabilities built in.&lt;/p&gt;</description></item><item><title>Cellular Backup Internet</title><link>https://heezy.blog/posts/cellular-backup/</link><pubDate>Sat, 19 Nov 2022 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/cellular-backup/</guid><description>&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;🚧 UNDER CONSTRUCTION 🚧&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;img src="images/cellular-backup-1.jpg" alt="Cellular backup setup 1" style="max-width: 480px; width: 100%;" /&gt;
&lt;img src="images/cellular-backup-2.jpg" alt="Cellular backup setup 2" style="max-width: 480px; width: 100%;" /&gt;
&lt;img src="images/cellular-backup-3.jpg" alt="Cellular backup setup 3" style="max-width: 480px; width: 100%;" /&gt;</description></item></channel></rss>