<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>iptables – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/iptables/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Tue, 16 Jun 2026 21:22:32 +0200</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/iptables/index.xml" rel="self" type="application/rss+xml"/><item><title>🔒 GitHub Repo Update: Migrating from iptables to nftables — A Packet Filter Deep Dive</title><link>https://www.apt-upgrade.me/2026/06/16/%F0%9F%94%92-github-repo-update-nftables-iptables-a-packet-filter-deep-dive/</link><pubDate>Tue, 16 Jun 2026 21:22:32 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/06/16/%F0%9F%94%92-github-repo-update-nftables-iptables-a-packet-filter-deep-dive/</guid><description>&lt;p&gt;Quick repo update: the &lt;a href="https://github.com/aptupgrademe/www_k3s"&gt;www_k3s GitHub repo&lt;/a&gt; just got a significant firewall overhaul. The old setup used classic &lt;strong&gt;iptables&lt;/strong&gt; — which worked fine, but was starting to feel like driving a stick-shift with three pedals. Time to upgrade. The firewall is now fully rewritten in &lt;strong&gt;nftables&lt;/strong&gt;, the modern successor that&amp;rsquo;s been shipping as the Linux default since kernel 3.13. Here&amp;rsquo;s why that&amp;rsquo;s the right call, and a full walkthrough of what the new ruleset actually does. 🧵&lt;/p&gt;</description></item><item><title>One Year Later: I Finally Open-Sourced My Homelab K3s Stack</title><link>https://www.apt-upgrade.me/2026/05/17/one-year-later-i-finally-open-sourced-my-homelab-k3s-stack/</link><pubDate>Sun, 17 May 2026 19:34:12 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/05/17/one-year-later-i-finally-open-sourced-my-homelab-k3s-stack/</guid><description>&lt;p&gt;In a few of my recent posts I mentioned that I was trying to figure out how to publish my homelab automation code *without accidentally open-sourcing my entire infrastructure along with it* 😅&lt;/p&gt;&#10;&lt;p&gt;Turns out that&amp;rsquo;s a surprisingly non-trivial problem when your Ansible inventory looks like a cyberpunk treasure chest full of vaults, secrets and host-specific variables. 🔐🐉&lt;/p&gt;&#10;&lt;p&gt;After a bit of trial, error, caffeine and questionable life choices… I finally found a setup that works beautifully:&lt;/p&gt;</description></item><item><title>iptables, Protectli &amp; Paranoia: Basic Segmentation for the Home Lab</title><link>https://www.apt-upgrade.me/2025/05/21/basic_segmentattion_for_the_home_lab/</link><pubDate>Wed, 21 May 2025 08:44:43 +0200</pubDate><guid>https://www.apt-upgrade.me/2025/05/21/basic_segmentattion_for_the_home_lab/</guid><description>&lt;p&gt;At home, in my &lt;strong&gt;homelab&lt;/strong&gt;, I run multiple internal networks.&lt;br&gt;&#10;There’s one for trusted client devices, and another that’s less trusted — kind of like a &lt;strong&gt;DMZ&lt;/strong&gt;. The DMZ hosts those VMs that need to be reachable from the internet at the network level.&lt;/p&gt;&#10;&lt;p&gt;The main goal is to safeguard the internal network and limit blast radius in case a box inside the untrusted DMZ gets popped.&lt;/p&gt;&#10;&lt;p&gt;Both networks are connected directly to my servers.&lt;/p&gt;</description></item></channel></rss>