packages/net/banip, branch master

banip: update 1.9.1-2

2026-10-17T13:10:28Z

- use the GNU regex matchers with gawk >= 5.4; gawk 5.4 switched its default regex engine to MinRX, this slows down the ip validation a lot (~35x slower) Signed-off-by: Dirk Brenken

banip: release 1.9.1-1

2026-10-15T15:06:18Z

- faster IPv4 validation in f_chkip (~2-3 × faster) - avoid full nft element fetches in the following functions: f_actual, f_down (reload & count) and f_search Signed-off-by: Dirk Brenken

banip: update 1.9.0-3

2026-09-27T19:00:39Z

* optimized the default download parameters for curl/wget * optimized the rdap range recognition * readme update Signed-off-by: Dirk Brenken

banip: update 1.9.0-2

2026-09-25T21:11:37Z

* use RDAP startAddress/endAddress as a single interval element (one nft call per lookup) * validate RDAP ranges, block nft command and log line injection * always restart the procd instance (unique nonce via env) * restart the log monitor if the log reader terminates (e.g. logd restart) * f_rmpid clears the pidfile before killing child processes * EXIT trap: route unexpected service exits through f_log "err" * readme update Signed-off-by: Dirk Brenken

banip: release 1.9.0

2026-09-19T17:50:03Z

- add the trigger interfaces to the runtime status - support url templates for the country and asn feeds; the readme contains an example of how to use an alternative MaxMind source as country feed - fix the fallback handling of the custom feed file - disable the curl url globbing - drop the unsupported 'w' nft expiry unit - LuCI: show the trigger interfaces, label the board model - LuCI: drop the unsupported 'w' expiry unit - LuCI: fix the custom feed file handling - readme update Signed-off-by: Dirk Brenken

banip: update 1.8.13-2

2026-09-10T18:02:03Z

- cap the GeoIP lookup at 15 batch requests per report run (ip-api.com rate limit) - reuse the map data for 60 seconds instead of querying the service again - log batch requests without geo data - limit the parallel background jobs exactly to `ban_cores (same as adblock) - LuCI: fix the GeoIP map description - readme update Signed-off-by: Dirk Brenken

banip: release 1.8.13

2026-09-08T15:58:17Z

- f_getup() collects the wan state in one pass and diffs the uplink against the local allowlist - new f_refresh() patches only the changed allowlist Set elements in a single atomic nft transaction, without touching the running instance - the procd trigger calls start refresh, start_service() picks the path, a manual start is unaffected - wan6 in ban_trigger is supported now - updatted the README and moved to the package root - LuCI: reworked the feed editor, get rid of custom css Signed-off-by: Dirk Brenken dev@brenken.org Signed-off-by: Dirk Brenken

banip: replace the CARTO basemap with local outlines

2026-08-27T09:06:55Z

CARTO now requires an API key for the raster basemaps at basemaps.cartocdn.com and watermarks every unauthenticated tile request, so the GeoIP map currently renders "API KEY REQUIRED" across the whole viewport. Therefore in luci-app-banip the basemap is now drawn from country outlines that ship with the package: Natural Earth 1:110m, public domain, all attributes stripped, simplified to 36 kB (~10 kB in the apk). readme changes in the base package only Signed-off-by: Dirk Brenken

banip: release 1.8.12-1

2026-08-21T19:47:17Z

* new option ban_monitorallowed: in allowlist-only mode the log monitor only honours the local allowlist, so attackers from an explicitly allowed segment can be banned (fixes openwrt/luci#8950) * adds the allowlist.local.v4/.v6 Sets, built from /etc/banip/banip.allowlist only, referenced by no rule * allowlist-only mode: skip only those external feeds whose direction is fully covered by the allowlist, instead of skipping all or none — split Sets included * f_lookup keeps the monitor Set in sync with resolved domains * f_restore: no more bogus per-proto restore attempts for the allowlist * f_report: batched and deduplicated geo lookups, correct Set names in the report * readme update Signed-off-by: Dirk Brenken

banip: fix cpu core calculation

2026-08-10T17:36:15Z

- only cap the cpu core count by available memory if it was auto-detected, a manually set 'ban_cores' is now authoritative and no longer lowered - readme update: clarify that the auto-cap does not apply to a manually set core count Signed-off-by: Dirk Brenken