pfBlockerNG Crash Report version 3.2.0_16 pfSense version 24.11 DNSBL UT1 Adult Category added

uniqueusername

Hi,

I have a Netgate 3100 with version 24.11 and pfBlockerNG 3.2.0._16 installed.

I just enabled the UT1 category Adult to block port (teenage son...) and I'm seeing the following crash when I force update:

PHP {$errortype}s

PHP ERROR: Type: 1, File: /usr/local/pkg/pfblockerng/pfblockerng.inc, Line: 3951, Message: Allowed memory size of 134217728 bytes exhausted (tried to allocate 125096640 bytes) @ 2025-01-04 18:10:16

Crash report begins. Anonymous machine information:

arm
15.0-CURRENT
FreeBSD 15.0-CURRENT #0 plus-RELENG_24_11-n256407-1bbb3194162: Fri Nov 22 05:04:59 UTC 2024 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-24_11-main/obj/armv7/k0yp0fpJ/var/jenkins/workspace/pfSense-Plus-snapshots-24_11-main/sources/FreeBS

Crash report details:

PHP Errors:
[04-Jan-2025 18:10:16 America/Chicago] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 125096640 bytes) in /usr/local/pkg/pfblockerng/pfblockerng.inc on line 3951

No FreeBSD crash data found.

I know I'm out of luck in terms of support for the 3100, but I'm holding off upgrading for a bit longer.

Regards,

Neil

Gertjan

@uniqueusername said in pfBlockerNG Crash Report version 3.2.0_16 pfSense version 24.11 DNSBL UT1 Adult Category added:

I just enabled the UT1 category Adult to block port ....

Not that one.
The fast reply : You can't buy a "3100" (a 1 Mega RAM arm device) and then use a functionality' that asks for way more processor power, and way (like 4 or 8 times) more memory.

The thing is, this file is not just large, it's more like huge ... and even if you can download it it, the next step will bring the system down : it has (hundreds of) thousands of lines, and pfBlockerNG will read them in one by one in memory (...,) together with all the other DNSBL you've also selected, and then it will remove the doubles ... and then filters them for the known DNSBL host names to be whitelisted, and so one. This task will bring PHP to it's knees.
I know, because on my 4100 with 4 Mbytes most often it will fail also, with the same error.
Put a "post it" on it, with : "try me again when I have the memory" ;)