pfBlockerNG-devel v3.2.0_15

LarryFahnoe

I solved my problem by following @stephenw10 suggestions on this thread: https://forum.netgate.com/post/1185688 Thanks Stephen!!

Also needed to kill off a pfblockerng.php cron process left over from the prior devel version.

--Larry

peroni5

... 3.2.0.16 is out

Unoptanio

@peroni5
Have you tried, does it work?

Gertjan

@peroni5 said in pfBlockerNG-devel v3.2.0_15:

... 3.2.0.16 is out

Yeah, saw that.
Did a save, a ZFS clone, rebootted from that, and installed the "16".
Saw procs hitting 100 % again as this morning, so I bailed out. I'll give it a 7 days cool-down from now ^^

3aandl

@Gertjan 3.2.0_17 was released and install etc. is working as it should now

Unoptanio

@Gertjan

This is a great system for testing, ZFS Boot Environment.
Too bad it didn't occur to me

Gertjan

@3aandl

I just installed _17 and that one is fine.

deepakm

I face same problem after upgrading . But i resolved it.

First Login by ssh then enter shell (8). Then enter cd /usr/local/www/ directory and remove pfblockerng folder . Then make new directory pfblockerng and give directory root:wheel permission. After this process run this cmd

For pfsense plus (

curl -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/72d559647564acc6a0b8353b72a40049/raw"
curl -o /usr/local/pkg/pfblockerng/pfblockerng.sh "https://gist.githubusercontent.com/BBcan177/abdeba2d1ee055efe3d5c23ab558c40d/raw"
curl -o /usr/local/www/pfblockerng/pfblockerng.php "https://gist.githubusercontent.com/BBcan177/8d67e132ad16b895b5dd8996c22359e3/raw"
curl -o /usr/local/www/pfblockerng/pfblockerng_ip.php "https://gist.githubusercontent.com/BBcan177/ff538442a2e7cf78a9f24119b70f575a/raw"
curl -o /usr/local/www/pfblockerng/pfblockerng_alerts.php "https://gist.githubusercontent.com/BBcan177/f2873a9b59bb491f5af6802c72807110/raw") and

for pfsense CE ( curl -o /usr/local/pkg/pfblockerng/pfblockerng.inc "https://gist.githubusercontent.com/BBcan177/e0347961852bfed16408bae2b475c36a/raw"
curl -o /usr/local/pkg/pfblockerng/pfblockerng.sh "https://gist.githubusercontent.com/BBcan177/abdeba2d1ee055efe3d5c23ab558c40d/raw"
curl -o /usr/local/www/pfblockerng/pfblockerng.php "https://gist.githubusercontent.com/BBcan177/8d67e132ad16b895b5dd8996c22359e3/raw"
curl -o /usr/local/www/pfblockerng/pfblockerng_ip.php "https://gist.githubusercontent.com/BBcan177/ff538442a2e7cf78a9f24119b70f575a/raw"
curl -o /usr/local/www/pfblockerng/pfblockerng_alerts.php "https://gist.githubusercontent.com/BBcan177/5a9a16698410c1171ddbb74df1007c7b/raw"
curl -o /usr/local/pkg/pfblockerng/pfblockerng_extra.inc "https://gist.githubusercontent.com/BBcan177/324e291bdf7636d34d274cc26490e764/raw")

After this exit run 16 and 11 . After this process your dashboard will be work.

dotsch

Thank you very much for the work around.
Had the same issue on 2.7.2 and it fixed it.

revengineer

I confirm, _17 went well and resolves the issue. Thank you!

Unoptanio

@revengineer

with version _17 now everything is ok we are online again

This problem made me discover the usefulness of boot environments

Active one time and reboot

slu

Is the update only available with the -devel package or will pfBlockerNG 3.2.0_8 also receive the update to _17?

Gertjan

@slu

AFAIK :
The _10 or non-devel remains stable and the same.
The devel version was upgraded, to see if all was ok and so on. If that was the case, the non devel would also be updated afterwards.
Remember : "devel" is bleeding edge technology. And sometimes there is progress, sometimes there is blood.

jrey

@slu

Just wait on a production system. there will be more. _17 still has "show stoppers"

yes you can "get around" some of them, but not all.
production wait.
installing and package testing -devel

SteveITS

To clarify for anyone finding this thread and looking for IPInfo ASN fields:

On 24.11, pfBlockerNG 3.2.0_16 does not include the IPInfo ASN token fields.

pfBlockerNG-devel 3.2.1_20 does.

Gertjan

@SteveITS said in pfBlockerNG-devel v3.2.0_15:

On 24.11, pfBlockerNG 3.2.0_16 does not include the IPInfo ASN token fields.

pfBlockerNG-devel 3.2.1_20 does.

Totally agree with this. For me, this implies :

Use pfBlockerNG-devel 3.2.1_20 - this means the latest version and thus I have to to deal with current, new issues, the old ones are gone. Chances are great the forum has very actual info and probably even a solution right now for these new issues.
When we use pfBlockerNG 3.2.0_16, will have to deal with the issues already known and solved.

So, what will it be ? _20 or version _16 ?

For me, the choice is a simple one. I've been using the 'devel' version and never regretted it