<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>nftables – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/nftables/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Tue, 03 Nov 2026 19:58:05 +0100</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/nftables/index.xml" rel="self" type="application/rss+xml"/><item><title>HTTP/3 for My Blog and Nextcloud: One Switch, Two Hidden Brakes, and What the Measurements Show</title><link>https://www.apt-upgrade.me/2026/11/03/http-3-for-my-blog-and-nextcloud-one-switch-two-hidden-brakes-and-what-the-measurements-show/</link><pubDate>Tue, 03 Nov 2026 19:58:05 +0100</pubDate><guid>https://www.apt-upgrade.me/2026/11/03/http-3-for-my-blog-and-nextcloud-one-switch-two-hidden-brakes-and-what-the-measurements-show/</guid><description>&lt;p&gt;&lt;strong&gt;Update of November 6, 2026:&lt;/strong&gt; HTTP/3 is back on here, with nginx mainline and &lt;code&gt;quic_bpf&lt;/code&gt;. &lt;a href="https://www.apt-upgrade.me/2026/11/06/this-blog-now-runs-on-hugo-no-wordpress-no-kubernetes-and-stable-http-3/"&gt;The story is in the migration post.&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Update, November 4, 2026:&lt;/strong&gt; HTTP/3 is off again on all my servers. The reason is at the end of this post.&lt;/p&gt;&#10;&lt;p&gt;Many users of my Nextcloud instances are on their phones. That is exactly what HTTP/3 was built for: it runs over QUIC instead of TCP, needs one round trip less to set up a connection, copes better with packet loss, and can keep a connection alive when the phone switches from Wi-Fi to mobile data. My goal, however, was not “have HTTP/3” but: &lt;strong&gt;HTTP/3 only if it measurably helps&lt;/strong&gt; – more throughput or a more stable connection on a bad network.&lt;/p&gt;</description></item><item><title>The Ansible Tour, Part 5: IT Security – Firewall, SSH, fail2ban, Hardening, SELinux and Detection</title><link>https://www.apt-upgrade.me/2026/10/19/ansible-tour-part-5-security/</link><pubDate>Mon, 19 Oct 2026 20:34:02 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/19/ansible-tour-part-5-security/</guid><description>&lt;p&gt;&lt;em&gt;Part 5 of the &lt;a href="https://www.apt-upgrade.me/2026/10/14/ansible-tour-part-1-framework/"&gt;Ansible Tour&lt;/a&gt;. After the platform, the blog and Nextcloud, this part gathers all security roles in one place, across both stacks. The series describes release &lt;a href="https://github.com/aptupgrademe/www_k3s/tree/v3.3.0"&gt;v3.3.0&lt;/a&gt;, with later changes added as updates.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;Security here comes from layers: each one catches what the previous one missed. From the outside in, these are the firewall, the SSH login, the reaction to attacks in the logs (fail2ban), the hardening of the operating system, containment by SELinux, and detection by auditd, AIDE, rkhunter and ClamAV. The code is public, so an attacker can read it too. That is fine: the protection has to come from keys, layers and alerts, not from secrecy. Exact thresholds still stay vague here.&lt;/p&gt;</description></item><item><title>Defence in Depth: Nine Layers Between the Internet and My Servers</title><link>https://www.apt-upgrade.me/2026/10/13/defense-in-depth-nine-layers/</link><pubDate>Tue, 13 Oct 2026 21:30:35 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/13/defense-in-depth-nine-layers/</guid><description>&lt;p&gt;A blog and two Nextcloud servers for local organisations: nothing on them is worth a targeted attack, and that is exactly why they get attacked. Not by someone who wants &lt;em&gt;my&lt;/em&gt; data, but by scanners that try every IP address on the internet, every hour, with the same handful of tricks. Most of them give up after the first locked door. The question is what happens with the ones that don&amp;rsquo;t.&lt;/p&gt;</description></item><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>Moving a Nextcloud From Bare Metal to K3s: A Full Dress Rehearsal, and What It Cost Me in Commits</title><link>https://www.apt-upgrade.me/2026/09/11/moving-a-nextcloud-from-bare-metal-to-k3s-a-full-dress-rehearsal-and-what-it-cost-me-in-commits/</link><pubDate>Fri, 11 Sep 2026 15:43:03 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/11/moving-a-nextcloud-from-bare-metal-to-k3s-a-full-dress-rehearsal-and-what-it-cost-me-in-commits/</guid><description>&lt;p&gt;There&amp;rsquo;s a migration coming up that I&amp;rsquo;ve been circling for a while. A &lt;a href="https://nextcloud.com/"&gt;Nextcloud&lt;/a&gt; instance I administer still runs as a plain native installation — packages, webserver, PHP-FPM, all hand-managed on one box. It&amp;rsquo;s moving onto the &lt;a href="https://k3s.io/"&gt;K3s&lt;/a&gt; stack I&amp;rsquo;ve been building out in Ansible.&lt;/p&gt;&#10;&lt;p&gt;The honest reason for moving is that the native installation has aged. It still works, but it has accumulated a decade of small decisions nobody wrote down, and every update is an event rather than a routine. What I&amp;rsquo;m hoping to get from the K3s side is a duller kind of upgrade: the Nextcloud version and every container version pinned in the Ansible code, so an update becomes a changed tag in a file I can review, roll out the same way twice, and change back if it goes badly. The application and the data end up in genuinely separate places instead of interleaved in one tree. And &lt;a href="https://www.collaboraonline.com/"&gt;Collabora&lt;/a&gt; becomes a container of its own, talking to Nextcloud across a defined interface rather than being wired into the same installation — one less thing that breaks because two applications are sharing a runtime.&lt;/p&gt;</description></item><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></channel></rss>