PfBlockerNG v2.0 w/DNSBL

Qinn

@Qinn:

Hi there is it possible to save and restore the pfBlockerNG settings at a certain phase, so when you mess up you can return to a previous setup?

Every change in pfBlockerNG is saved in the config file.

You can save the config with Diagnostics/Backup & Restore/Backup & Restore and do a restore of the config at a later time.

Thanks for the reply, but I was hoping for a separate config file, as far as I can see there is none.

PF64

@wiz561:

I just updated the pfBlockerNG package and I'm now receiving these errors when I reboot…
There were error(s) loading the rules: /tmp/rules.debug:47: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [47]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 12:37:54
There were error(s) loading the rules: /tmp/rules.debug:47: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [47]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 12:39:58
There were error(s) loading the rules: /tmp/rules.debug:47: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [47]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 12:40:37
I'm running pfBlockerNG 2.1.1_2 with PfSense 2.3.2-RELEASE (amd64). I have 2gb of memory and 34% in use with a 2gb swap and 0% in use (for the swap).

I'm assuming it's not a memory issue and possibly something else. I was wondering if anybody else had this issue and what a possible fix may be.

Thanks!

I have a huge issue with the last update as well. It eats memory like a banshee in a matter of minutes! I have 16Gb and it fills it to the brim then gives me the same errors, can't load rules.

f34rinc

@PF64:

I have a huge issue with the last update as well. It eats memory like a banshee in a matter of minutes!

Are you using the new DNSBL TLD feature?

RonpfS

Did you raise the Firewall Maximum Table Entries?
How many IPs are blocked ? Did you enabled De-Duplication? CIDR Aggregation? Suppression?

If you are using DNSBL, how many domains does it reports after a Force Reload?
Suppressing a Domain in the Alert Tab will consume memory.

What do you see in the log file during Update ?
Provide more info on you setup so we can pinpoint the issue.

Panja

I used DNSBL before but have disabled it at the moment.
Is it correct I can still ping the virtual IP address (default: 10.10.10.1) even after disabling DNSBL?

[UPDATE]
I uninstalled pfBlockerNG and unticked the box that says "keep settings".
After that I re-installed pfBlockerNG and configured everything without enabling DNSBL.
The virtual IP assigned to DNSBL is not pingable now. I "fixed" the problem myself. 8)

Qinn

Got a crash report running on 2.3.2-RELEASE (i386) with pfBlockerNG 2.1.1_2 with only DNSBL setup according to advise #18 (https://forum.pfsense.org/index.php?topic=102470.15), btw having enabled Alexa with 1K set.

Thanks for any help/advise cheers Qinn

Crash report begins. Anonymous machine information:

i386
10.3-RELEASE-p5
FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 14:11:41 CDT 2016 root@ce23-i386-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense_wrap_vga

Crash report details:

PHP Errors:
[03-Aug-2016 05:06:13] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20 bytes) in /usr/local/www/pfblockerng/pfblockerng.php on line 728
[03-Aug-2016 05:06:13] PHP Stack trace:
[03-Aug-2016 05:06:13] PHP 1. {main}() /usr/local/www/pfblockerng/pfblockerng.php:0
[03-Aug-2016 05:06:13] PHP 2. pfblockerng_get_countries() /usr/local/www/pfblockerng/pfblockerng.php:105
[03-Aug-2016 05:06:13] PHP 3. explode() /usr/local/www/pfblockerng/pfblockerng.php:728

Filename: /var/crash/minfree
2048

RonpfS

@Qinn:

Got a crash report running on 2.3.2-RELEASE (i386) with pfBlockerNG 2.1.1_2 with only DNSBL setup according to advise #18 (https://forum.pfsense.org/index.php?topic=102470.15), btw having enabled Alexa with 1K set.

Thanks for any help/advise cheers Qinn

Can you run from Shell

php /usr/local/www/pfblockerng/pfblockerng.php dc

That will download the latest MaxMind as it did that yesterday (first tue of each month). Looks like you may have ran out of memory. How much memory do you have in the box?

You can also look in the Firewall/pfBlockerNG/Log Browser at the extra.log or pfBlockerNG.log file.

Qinn

@RonpfS:

@Qinn:

Got a crash report running on 2.3.2-RELEASE (i386) with pfBlockerNG 2.1.1_2 with only DNSBL setup according to advise #18 (https://forum.pfsense.org/index.php?topic=102470.15), btw having enabled Alexa with 1K set.

