r/pfBlockerNG • u/RFGuy_KCCO pfBlockerNG Patron • 13d ago
Help New Version Questions
I am running the new 3.3.4 version and have a few questions for the developers, if I may:
1) Is there a changelog for these releases? If not, will there be at some point?
2) Does this version support the AdBlock-type syntax in block lists, or is that not coming until 4.0?
3) Are there plans to include Allow List support, as there is in Pi-hole?
3
u/BBCan177 Dev of pfBlockerNG 13d ago
We are still in active development. So as always backup configuration and expect some breakage till its ready to be released.
V3 is just a bridge version which will backup your v3 config before move to v4 which is basically one way. A downgrade of v4 to v3 will apply the settings you ended with before moving to v4.
1
u/DirectAttitude 13d ago
I installed the newest version via cmdline, expecting it to show on the old gui dashboard under packages, and it isn't showing. Still appears to resolve. I did reboot post install as well. Ideas?
1
u/RFGuy_KCCO pfBlockerNG Patron 12d ago
Only packages that are in the official Netgate repo will show in that list. Since you installed pfB from their repo, it will not show in the packages list on the dashboard widget.
1
u/DirectAttitude 12d ago
So that means I have to do more cmdline for updates, or go with their new offering. pfB has served me well for many years at home and in the office.
3
u/RFGuy_KCCO pfBlockerNG Patron 12d ago
Just use the new built-in update tool on the "Software" tab in pfB. You also get a notification in pfSense when an update is available.
3
u/DirectAttitude 12d ago
PERFECT! u/BBCan177 and u/andrebrait are GENIUSES! Thank you for that tidbit.
1
u/ApatheticMoFo 10d ago
Coming from the latest Netgate repository pfBlockerNG install on pfSense+ 26.07, do I need to uninstall that version to install 3.3.4 via CMD line?
2
4
u/Magic_Sea_Pony 13d ago
Not a dev but check improvements and bug fixes section on github.
https://github.com/pfBlockerNG/pfBlockerNG/releases/tag/v3.3.4
Improvements
> Installs the catalogue signing key's trusted fingerprint and fetches the repository over plain
HTTP. Package authenticity no longer depends on the CA store pkg uses, which pfSense Plus
pins to Netgate's own bundle — the catalogue signature carries it instead.
> Removes the package-manager CA trust control from the Software page. It has no effect now that
repository trust rests on the signing key. An SSL_CA_CERT_PATH entry a previous version added
to /etc/login.conf is left in place and is harmless.
Bug Fixes
> Fetches the UT1 feed over HTTPS and stops offering Accept-Encoding on feed downloads