pfblockerNG-devel 3.1.0_5

Bob.Dig

@fireodo I can't see it on 22.05-RELEASE.

fireodo

@bob-dig said in pfblockerNG-devel 3.1.0_5:

I can't see it on 22.05-RELEASE.

Maybe its only for CE 2.6.0 ...? Hmmm

jdeloach

@fireodo said in pfblockerNG-devel 3.1.0_5:

@bob-dig said in pfblockerNG-devel 3.1.0_5:

I can't see it on 22.05-RELEASE.

Maybe its only for CE 2.6.0 ...? Hmmm

I loaded it on my CE 2.6.0 but I haven't noticed anything different either.

SteveITS

@fireodo In System/Package Manager if you click the (old/installed) version number it is a link to the repo history. While not exactly a changelog that shows the history of commits.

Looks like it fixes the CPU load/logging/reporting issue among other things.

fireodo

@steveits said in pfblockerNG-devel 3.1.0_5:

In System/Package Manager if you click the (old/installed) version number it is a link to the repo history. While not exactly a changelog that shows the history of commits.

I was there, but as you say I saw the repo history, but I didn't find a kind of changelog - thats why I asked the forum.

provels

3.1.0_6 now showing for pfS+ 22.05.

Gertjan

After updating to 3.1.0_6 on 22.05 :

Read : https://redmine.pfsense.org/issues/13154 - the remark of Denny Page :

This issue is still present in the just released pfBlockerNG-devel 3.1.0_6.
Same fix as before:

So, don't forget to re apply the patch in system patcher (you have to create yourself this patch).

I had to start unbound (it was stopped after upgrading to 3.1.0_6
Check the pfBlokcerng dashboard widget : a yellow DNSBL icon means : it's time for a force reload all.

Bob.Dig

@gertjan said in pfblockerNG-devel 3.1.0_5:

https://redmine.pfsense.org/issues/13154

I can confirm, IP-logging is again not working.

fireodo

@provels said in pfblockerNG-devel 3.1.0_5:

3.1.0_6 now showing for pfS+ 22.05.

What I have also seen is that the commits are not from BBcan177 ... is someone else the maintainer now?

Gertjan

@fireodo

From what I've understood, read 'here' and 'there', Netgate/pfSense is now the maintainer of pfblockerNG-devel.

fireodo

@gertjan said in pfblockerNG-devel 3.1.0_5:

From what I've understood, read 'here' and 'there', Netgate/pfSense is now the maintainer of pfblockerNG-devel.

Thanks - thats what i supposed too ...

jdeloach

@gertjan said in pfblockerNG-devel 3.1.0_5:

From what I've understood, read 'here' and 'there', Netgate/pfSense is now the maintainer of pfblockerNG-devel.

That is sad to hear. Guess that means the beginning of the end for a great addon package.

@BBcan177 had great plans if Netgate ever moved to FreeBSD 13 but since that hasn't happened, I guess he decided to move on to greener pastures.

provels

@jdeloach said in pfblockerNG-devel 3.1.0_5:

@BBcan177 had great plans if Netgate ever moved to FreeBSD 13

According to the RSS, they're heading right to 14.

keyser

@jdeloach said in pfblockerNG-devel 3.1.0_5:

@gertjan said in pfblockerNG-devel 3.1.0_5:

From what I've understood, read 'here' and 'there', Netgate/pfSense is now the maintainer of pfblockerNG-devel.

That is sad to hear. Guess that means the beginning of the end for a great addon package.

@BBcan177 had great plans if Netgate ever moved to FreeBSD 13 but since that hasn't happened, I guess he decided to move on to greener pastures.

I hope not. If pfBlockerNG goes unmaintained and dies of, that will be the end of pfSense for most - if not all - of my pfSense customers.
That very package is what makes pfSense a very compelling offer even though it uses FreeBSD (with it’s glaring lack of drivers, 4G support, proper mobile user IPsec VPN and what not).
Here’s hoping that Netgate will throw ressources at pfBlocker and integrate it even further as a standard feature in pfSense+ (I’m guessing that if they do, it will be + only :-))