Thanks for any help/advise cheers Qinn

Can you run from Shell

php /usr/local/www/pfblockerng/pfblockerng.php dc

That will download the latest MaxMind as it did that yesterday (first tue of each month). Looks like you may have ran out of memory. How much memory do you have in the box?

You can also look in the Firewall/pfBlockerNG/Log Browser at the geoip.log or pfBlockerNG.log file.

Took a look at the code with:

sed -n '720,740p' /usr/local/pkg/pfblockerng/pfblockerng.inc

but can't see anything strange?

Second, I followed your advise, here are the results, btw Memory size = 1Gb (1024) usage 18%, during the process below I noticed that Memory usage rose from 16% to 28% and dropped to 17% after the error occurred, as shown below. It seems the process eats RAM and somehow there is a max set for the process.

[2.3.2-RELEASE][root@pfSense.localdomain]/root: php /usr/local/www/pfblockerng/pfblockerng.php dc
Country code update Start [ 08/03/16 13:17:48 ]
Converting MaxMind Country databases for pfBlockerNG.
Processing ISO IPv4 Continent/Country Data
Processing ISO IPv6 Continent/Country Data
Creating pfBlockerNG Continent XML files
IPv4 Africa
IPv6 Africa
IPv4 Antarctica
IPv6 Antarctica
IPv4 Asia
IPv6 Asia
IPv4 Europe
IPv6 Europe

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 23 bytes) in /usr/local/www/pfblockerng/pfblockerng.php on line 728

Call Stack:
0.0043 233872 1. {main}() /usr/local/www/pfblockerng/pfblockerng.php:0
397.0779 6345188 2. pfblockerng_get_countries() /usr/local/www/pfblockerng/pfblockerng.php:105
404.0040 38288884 3. explode() /usr/local/www/pfblockerng/pfblockerng.php:728

PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng.php, Line: 728, Message: Allowed memory size of 134217728 bytes exhausted (tried to allocate 23 bytes)
[2.3.2-RELEASE][root@pfSense.localdomain]/root:

any advice is welcome,

cheers, Qinn

Guest

@Qinn:

Got a crash report running on 2.3.2-RELEASE (i386) with pfBlockerNG 2.1.1_2 with only DNSBL setup according to advise #18 (https://forum.pfsense.org/index.php?topic=102470.15), btw having enabled Alexa with 1K set.

Thanks for any help/advise cheers Qinn

Crash report begins. Anonymous machine information:

i386
10.3-RELEASE-p5
FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 14:11:41 CDT 2016 root@ce23-i386-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense_wrap_vga

Crash report details:

PHP Errors:
[03-Aug-2016 05:06:13] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20 bytes) in /usr/local/www/pfblockerng/pfblockerng.php on line 728
[03-Aug-2016 05:06:13] PHP Stack trace:
[03-Aug-2016 05:06:13] PHP 1. {main}() /usr/local/www/pfblockerng/pfblockerng.php:0
[03-Aug-2016 05:06:13] PHP 2. pfblockerng_get_countries() /usr/local/www/pfblockerng/pfblockerng.php:105
[03-Aug-2016 05:06:13] PHP 3. explode() /usr/local/www/pfblockerng/pfblockerng.php:728

Filename: /var/crash/minfree
2048

I have an identical situation except the line "(tried to allocate 20 bytes)" reads 27 bytes. Also, the PHP Errors block repeats itself a few times.
I tried to reinstall pfBlockerNG through the package manager, it claimed to have reinstalled but it no longer shows under the Firewall menu of pfSense. I uninstalled and reinstalled in two steps, again using the package manager, same result. For now I removed the package. My hardware is based on 32 bit N270 and I have 1GB of RAM, tons of HD space.
Prior to upgrading pfSense to 2.3.2 everything worked flawlessly for over a month so I assume that it has something to do with pfSense upgrade. I don't recall when I got pfBlockerNG upgraded.
I hope mine is not an isolated case.

RonpfS

@Qinn:

Second, I followed your advise, here are the results, btw Memory size = 1Gb (1024) usage 18%, during the process below I noticed that Memory usage rose from 16% to 28% and dropped to 17% after the error occurred, as shown below. It seems the process eats RAM and somehow there is a max set for the process.

any advice is welcome,

cheers, Qinn

1GB might be too small since the last MaxMind database change. Can you put more RAM in the box?

I have 2.5GB on my pfsense and I got a crash report :o
This looks like a change at some point in the MaxMind db. So be patient until BBcan177 take a looks at this.

