See pfBlocker version 3.1.0_8 was released
-
What version of pfSense was pfBlockerNG 3.1.0_8 released for? I'm still on CE 2.6.0 but pfBlockerNG 3.1.0_7 is the only version that shows to be available in package manager.
Edit: Was this another Netgate released version or was it released by the pfBlockerNG maintainer?
-
@jdeloach said in See pfBlocker version 3.1.0_8 was released:
What version of pfSense was pfBlockerNG 3.1.0_8 released for?
I'm using 22.05 (pfSense Plus) and installed that version this morning.
-
@jdeloach Looks like it was just a numbering issue between the previous Netgate release and this new update by BBCann177.
He's since change the version for 2.6 and 22.x to a .8 release.
https://www.reddit.com/r/pfblockerng/comments/zg9ipo
I've installed .8 on my main box and a test VM yesterday evening both running 22.05.
-
@cappie said in See pfBlocker version 3.1.0_8 was released:
@jdeloach Looks like it was just a numbering issue between the previous Netgate release and this new update by BBCann177.
He's since change the version for 2.6 and 22.x to a .8 release.
https://www.reddit.com/r/pfblockerng/comments/zg9ipo
I've installed .8 on my main box and a test VM yesterday evening both running 22.05.
I'm on CE 2.6 and things still show 3.1.0_7 as the only choice. In fact .0_7 only became available late last week.
I'm running on a PC with AMD64 processor using real hardware so appears that Netgate has still screwed up their configuration because we still have different version numbers for packages for folks running CE 2.6 and the Plus versions.
This is something that is not going to be easy to fix and is going to probably drive folks away due to incompatibility between versions of pfSense and the versions of installed packages. It appears that the right hand does not know what the left hand is doing.
-
Netgate has still screwed up their configuration because we still have different version numbers for packages for folks running CE 2.6 and the Plus versions.
That certainly does not strike me as the intention of Netgate nor @BBcan177. There was simply a mistake made in version numbers, which happens in other vendors software.
This is something that is not going to be easy to fix and is going to probably drive folks away due to incompatibility between versions of pfSense and the versions of installed packages. It appears that the right hand does not know what the left hand is doing.
That can be interpreted as a offhand dig at the package maintainer who's dedicated his time and effort on a package used by many and maintained by one.
With all that said, I'm sure I've seen a post in the past few days around issues with the package update database or the like. Maybe a better solution would be seeing if this is related.
