I just noticed that an IP address was still being blocked by the firewall although it wasn't contained in the blocklist anymore. # date Mon Mar 27 10:19:05 AM CEST 2023 # grep "Successfully updated BLOCKLIST_DE" /var/log/messages | tail -n1 Mar 27 10:15:18 atl-ipfire ipblocklist: <INFO> Successfully updated BLOCKLIST_DE blocklist. # ll /var/lib/ipblocklist/BLOCKLIST_DE.conf -rw-r--r-- 1 nobody nobody 663K Mar 27 10:15 /var/lib/ipblocklist/BLOCKLIST_DE.conf # grep 31.17.17.114 BLOCKLIST_DE.conf -> empty # ipset list BLOCKLIST_DE | grep 31.17.17.114 31.17.17.114 As a workaround, I disabled the blocklist use in the GUI and reloaded the firewall rules: # ipset list BLOCKLIST_DE | grep 31.17.17.114 ipset v7.15: The set with the given name does not exist Re-enabled blocklist: # ipset list BLOCKLIST_DE | grep 31.17.17.114 -> empty
@Stefan: Could you please have a look at this?
Hello Larsen, thanks for reporting this issue. I've sent a fix to the development mailing list which should be part of the next core update: https://patchwork.ipfire.org/project/ipfire/patch/20230328160542.132432-1-stefan.schantl@ipfire.org/ Please test and report back any remain issues. Thanks in advance, -Stefan
Thanks, will wait for the next core update and then test.
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=41d3d33dde1312d6e1556d3279d9c09d925b7452
https://blog.ipfire.org/post/ipfire-2-27-core-update-174-released
Just for the record: Works as expected now