Pfsense updated to 2.8 and now get an crash report
-
I would leave it at the default 512MB and enable python mode. That is the expected/tested workaround there.
If you still see issues then revisit.
-
@stephenw10 Thanks Stephen, I appear to have around 3 million blocks in block lists.
-
Mmm, quite a lot!
-
@stephenw10 Probably too many. I went a bit overboard selecting lists.
As an aside, my whole set up EVERYTHING network from the ONT, switch, VOIP ATA, server to wifi uses around ~36 watts
-
@stephenw10 Is this something that may change in the future as a default setting, since it seems not using python mode just causes problems? Or that would be on the pfblocker dev's to make that change?
-
Mine locked-up early in the upgrade process but a quick push of the power button on my Vault caused it to powered down after a short delay and when it came back up it was still working fine on 2.7.2.
RPSmith...
-
It ultimately had problems and had to be reflashed!
RPSmith...
-
@MBILC said in Pfsense updated to 2.8 and now get an crash report:
Is this something that may change in the future as a default setting, since it seems not using python mode just causes problems?
Unclear. Python mode also introduces complexity many users don't need. But, yes, that would be a choice the pfBlockerNG dev makes IMO.
-
Changing over to python mode has significantly reduced cpu usage on my system from around 25% to less than 10%.
-
Just checking the power log for the server and showing a saving of about 75-100 watts per day since changing over to python mode. Or about £8 a year in electricity.
-
You mean Watt-hours per day? That's significant. Nice
-
@stephenw10 Yes, I meant Wh it went from ~900 watt hours to ~825 watt hours per day.
