PfBlocker seems completely broken since last build
-
The pfblockerNG package is about to be committed and works a LOT better than the old pfblocker package.
It was designed for 1.2.3.
-
Ok, so this means better wait for the new package….
-
YES :)
-
O what a shame, the thing with the "admin" in the fields was caused by a broken firefox plugin which filled these fields :o ::)
But nonetheless after fixing that I am getting still crash reports when saving something in pfBlocker.But we already know now that we should wait on pfblocker-ng anyway 8)
-
Supermule, what time frame are we looking at for pfblocker-NG release?
-
-
It should be in the final stages and are waiting for at commit….
I will link this to Anthony so he can comment on it :)
-
I think it's been submitted - it's awaiting review/approval by "the powers that be".
-
You can watch the status here:
-
It seems a merge has taken place into pfsense master…
https://github.com/pfsense/pfsense-packages/pull/743
So I guess it means it should be available quite soon...
-
It was merged to make it easier for Renato to review the code. It's a lot of code, it might take a bit. Get excited, it is awesome when combined with Snort or Suricata.
-
Get excited, it is awesome when combined with Snort or Suricata.
There is a lot to be excited about with pfBlockerNG…
The cost/benefit ratio of maintaining and monitoring pfBlockerNG is very high. Suricata's in IDS mode is rather low in comparison. pfBlockerNG actually pushed me over the edge to remove Suricata.
If Suricata could be used in IPS mode I might put it back in play. But as it sits I'd rather put the effort into maintaining block lists.
Your mileage may vary.
-
And it was actually my idea to begin with ;)