If not, I guess 22.05 will be the end station for upgrading my own and customers appliances.

mcury

Is this the correct shasum for 3.1.0_6 with the patch applied?

Before patch:
shasum /usr/local/pkg/pfblockerng/pfblockerng.inc.orig
fc56abd134d3c35fe66a4736f080c545b42e827b  /usr/local/pkg/pfblockerng/pfblockerng.inc.orig

After patch:
shasum /usr/local/pkg/pfblockerng/pfblockerng.inc
3012a2cd5c1c442671d50b2c7421e69149678cd7  /usr/local/pkg/pfblockerng/pfblockerng.inc

dennypage

@mcury said in pfblockerNG-devel 3.1.0_5:

Is this the correct shasum for 3.1.0_6 with the patch applied?

Yes.

dennypage

@keyser said in pfblockerNG-devel 3.1.0_5:

@jdeloach said in pfblockerNG-devel 3.1.0_5:

@gertjan said in pfblockerNG-devel 3.1.0_5:

From what I've understood, read 'here' and 'there', Netgate/pfSense is now the maintainer of pfblockerNG-devel.

That is sad to hear. Guess that means the beginning of the end for a great addon package.

@BBcan177 had great plans if Netgate ever moved to FreeBSD 13 but since that hasn't happened, I guess he decided to move on to greener pastures.

I hope not. If pfBlockerNG goes unmaintained and dies of, that will be the end of pfSense for most - if not all - of my pfSense customers.
That very package is what makes pfSense a very compelling offer even though it uses FreeBSD (with it’s glaring lack of drivers, 4G support, proper mobile user IPsec VPN and what not).
Here’s hoping that Netgate will throw ressources at pfBlocker and integrate it even further as a standard feature in pfSense+ (I’m guessing that if they do, it will be + only :-))

If not, I guess 22.05 will be the end station for upgrading my own and customers appliances.

I don't know that @BBcan177 has "moved on" per se. I do know that he is personally very, very busy right now. It's unclear how much time he will have for a while to devote time to trivial things like coding.

keyser

@dennypage Which is fair, but…

Where is the _5 and _6 updates then coming from?
Is it just me, or is it not VERY strange there are no proper release notes to be found - AND niether version fixes the only big and very obvious known bug that needs fixing?

OpIT GmbH

I dont know why they bring an Update with no Release Notes and also no fix for this..

https://redmine.pfsense.org/issues/13154
https://redmine.pfsense.org/issues/13156

Both Tickets are the same problem. The Patch is still needed i think.

Gertjan

@keyser said in pfblockerNG-devel 3.1.0_5:

Where is the _5 and _6 updates then coming from?

Check github.
There is a huge "issue' coming up : the eternal "where is the new pfSEnse" and as as soon as it comes out : I have to go back because ...
The shift to FreeBSD 14 is such an issue, and the shift to PHP 8.1 is even bigger.
pfBockerng-devel is by far the biggest pfsense package. It is only based on PHP (and some python ;) ) and this package needs to work when the next pfSense comes out.
Edits in github points to PHP 8.1 conversion.

True, it's a bit silly that for those who want to use pfBockerng-devel right know, they will have to know to 'read', know how to find their way to this forum, find the issue, know how to edit e file (or make the patch), and apply the correction. Not much for some, far more for others.
Maybe the current issue is already patched in some upstream "2.7.0" repository, and it wasn't back ported to current.

For myself, I undid the patch before upgrading, and to my surprise it could still 'apply' the same patch when upgraded to 0_6. This means the the bug wasn't corrected. (If it was actually a bug ?) Anyway, the solution was a one click show = apply again.

@opit-gmbh said in pfblockerNG-devel 3.1.0_5:

I dont know why they bring an Update with no Release Notes and also no fix for this.

pfblokcerng-devel is now treated as most other interim updates (acme etc) : their is an update, without the ticket parade.
With BBcan77 we saw far more info.