RonpfS

@haleakalas:

I have an identical situation except the line "(tried to allocate 20 bytes)" reads 27 bytes. Also, the PHP Errors block repeats itself a few times.
I tried to reinstall pfBlockerNG through the package manager, it claimed to have reinstalled but it no longer shows under the Firewall menu of pfSense. I uninstalled and reinstalled in two steps, again using the package manager, same result. For now I removed the package. My hardware is based on 32 bit N270 and I have 1GB of RAM, tons of HD space.
Prior to upgrading pfSense to 2.3.2 everything worked flawlessly for over a month so I assume that it has something to do with pfSense upgrade. I don't recall when I got pfBlockerNG upgraded.
I hope mine is not an isolated case.

Maybe it is too late, but did you get any errors while removing or installing pfBlockerNG?

Qinn

Although today 1GB Memory isn't much, maybe the dev's (BBcan177) could be encouraged ;) to find a solution as the pfSense recommended requirements are (https://www.pfsense.org/hardware/) RAM - 1 GB. So I put in a extra 512MB (so now 1,5GB), but I am shit out of luck, again error. Should have guessed it, as even your 2,5GB wasn't enough.

Qinn

Hmmm, I have searched the forum and this error has occurred many times, and never the solution was to increase memory:

https://forum.pfsense.org/index.php?topic=87994.0

https://forum.pfsense.org/index.php?topic=113483.0

https://forum.pfsense.org/index.php?topic=102904.0

https://forum.pfsense.org/index.php?topic=76981.0

RonpfS

I get these messages Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 36 bytes)
from time to time with other function in pfsense, when viewing big file or with backup.
And I never found a solution for these.

I disabled pfBlockerNG, DSNBL, surricata, reboot, close all pfsense tabs.
This gives me around 1.8GB of free memory, and the pfblockerng.php dc still crashes.

Is there someone with more than 2.5GB of memory that doesn't have crash when updating the MaxMind GeoIP db ?

Qinn

https://forum.pfsense.org/index.php?topic=116305.0

https://forum.pfsense.org/index.php?topic=116307.0

Problem seems to be spreading…

vbentley

@oswoldy:

Hi,
I get the crash with 8GB of RAM :(

I guess I won't bother installing any more than the 4GB that I currently have installed. I have disabled pfBlockerNG for the time being.

Gerard64

Same here with 4gb ram.

I tried to reinstall Pfblocker but no luck now it doesn't even show up anymore under Firewall menu item.
Before I reinstalled it hanged constantly on update the lists.

RonpfS

Well during installation pfBlockerNG download the MaxMind GeoIP database … it probably crashes and the installation doesn't complete. :o

q54e3w

do you see stability if you reduce the number of lists you have active? My 16GB runs along fine at 40% utilisation with a fair few lists thrown at it and I recall from my casual observation it uses more whilst it processes them too.

Guest

@RonpfS:

@haleakalas:

I have an identical situation except the line "(tried to allocate 20 bytes)" reads 27 bytes. Also, the PHP Errors block repeats itself a few times.
I tried to reinstall pfBlockerNG through the package manager, it claimed to have reinstalled but it no longer shows under the Firewall menu of pfSense. I uninstalled and reinstalled in two steps, again using the package manager, same result. For now I removed the package. My hardware is based on 32 bit N270 and I have 1GB of RAM, tons of HD space.
Prior to upgrading pfSense to 2.3.2 everything worked flawlessly for over a month so I assume that it has something to do with pfSense upgrade. I don't recall when I got pfBlockerNG upgraded.
I hope mine is not an isolated case.

Maybe it is too late, but did you get any errors while removing or installing pfBlockerNG?

No, there was no error messages during the reinstall, removal or installation. But, the weird thing is that although pfSense said the installation (or the reinstallation) was a success, pfBlockerNG was nowhere to be found; in the menus nor in the service status, watchdog, etc. So, I assume that it didn't install properly. But the dashboard says that only 20% of the RAM is used, so I doubt that this is a memory issue. Plus, I have been using pfBlockerNG on this same hardware for some time, so unless the last version has changed something drastically 1GB has been fine.
Meanwhile, I restored a raw copy backup of my system prior to 2.3.2 upgrade. That works like a charm. It has pfBlockerNG 2.0.17 on pfSense 2.3.1-p5 (i386). PfBlocker definitely works as it blocks access to and from China, Russia, etc.
So, until the dust settles oldies are the best way to go for me.