pfBlockerNG-devel v3.0.0_10
-
You likely aren't running the extra stuff I have such as haproxy, and ntopng. I also have my guest WiFi connection going through my pfSense from Unifi. It wasn't crashing before I installed pfBlockerNG, after that's been nothing but issues. :(
-
@teamits said in pfBlockerNG-devel v3.0.0_10:
So perhaps it increased in 21.02?
Nope, it just take your number as default. :)
-
@ronpfs said in pfBlockerNG-devel v3.0.0_10:
Nope, it just take your number as default. :)
You're right. That's dumb. 2.4.5 does that too.
-
@teamits said in pfBlockerNG-devel v3.0.0_10:
@smoothrunnings said in pfBlockerNG-devel v3.0.0_10:
pfSense keeps rebooting
The out of memory error can't really cause a reboot AFAIK. I think those are two different symptoms. You only need a table size big enough to handle the table entries you're loading.
So provide me with the tool/instructions to verify that instead of just stating it.
What I am stating and will continue to state is I am running this on a WatchGuard M400 with an intel i5-4750, 8GB of RAM, and 250GB SSD.
Since last week I have been running my M400 with DHCP services for my WiFi Guest network, along with haproxy and ntopng for about a year without any issues, at the time I installed pfBlockerNG 3.0 Devel I was running on 2.4.5 and was getting the random reboots of pfSense on 2.4.5 which why I rolled over to 2.5.0.
Looking at my pfSense this morning its uptime is 55 minutes right now, meaning through the night its rebooted.
I think at this point someone needs to give me a hand looking through the logs to see why the pfsense keeps rebooting. Maybe it's coincidence that it started happening after pfBlockerNG was installed, but maybe it's it not, no one will really know until I get some help (the firewall just rebooted again), looks like its this time it hit about 6764 blocked IPs and rebooted. As I was saying the answer will likely be in the logs, but I don't know what to look for, so instead of just pointing fingers or saying "its working here" help.
Thanks,
-
@smoothrunnings Maybe start a new forum post with Settings info and logs.
-
Looks like there might be an issue with ntopng and pfBlockerNG. I saw some errors in the logs for ntopng, so decided to remove the service and so far (knock on wood) pfSense has been running for over 4 hours and pfBlockerNG has blocked over 28k IPs without a reboot.
Whats a good forum to start a new thread in, in case there is some weird issue going on?
Thanks,
Updated typo's
-
-
@ronpfs said in pfBlockerNG-devel v3.0.0_10:
it just take your number as default
FWIW I made https://redmine.pfsense.org/issues/11566
-
@teamits Turns out that's not the issue, the issue was with unbound. As soon as I patched it the FW hasn't rebooted...its been running for over 15 hours now.
-
I upgraded our one router with CE to 2.5, so uninstalled pfBlockerNG-devel 2.x and installed 3.0.0_10 afterwards.
If I click on any of the URLs in the Packets column of the dashboard wizard (https://router/pfblockerng/pfblockerng_alerts.php?filterip=pfB_Africa_v4) I get:
Fatal error: Uncaught Error: Cannot use string offset as an array in /usr/local/www/pfblockerng/pfblockerng_alerts.php:160 Stack trace: #0 {main} thrown in /usr/local/www/pfblockerng/pfblockerng_alerts.php on line 160 PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_alerts.php, Line: 160, Message: Uncaught Error: Cannot use string offset as an array in /usr/local/www/pfblockerng/pfblockerng_alerts.php:160 Stack trace: #0 {main} thrown
-
@teamits said in pfBlockerNG-devel v3.0.0_10:
/usr/local/www/pfblockerng/pfblockerng_alerts.php:160
Comment out that line #160, by prefixing "//" to it (without the quotes). Will get that fixed in next version.
