<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Home Lab on Bill's Blog</title><link>https://billalrehmani.pages.dev/series/home-lab/</link><description>Recent content in Home Lab on Bill's Blog</description><image><title>Bill's Blog</title><url>https://billalrehmani.pages.dev/images/eft-bg.jpg</url><link>https://billalrehmani.pages.dev/images/eft-bg.jpg</link></image><generator>Hugo</generator><language>en-AU</language><lastBuildDate>Sat, 11 Jul 2026 22:30:00 +1000</lastBuildDate><atom:link href="https://billalrehmani.pages.dev/series/home-lab/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosted WireGuard Through a Nested Firewall — and the Four-Layer Debug to Make It Work</title><link>https://billalrehmani.pages.dev/posts/wireguard-pfsense-nested-firewall/</link><pubDate>Sat, 11 Jul 2026 22:30:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/wireguard-pfsense-nested-firewall/</guid><description>I already run Tailscale, but I wanted to build a VPN into my lab from scratch — raw WireGuard on pfSense, reaching it from my phone on mobile data. Getting the tunnel up was the easy part. Then came four separate silent failures, each producing the identical &amp;#39;won&amp;#39;t load&amp;#39; symptom for a completely different reason, at a completely different layer.</description></item><item><title>Syncing Claude Code Across Devices with a Custom MCP Hub over Tailscale</title><link>https://billalrehmani.pages.dev/posts/claude-code-mcp-hub-tailscale/</link><pubDate>Tue, 07 Jul 2026 16:55:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/claude-code-mcp-hub-tailscale/</guid><description>Linking two independent Claude Code agents — a home-lab VM and a roaming laptop — through a custom MCP server over a Tailscale mesh, so the laptop can push notes to a central hub from any network without opening a single inbound port.</description></item><item><title>Building a Prometheus and Grafana Observability Stack for My Home Lab</title><link>https://billalrehmani.pages.dev/posts/prometheus-grafana-observability-stack/</link><pubDate>Mon, 06 Jul 2026 21:26:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/prometheus-grafana-observability-stack/</guid><description>The dashboard layer under the LaMetric glance: Prometheus scraping my Debian VM and pfSense firewall, Grafana turning it into real graphs with history — all on one isolated VM, bound to localhost, reusing the SNMP work from the last project.</description></item><item><title>Implementing LaMetric TIME to Network Part 2</title><link>https://billalrehmani.pages.dev/posts/implementing-lametric-time-to-network-part-2/</link><pubDate>Mon, 06 Jul 2026 19:20:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/implementing-lametric-time-to-network-part-2/</guid><description>Adding real WAN throughput to the LaMetric display by polling pfSense over SNMP — turning &amp;#39;a VM&amp;#39;s stats&amp;#39; into &amp;#39;my network&amp;#39;s stats&amp;#39;, with the counter that proves it works.</description></item><item><title>Implementing LaMetric TIME to Network</title><link>https://billalrehmani.pages.dev/posts/implementing-lametric-time-to-network/</link><pubDate>Sun, 05 Jul 2026 21:30:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/implementing-lametric-time-to-network/</guid><description>Piping live home-lab stats to a LaMetric Time over MQTT — bridging two deliberately-isolated networks through a cloud broker without opening a single inbound port.</description></item><item><title>Debugging a Dead VMware NAT and Hardening My pfSense Containment Lab</title><link>https://billalrehmani.pages.dev/posts/pfsense-lab-recovery-and-hardening/</link><pubDate>Thu, 02 Jul 2026 21:46:00 +1000</pubDate><guid>https://billalrehmani.pages.dev/posts/pfsense-lab-recovery-and-hardening/</guid><description>A Windows update silently re-enabled the hypervisor and killed my VMware lab&amp;#39;s networking. The diagnosis, the fix, and the pfSense rebuild — bridged WAN plus egress rules — that came out of it.</description></item></channel></rss>