pfBlockerNG/pfBlockerNG-devel v3.2.0_2

emikaadeo

@roger-s
This is a known issue. Read the first post from @BBcan177
Full Details here

There is still a Regression with TLD Wildcard Feature in pfSense+ (possibly in pfSense 2.6 also) due to some recent changes to FreeBSD Grep command. This is being reviewed and will provide more updates as soon as we have a solution.
The only solution for now is to disable Wildcard Blocking (TLD) in pfBlockerNG

raidflex

So I tried to update to 3.2.0_2 but the update is failing.

>>> Upgrading pfSense-pkg-pfBlockerNG... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-pkg-pfBlockerNG: 3.2.0_1 -> 3.2.0_2 [pfSense]

Number of packages to be upgraded: 1

2 MiB to be downloaded.
pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_01_amd64-pfSense_plus_v23_01/All/pfSense-pkg-pfBlockerNG-3.2.0_2.pkg: Not Found
Failed

EDIT: Update works now please disregard.

mcury

Installed this version on my SG-3100, using DNSBL python mode, with geoIP.

It's working perfectly fine for me, thanks a lot for all your efforts in fixing the problems, BBcan177 and Netgate team.

pfsjap

@jrey BBcan177 posted a fix for the download problem: https://www.reddit.com/r/pfBlockerNG/comments/116fuie/temp_workaround_to_get_latest_v320_2_files/

jrey

@pfsjap

Thanks, but I wasn't looking for the 3.2.0_2 package.

The issue for me had nothing to do with the lack of that package. I spent some time working through the code and providing feedback to @BBcan177 over the weekend. A local code change worked out to resolve the issue. So for my case (which was a real problem documented in this thread by the way) I'm not sure that changes made to test the change would be in the 3.2.0_2 package at this point. So I'm unlikely to even try until all my current testing is complete.

PS @BBcan177 I just waiting for a 12:00 time cycle to pass "12hours" and I'll send you the notes. Thanks JR

raidflex

Looks like the update worked now, idk why it was not before.

Does this also fix the PHP errors and freezing of the Pfblockerng widget on the dashboard?

EDIT: Looks like this PHP error is still present, it freezes PfSense+ 23.01 so hopefully its fixed soon. I had to remove the pfblockerng widget and all is well again.

BBcan177

@raidflex
I am working on the next version. Can you test this widget patch please?

curl -o /usr/local/www/widgets/widgets/pfblockerng.widget.php "https://gist.githubusercontent.com/BBcan177/6d4e9aa41cbbd802b69c0501a2c7d092/raw"

raidflex

@bbcan177 said in pfBlockerNG/pfBlockerNG-devel v3.2.0_2:

@raidflex
I am working on the next version. Can you test this widget patch please?
curl -o /usr/local/www/widgets/widgets/pfblockerng.widget.php "https://gist.githubusercontent.com/BBcan177/6d4e9aa41cbbd802b69c0501a2c7d092/raw"

This did fix the widget issue. I also rebooted to ensure no PHP errors are present and the freezing has also been resolved. Thank you!

BBcan177

@raidflex Thanks for testing!

dennypage

@bbcan177 Do you have a fix to test for the URL validation errors?

BBcan177

@dennypage trying to remember which error in particular? But there was a change made to v3.2.0_2 to avoid appending any local DNS to the validation. So if the url was feed.com, the validation uses "feed.com." (added a trailing dot)

dennypage

@bbcan177 said in pfBlockerNG/pfBlockerNG-devel v3.2.0_2:

@dennypage trying to remember which error in particular?

This one: pfBlockerNG update errors

BBcan177

@dennypage should already be fixed in v3.2.0_2

dennypage

@bbcan177 said in pfBlockerNG/pfBlockerNG-devel v3.2.0_2:

should already be fixed in v3.2.0_2

v3.2.0_2 isn't showing yet in 23.01, but I assume it will soon. Thanks.

johnpoz

@dennypage I updated to it on 23.01

There was error first time clicked on it that couldn't download package, but it worked 2nd time

dennypage

@bbcan177 And of course, as soon as I post it shows up.

3.2.0_2 does indeed correct the URL issue. Thanks!

michmoor

@BBcan177 Seems to be stuck when updating

michmoor

I take it the TLD issue is still not fixed.
This update only addresses the GeoIP problem?

MoonKnight

@johnpoz
Didn't see any update after multiple refresh on "Installed Packages" so I did an force update from the console "13", then back to "Installed Packages". Now I see multiple updates ready for update, weird :)

cmcdonald

@michmoor The issue is fixed internally. An update should be available soon.