<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Home Network Build on The Home Lab</title><link>https://adamazl.github.io/homelab/series/home-network-build/</link><description>Recent content in Home Network Build on The Home Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Mar 2026 00:37:20 +1300</lastBuildDate><atom:link href="https://adamazl.github.io/homelab/series/home-network-build/index.xml" rel="self" type="application/rss+xml"/><item><title>Automated Backups with Proxmox Backup Server</title><link>https://adamazl.github.io/homelab/posts/proxmox-backup-server/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/proxmox-backup-server/</guid><description>&lt;h2 id="the-problem-with-ad-hoc-backups"&gt;The Problem with Ad-hoc Backups&lt;/h2&gt;
&lt;p&gt;Proxmox VE has built-in backup functionality — you can snapshot a VM to a directory or NFS share on a schedule. But it stores full backups each time, space grows fast, and restoring requires the whole archive. Proxmox Backup Server (PBS) solves all three problems.&lt;/p&gt;
&lt;p&gt;PBS is a dedicated backup server that:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Stores backups with &lt;strong&gt;client-side deduplication and compression&lt;/strong&gt; (typically 50–80% space savings)&lt;/li&gt;
&lt;li&gt;Does &lt;strong&gt;incremental backups&lt;/strong&gt; — only changed chunks are uploaded&lt;/li&gt;
&lt;li&gt;Supports &lt;strong&gt;instant verification&lt;/strong&gt; by recalculating checksums&lt;/li&gt;
&lt;li&gt;Has &lt;strong&gt;pruning policies&lt;/strong&gt; — keep 7 daily, 4 weekly, 12 monthly backups automatically&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="architecture"&gt;Architecture&lt;/h2&gt;
&lt;p&gt;PBS is a separate Debian-based appliance. It does not run inside Proxmox VE. You have a few options:&lt;/p&gt;</description></item><item><title>Installing Proxmox VE</title><link>https://adamazl.github.io/homelab/posts/installing-proxmox/</link><pubDate>Sat, 13 Dec 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/installing-proxmox/</guid><description>&lt;h2 id="what-is-proxmox-ve"&gt;What is Proxmox VE?&lt;/h2&gt;
&lt;p&gt;Proxmox Virtual Environment (VE) is a free, open-source hypervisor built on Debian. It supports both
KVM-based virtual machines and LXC containers, and comes with a decent web UI out of the box — no
need to pay for a VMware licence.&lt;/p&gt;
&lt;h2 id="hardware"&gt;Hardware&lt;/h2&gt;
&lt;p&gt;For this build I&amp;rsquo;m running Proxmox on two nodes:&lt;/p&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Node&lt;/th&gt;
 &lt;th&gt;CPU&lt;/th&gt;
 &lt;th&gt;RAM&lt;/th&gt;
 &lt;th&gt;Storage&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;pve-01&lt;/td&gt;
 &lt;td&gt;Intel Core i5-12400&lt;/td&gt;
 &lt;td&gt;32 GB DDR4&lt;/td&gt;
 &lt;td&gt;500 GB NVMe (OS) + 2 TB SSD (VMs)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;pve-02&lt;/td&gt;
 &lt;td&gt;Intel Core i5-10400&lt;/td&gt;
 &lt;td&gt;16 GB DDR4&lt;/td&gt;
 &lt;td&gt;256 GB NVMe (OS) + 1 TB SSD (VMs)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="downloading-the-iso"&gt;Downloading the ISO&lt;/h2&gt;
