Whatever the reason it must be removed urgently. But it is still there...
so what this means is to hold of with upgrade intil json problem is solved?
The problem is solved, just wait until the fix/jsonfilter update is available for your arch.
3 Likes
So would the correct way to upgrade be with owut or apk ?
You can manually install the packages, but they will be written to your available storage. If you want the updates to be in the ROM area, then you could just use LUCI > Attended SysUpgrade to build and re-flash the same OpenWRT firmware version with the current updated packages.
1 Like
jsonfilter-2026.03.16~b9034210-r1 is out and solves the issue
1 Like
On my side, I see:
root@AirGate:~# apk list | grep jsonfilter
jsonfilter-2026.03.16~b9034210-r1 aarch64_cortex-a53 {feeds/base/utils/jsonfilter} (ISC) [installed]
root@AirGate:~# apk list | grep banip
banip-1.8.1-r1 noarch {feeds/packages/feeds/packages/net/banip} (GPL-3.0-or-later) [installed]
... but I still see the garbled timestamps in the banip luci interface:
[12/01/58188-20:28:30] [ 1434.234990] banIP/inbound/drop/cinsscore.v4: IN=wan OUT= MAC=e8:9f:80:###################### SRC=85.217.149.55 DST=131.93.##### LEN=52 TOS=0x00 PREC=0x00 TTL=50 ID=16340 PROTO=TCP SPT=54329 DPT=4952 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0x1
Is the issue that you are referencing just the timestamps, or did I miss something - maybe another issue? That version did not solve it for me...
That cosmetic bug is unrelated to jsonfilter and already fixed in my dev version. Please stay tuned for the next banIP frontend update.
2 Likes
Team,
I’m in trouble with my banipLog after upgrade 25.12.1:
SystemLog shows:
[21.03.2026, 15:46:39 MEZ] kern.warn: [32022.059498] banIP/pre-ct/drop: IN=pppoe-WAN_GF OUT= MAC= SRC=80.66.66.54 DST=87.184.70.190 LEN=44 TOS=0x00 PREC=0x00 TTL=250 ID=52557 PROTO=TCP SPT=57155 DPT=9122 WINDOW=1200 RES=0x00 RST URGP=0
banipLog shows:
[16.02.58189-18:35:16] [32022.059498] banIP/pre-ct/drop: IN=pppoe-WAN_GF OUT= MAC= SRC=80.66.66.54 DST=87.184.70.190 LEN=44 TOS=0x00 PREC=0x00 TTL=250 ID=52557 PROTO=TCP SPT=57155 DPT=9122 WINDOW=1200 RES=0x00 RST URGP=0
Take a look at the timestamp…
There are much more wrong entries in banipLog…
Config:
config banip 'global'
option ban_enabled '1'
option ban_debug '1'
option ban_autodetect '0'
option ban_fetchretry '5'
option ban_nicelimit '-10'
option ban_filelimit '1024'
option ban_deduplicate '1'
option ban_nftpriority '-100'
option ban_icmplimit '25'
option ban_synlimit '10'
option ban_udplimit '100'
option ban_nftpolicy 'performance'
option ban_nftretry '5'
option ban_blockpolicy 'drop'
option ban_nftloglevel 'warn'
option ban_logprerouting '1'
option ban_loginbound '1'
option ban_logoutbound '1'
option ban_loglimit '100'
list ban_region 'AFRINIC'
list ban_region 'APNIC'
list ban_region 'ARIN'
list ban_region 'LACNIC'
list ban_region 'RIPE'
option ban_autoallowlist '1'
option ban_autoallowuplink 'subnet'
option ban_autoblocklist '1'
option ban_allowlistonly '0'
option ban_fetchcmd 'uclient-fetch'
option ban_protov4 '1'
list ban_logterm 'Exit before auth from'
list ban_logterm 'luci: failed login'
list ban_logterm 'AdGuardHome.*\[error\].*/control/login: from ip'
option ban_nftcount '1'
option ban_map '1'
option ban_autoblocksubnet '1'
list ban_dev 'lan2'
list ban_dev 'pppoe-WAN_GF'
list ban_ifv4 'WAN_GF'
list ban_ifv4 'WAN2_5G'
option ban_triggerdelay '150'
option ban_basedir '/mnt/sda1/banIP'
option ban_backupdir '/mnt/sda1/banIP-backup'
option ban_reportdir '/mnt/sda1/banIP-report'
option ban_errordir '/mnt/sda1/banIP-error'
...
Any idea??
Neuro
Have you read the last two posts in this thread (above yours)? 
1 Like
…no…
…
sorry
1 Like
…Oh, I need some makeup...
2 Likes
@davygravy @neurotransmitter The reported issue has been fixed with this update (backend plus LuCI):
3 Likes
Merci beaucoup @dibdot, it looks like it will take it a short while until it populates the feeds... I'll check to see that upgrading banip and luci-app-banip won't break anything else in 25.10.1 before jumping in ...
Again, thanks.
Works as expected!!
Thx Dirk
Neuro
2 Likes
Thanks.
I'm not streaming or using VoIP.
I just updated from 24.10.5 to 24.10.6 and it returned to "normal" levels:
1 Like
I need a little help. New to banIP, and I'm unsure if I need to set anything for "Startup Trigger Interface" or to just leave it empty.
Home router, using wan and wan6. wan is DHCP, wan6 is DHCPv6.
Yep, it's recommended. For details see the readme, just use your wan interface (not wan6).
1 Like
Perfect, thank you.
I promise I did read the readme before posting, and was trying to understand what it meant:
It's also recommended to configure a 'Reload Trigger Interface' to depend on your WAN ifup events during boot or restart of your router.
Perhaps it’s just the way it was said, as I didn’t realise ‘WAN ifup events’ was describing one thing.
Good to know now, in simpler terms, it’s recommended to set the ‘Reload Trigger Interface’ to your wan interface (not wan6), for banIP to look at the WAN’s ‘ifup’ events during boot or restart of your router.
1 Like
FYI, a brand new banIP release in master & 25.12 branch - thanks @Coralesoft for co-authoring!
Have fun!
Dirk
10 Likes