pfBlockerNG-devel: Version 3.1.0_2 - Fix for #12706

cantor

If I don't get something wrong, version 3.1.0_2 will fix bug #12706 https://redmine.pfsense.org/issues/12706.
Does anybody know when version 3.1.0_2 might be available via Package Manager?

Regards cantor

lohphat

@cantor Confirmed fixed with today's 3.1.0_2 release.

Tzvia

Reintroduced the high cpu usage, up from 5% average to around 20% that the hotfix had resolved a few weeks ago. I turn off PFBlocker and it goes back to normal...

fireodo

... and the "no IP logging" seems to be back too ...
https://forum.netgate.com/topic/169610/ip-logs-are-not-being-created-populated/14

Temporary fix:

curl -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/7cb8635199446866d511b97166d65296/raw/"

and after that restart pfb_filter

Cool_Corona

So in short, dont upgrade....

Gertjan

@cool_corona said in pfBlockerNG-devel: Version 3.1.0_2 - Fix for #12706:

So in short, dont upgrade....

If you use RAM disks.
Right ?

Cool_Corona

@gertjan Does it matter?

emikaadeo

Wait for v3.1.0_3
https://www.reddit.com/r/pfBlockerNG/comments/tmlgg1/comment/i1zm0xd/

Gertjan

@cool_corona said in pfBlockerNG-devel: Version 3.1.0_2 - Fix for #12706:

@gertjan Does it matter?

As https://redmine.pfsense.org/issues/12706 tells me :

Description

How to reproduce:
1) Install pfBlockerNG-devel, and configure DNSBL in python mode
2) Enable RAM disk for /var
3) After reboot, all files associated with pfblockerng are deleted:
/var/unbound/pfb_unbound.py
/var/unbound/pfb_unbound_include.inc
/var/unbound/pfb_py_hsts.txt
4) ...and unbound doesn't start:

But I have no RAM disks, as 'my case' is like many others : not much RAM, but loads of (SSD) disk space.
So, no step 2 for me. The issue becomes a none issue.
The issue is real, that's not the question.