<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Geo Filtering for nftables Brings Simplicity &amp; Flexibility to Geolocation Matching]]></title><description><![CDATA[<p dir="auto">This looks like a good upgrade, simplifying the blocklist use case.</p>
<p dir="auto"><a href="https://github.com/wirefalls/geo-nft" target="_blank" rel="noopener noreferrer nofollow ugc">https://github.com/wirefalls/geo-nft</a></p>
<p dir="auto">Geolocation for nftables is a Bash script to create nftables sets of country specific IP address ranges for use with firewall rulesets. The project provides a simple and flexible way to implement geolocation filtering with nftables.</p>
<ul>
<li>A script written for the widely used Bash shell.</li>
<li>Easy to set up, configure and customize with source code that's heavily commented.</li>
<li>Uses the free geolocation database from <a href="http://db-ip.com" target="_blank" rel="noopener noreferrer nofollow ugc">db-ip.com</a> (no EULA to accept).</li>
<li>Automatically generates country-specific nftables address range sets.</li>
<li>The script has a small memory footprint to run well on systems with limited RAM. A flexible configuration allows loading only minimum sets required if memory is tight.</li>
<li>User settings are stored in a standard configuration file rather than using command line arguments.</li>
<li>Packets can be geolocation filtered with a single nftables rule rather than two rules to mark and match packets like nftables map based solutions.</li>
<li>The script allows access to all of the valid country code address ranges in the database.</li>
<li>Automatically determines your installed version of nftables and recommends the correct "include" statements for your ruleset. The script also creates "include-all" files to allow you to include all geolocation sets with a single reference on older versions of nftables that don't support include wildcards.</li>
<li>The User Guide explains how to define all element definitions for geolocation sets in one file, eliminating the chance of having out-of-sync definitions in multiple files when flushing and refilling sets with new data.</li>
<li>Simplified directory structure to shorten "include" path names.<br />
The script creates ~500 IPv4 and IPv6 set files from the geolocation database in about 10 seconds on a low power quad-core 2200ge server with SSD storage.</li>
<li>Tested on Ubuntu Server, Fedora Server, and Raspberry Pi OS.</li>
</ul>
]]></description><link>https://forum.cloudron.io/topic/4461/geo-filtering-for-nftables-brings-simplicity-flexibility-to-geolocation-matching</link><generator>RSS for Node</generator><lastBuildDate>Fri, 17 Apr 2026 08:37:33 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/4461.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 14 Feb 2021 19:52:41 GMT</pubDate><ttl>60</ttl></channel></rss>