When unchecking it, the logs are well stopped after save and reload fireqall rules But the box remains checked on the page. write LOGGING=off in /var/ipfire/ipblocklist/settings could resolve the problem
See: https://community.ipfire.org/t/ipblocklist-cgi-log-dropped-packets-check-box-stay-checked/8871
Confirmed. Furthermore, once decativated, the default entry 'LOGGING=ON' is deleted and it can't be activated again. Even if the option is checked, 'LOGGING=ON' doesn't show up in the settings file. You have to add this line manually in the settings file and reload firewall rules, otherwise logging stays off.
Message when starting the firewall after unchecking "Log dropped packets" Setting up firewall Use of uninitialized value $blocklistsettings{"LOGGING"} in string eq at /usr/lib/firewall/rules.pl line 764. Use of uninitialized value $blocklistsettings{"LOGGING"} in string eq at /usr/lib/firewall/rules.pl line 764. Use of uninitialized value $blocklistsettings{"LOGGING"} in string eq at /usr/lib/firewall/rules.pl line 764. Use of uninitialized value $blocklistsettings{"LOGGING"} in string eq at /usr/lib/firewall/rules.pl line 764. Use of uninitialized value $blocklistsettings{"LOGGING"} in string eq at /usr/lib/firewall/rules.pl line 764.
Fix has been sent to the development mailing list: https://patchwork.ipfire.org/project/ipfire/patch/20230307121735.6485-2-stefan.schantl@ipfire.org/
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=1b70ead36dfaf6541677e4ac5d05867273eaa265 https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=0450dce6f6eb02fc539c0f0d0ccc01a281dcad58
https://blog.ipfire.org/post/ipfire-2-27-core-update-174-is-available-for-testing
Tested this with CU174 Testing on my vm testbed and confirmed that the log checkbox can be changed and stays as changed after the page has been saved. This verifies the bug fix.
https://blog.ipfire.org/post/ipfire-2-27-core-update-174-released