pfBlockerNG-devel v3.2.0_15
-
I confirm, _17 went well and resolves the issue. Thank you!
-
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
-
Is the update only available with the -devel package or will pfBlockerNG 3.2.0_8 also receive the update to _17?
pfSense Gold subscription
-
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. -
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 -
J jrey referenced this topic on
-
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.
-
@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
