<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>firewall – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/firewall/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Thu, 01 Oct 2026 13:51:27 +0200</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/firewall/index.xml" rel="self" type="application/rss+xml"/><item><title>Germany Only: Geo-Fencing SSH with nftables and Ansible (and What My Logs Said About Bots and Readers)</title><link>https://www.apt-upgrade.me/2026/10/01/geo-fencing-ssh-with-nftables-and-ansible/</link><pubDate>Thu, 01 Oct 2026 13:51:27 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/01/geo-fencing-ssh-with-nftables-and-ansible/</guid><description>&lt;p&gt;After moving two &lt;a href="https://nextcloud.com/"&gt;Nextcloud&lt;/a&gt; instances to new servers this week, I asked a simple question: &lt;em&gt;do my three servers - this blog and the two Nextclouds - attract different kinds of attackers?&lt;/em&gt; The answer was mostly &amp;ldquo;no, it&amp;rsquo;s the same background noise everywhere&amp;rdquo;. Except for one line that bugged me: &lt;strong&gt;SSH&lt;/strong&gt;. It runs on a non-standard port, accepts keys only, and fail2ban watches it. And yet the blog alone logged around &lt;strong&gt;16 connection attempts per hour&lt;/strong&gt; to the SSH daemon, from all over the world.&lt;/p&gt;</description></item><item><title>Adventures in IPv6, Firewalls &amp; the “Oops-I-Forgot” Department 🚀</title><link>https://www.apt-upgrade.me/2025/08/25/adventures-in-ipv6-firewalls-the-oops-i-forgot-department-%F0%9F%9A%80/</link><pubDate>Mon, 25 Aug 2025 16:17:34 +0200</pubDate><guid>https://www.apt-upgrade.me/2025/08/25/adventures-in-ipv6-firewalls-the-oops-i-forgot-department-%F0%9F%9A%80/</guid><description>&lt;p&gt;So, a few days ago I thought: &lt;em&gt;&amp;ldquo;Hey, let’s be cool, ditch Apache, and hop onto the Nginx hype train because... HTTP/3, baby!&amp;rdquo;&lt;/em&gt; 🎉&lt;/p&gt;&#10;&lt;p&gt;Fast-forward to today, when I decided to show off and run one of those fancy SSL / web server grading tools. You know, the nerd’s equivalent of flexing in front of a mirror. 😎&lt;/p&gt;&#10;&lt;p&gt;...and then BAM 💥: my blog was &lt;strong&gt;completely invisible over IPv6&lt;/strong&gt;. Like, gone. As if Thanos snapped half the packets away. 🫰&lt;/p&gt;</description></item><item><title>How I Managed to Wreck My Firewall Appliance With a Debian 13 Upgrade</title><link>https://www.apt-upgrade.me/2025/08/20/how-i-managed-to-wreck-my-firewall-appliance-with-a-debian-13-upgrade/</link><pubDate>Wed, 20 Aug 2025 21:25:15 +0200</pubDate><guid>https://www.apt-upgrade.me/2025/08/20/how-i-managed-to-wreck-my-firewall-appliance-with-a-debian-13-upgrade/</guid><description>&lt;p&gt;Yesterday I proudly hit publish on a post about my &lt;em&gt;super smooth&lt;/em&gt; upgrade to Debian 13… feeling like a proper Linux wizard. 🧙‍♂️&lt;/p&gt;&#10;&lt;p&gt;A few hours later, reality slapped me in the face: I managed to completely nuke my poor firewall appliance while trying to upgrade it as well. RIP.&lt;/p&gt;&#10;&lt;p&gt;Technically, it still booted and looked fine – no scary red error messages. But this box was the one running &lt;strong&gt;Traefik&lt;/strong&gt;, the gatekeeper to my self-hosted blog. And suddenly… things got weird.&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>