&lt;p&gt;Head to the &lt;a href="https://www.proxmox.com/en/downloads"&gt;Proxmox downloads page&lt;/a&gt; and grab the latest
&lt;strong&gt;Proxmox VE ISO Installer&lt;/strong&gt;. At the time of writing that was 8.x.&lt;/p&gt;</description></item><item><title>Reverse Proxy and SSL with Nginx Proxy Manager</title><link>https://adamazl.github.io/homelab/posts/nginx-proxy-manager-ssl/</link><pubDate>Sat, 15 Nov 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/nginx-proxy-manager-ssl/</guid><description>&lt;h2 id="the-problem-nginx-proxy-manager-solves"&gt;The Problem Nginx Proxy Manager Solves&lt;/h2&gt;
&lt;p&gt;As your homelab grows, you accumulate services running on various IPs and ports: Proxmox on &lt;code&gt;:8006&lt;/code&gt;, Jellyfin on &lt;code&gt;:8096&lt;/code&gt;, Nextcloud on &lt;code&gt;:443&lt;/code&gt;, Home Assistant on &lt;code&gt;:8123&lt;/code&gt;. Remembering port numbers is tedious, but the bigger issue is HTTPS — browsers complain about self-signed certificates, and accessing services over plain HTTP on your LAN is a security risk.&lt;/p&gt;
&lt;p&gt;Nginx Proxy Manager (NPM) solves both problems. It&amp;rsquo;s a Docker container with a web UI that lets you:&lt;/p&gt;</description></item><item><title>Self-Hosted VPN with WireGuard</title><link>https://adamazl.github.io/homelab/posts/wireguard-vpn-server/</link><pubDate>Sat, 01 Nov 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/wireguard-vpn-server/</guid><description>&lt;h2 id="why-self-host-a-vpn"&gt;Why Self-Host a VPN?&lt;/h2&gt;
&lt;p&gt;A self-hosted VPN gives you a secure tunnel back into your home network when you&amp;rsquo;re away. Unlike commercial VPN services (which are for hiding traffic from your ISP), this is about remote access — connecting to your NAS, home automation, internal dashboards, or development environment from a coffee shop or hotel.&lt;/p&gt;
&lt;p&gt;WireGuard is the right choice today. It&amp;rsquo;s built into the Linux kernel, uses modern cryptography (ChaCha20, Curve25519), and has a drastically smaller codebase than OpenVPN (~4,000 lines vs ~400,000). Handshakes complete in milliseconds. Battery drain on mobile is noticeably lower.&lt;/p&gt;</description></item><item><title>Network-Wide Ad Blocking with Pi-hole</title><link>https://adamazl.github.io/homelab/posts/pihole-dns-ad-blocking/</link><pubDate>Sat, 18 Oct 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/pihole-dns-ad-blocking/</guid><description>&lt;h2 id="why-pi-hole"&gt;Why Pi-hole&lt;/h2&gt;
&lt;p&gt;Most ad blockers work at the browser level. Pi-hole works at the DNS level, which means it blocks ads for every device on your network — smart TVs, phones, game consoles, IoT devices — without installing anything on them. It works by acting as the DNS resolver for your LAN and returning &lt;code&gt;0.0.0.0&lt;/code&gt; for known ad and tracking domains instead of the real IP.&lt;/p&gt;
&lt;p&gt;The side effect is that you also get a full picture of every DNS query every device makes, which is genuinely eye-opening. You will quickly discover that your smart TV is phoning home every few minutes.&lt;/p&gt;</description></item><item><title>VLAN Segmentation: Isolating Your IoT Devices</title><link>https://adamazl.github.io/homelab/posts/vlan-segmentation-basics/</link><pubDate>Sat, 04 Oct 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/vlan-segmentation-basics/</guid><description>&lt;h2 id="why-segment-your-network"&gt;Why Segment Your Network?&lt;/h2&gt;
&lt;p&gt;The average home today has dozens of connected devices — smart bulbs, cameras, thermostats,
TVs. Most of these devices have poor security track records: default credentials, infrequent
firmware updates, and sometimes outright malicious firmware from vendors.&lt;/p&gt;
&lt;p&gt;Putting them on the same flat network as your laptop and NAS is an unnecessary risk. VLANs fix
this.&lt;/p&gt;
&lt;h2 id="what-is-a-vlan"&gt;What Is a VLAN?&lt;/h2&gt;
&lt;p&gt;A &lt;strong&gt;Virtual LAN (VLAN)&lt;/strong&gt; is a logical partition of a physical network. Devices on different VLANs
cannot communicate with each other unless you explicitly allow it through firewall rules — even if
they share the same physical switch.&lt;/p&gt;</description></item><item><title>Setting Up OPNsense as Your Home Firewall</title><link>https://adamazl.github.io/homelab/posts/opnsense-firewall-setup/</link><pubDate>Sat, 20 Sep 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/opnsense-firewall-setup/</guid><description>&lt;h2 id="why-replace-your-isp-router"&gt;Why Replace Your ISP Router?&lt;/h2&gt;
&lt;p&gt;ISP-provided routers are designed to be cheap and manageable by support staff, not to give you control. They have opaque firmware, rarely get security updates, and have none of the features a proper firewall offers: VLAN support, traffic shaping, IDS/IPS, meaningful logs, VPN server, DNS over TLS.&lt;/p&gt;
&lt;p&gt;OPNsense is a FreeBSD-based firewall/router that runs on commodity x86 hardware. It&amp;rsquo;s fully open-source (forked from pfSense in 2015), actively maintained, and has a polished web UI.&lt;/p&gt;</description></item><item><title>Hello, Homelab</title><link>https://adamazl.github.io/homelab/posts/hello-world/</link><pubDate>Sat, 06 Sep 2025 00:00:00 +0000</pubDate><guid>https://adamazl.github.io/homelab/posts/hello-world/</guid><description>&lt;h2 id="why-a-homelab"&gt;Why a Homelab?&lt;/h2&gt;
&lt;p&gt;Every homelab starts somewhere. Mine started with the frustration of paying for cloud services I
could run myself, and curiosity about what actually happens when packets travel across a network.&lt;/p&gt;
&lt;h2 id="current-goals"&gt;Current Goals&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Full network segmentation&lt;/strong&gt; — IoT devices on their own VLAN, completely isolated from the
trusted network&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Self-hosted DNS&lt;/strong&gt; with ad-blocking (Pi-hole / AdGuard Home)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A proper NAS&lt;/strong&gt; for media, backups, and general storage&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Monitoring stack&lt;/strong&gt; — Prometheus + Grafana so nothing breaks silently&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id="hardware-on-the-bench"&gt;Hardware on the Bench&lt;/h2&gt;
&lt;table&gt;
 &lt;thead&gt;
 &lt;tr&gt;
 &lt;th&gt;Device&lt;/th&gt;
 &lt;th&gt;Role&lt;/th&gt;
 &lt;/tr&gt;
 &lt;/thead&gt;
 &lt;tbody&gt;
 &lt;tr&gt;
 &lt;td&gt;TP-Link ER605&lt;/td&gt;
 &lt;td&gt;Router / gateway&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;TP-Link SG2008P&lt;/td&gt;
 &lt;td&gt;Managed PoE switch&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;TP-Link OC200&lt;/td&gt;
 &lt;td&gt;Omada hardware controller&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;TP-Link EAP245&lt;/td&gt;
 &lt;td&gt;Wi-Fi access point&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Proxmox VE × 2&lt;/td&gt;
 &lt;td&gt;Compute nodes (virtualisation)&lt;/td&gt;
 &lt;/tr&gt;
 &lt;tr&gt;
 &lt;td&gt;Proxmox PBS&lt;/td&gt;
 &lt;td&gt;Backup server&lt;/td&gt;
 &lt;/tr&gt;
 &lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="whats-coming-next"&gt;What&amp;rsquo;s Coming Next&lt;/h2&gt;
&lt;p&gt;The first series of posts will cover setting up a flat-to-segmented network from scratch —
starting with the router/firewall choice all the way through VLAN tagging and inter-VLAN routing
rules.&lt;/p&gt;</description></item></channel></rss>