pfblockerNG deny logs are empty after pfsense 2.50 upgrade
-
Hi there,
After upgradeing pfsense to 2.50. The pfblockerNG deny logs are empty. We uninstalled the package and reinstalled as well as installing the pfblockerNG-Devel package (which is a much nicer package).
Still the same, deny logs are empty. DNSBL logs are populating however
-
Use world's favourite IP for a moment.
You'll get hits for sure.
-
Is the world favourite IP a feed or a predefined feed in pfblockerNG?
-
@solte98hotmail-com said in pfblockerNG deny logs are empty after pfsense 2.50 upgrade:
Is the world favourite IP a feed or a predefined feed in pfblockerNG?
It's defined in the more serious (the opinion is mine) feeds like :
See also the source https://github.com/Sekhan/TheGreatWall
edit : the name of the feed is listed in my first image.
-
I am having this issue too, and have plenty of feeds that blocked loggable activity in 2.4.5:
https://forum.netgate.com/topic/162068/pfsense-2-5-0-and-pfblockerng-2-1-4_25-no-alert-deny-activity
-
@drewsaur said in pfblockerNG deny logs are empty after pfsense 2.50 upgrade:
and-pfblockerng-2-1-4_25-no-alert-deny-activity
Not the same.
pfBlockerNG 2.1.4_25 is very ancient ..... -
@gertjan that’s the current and recent non-devel version.
-
Still, some 2 years old.
So no one knows hat it 'looks like' any-more.This one :
is ok.
Edit : so also the Home pfSense Packages pfBlockerNG forum.
-
@gertjan it’s only a few weeks old. However, yes, the devel version is what bbcan177 recommended I move to.
-
@drewsaur said in pfblockerNG deny logs are empty after pfsense 2.50 upgrade:
it’s only a few weeks old
It was 'touched' so it could be used for 2.5.0.
Probably security issue would still be addressed. -
@gertjan this feed def gets logged in the reports/log files section.
in the test area, I am going to try some more IP feeds.
