@monaco said in DNSBL fail - pfblockerNG:
https://raw.githubusercontent.com/RPiList/specials/master/Blocklisten/pornblock3
the following error:
[ DNSBL FAIL ] [ Skipping : pornblock3 ]
[1614168721] unbound-checkconf[22123:0] error: local-data in redirect zone must reside at top of zone, not at m.www.localhost 60 IN A X.X.10.X
[1614168721] unbound-checkconf[22123:0] fatal error: failed local-zone, local-data configuration
Is it possibly because of this entry:
m.www.localhost
Yes you can't add localhost TLD in a blocklist as you have that TLD already defined in Unboubd abd hence the error:
"local-data in redirect zone must reside at top of zone"
Seems like they removed that domain from that Feed.
@ronpfs said in pfblockerng crash report:
@fireodo The problem occurred when Unbound restart after WAN was toggling.
I stop Firewall service, that stopped all tail_pfb processes. Start Firewall service.
I have also toggled the WAN and there was no problem.
@mariusghita see/read other threads first - the ones from yesterday (March first). They were closed with a 'a solution is coming'.
This morning/night, the issue was corrected.
Upgrade to 3.0.0_14.
@cjbujold
Ok found the issue
Edit file: /usr/local/pkg/pfblockerng/pfblockerng.inc
Reference:
https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L2489
From:
$s_info6 = str_replace(' A ', ' AAAA ::/0', $s_info);
To:
$s_info6 = str_replace(' A ', ' AAAA ::', $s_info);
Will get this fixed asap.
Submitted PR here:
v3.0.0_13
https://github.com/pfsense/FreeBSD-ports/pull/1049/files
@bbcan177 said in pfBlockerNG-devel v3.0.0_11:
@fireodo said in pfBlockerNG-devel v3.0.0_11:
BTW: after update unbound has to be started manually.
See here:
https://redmine.pfsense.org/issues/11398
Aha! - thanks
@teamits said in pfBlockerNG-devel v3.0.0_10:
/usr/local/www/pfblockerng/pfblockerng_alerts.php:160
Comment out that line #160, by prefixing "//" to it (without the quotes). Will get that fixed in next version.
@ronpfs said in pfBlockerNG-devel 3.0.0_10 won't uninstall:
@smoothrunnings What version of pfsense? There was a "fix" to install unbound 1.13.1 Unbound crashes periodically with signal 11
Version 2.5.0-RELEASE (amd64)
built on Tue Feb 16 08:56:29 EST 2021
FreeBSD 12.2-STABLE
Currently system is on the latest version.
@ronpfs a pleasure.
In your example there is a date, the missing data is the year.
Feb 23 17:19:24 pfSense filterlog: 9,,,1000000103,xl0,match,block,in,4,0x0
@mhab12 said in No pfBlockerNG alerts after update to 2102:
Perhaps the log file locations are different after update to pfS+/2102?
The file format changed, 2.5.0 is not using clog.
@BBcan177
Well, did a clean reinstall today and - Unbound python mode love is back !
What was it ? No clue, suspect that package updates did not worked well after 2.5.0. upgrade.
Thanks all !
@beachbum2021 Often when the count is wrong, it is because you have identical Header/Label names.
I can't tell much without more information on your setup.
@gertjan
Is it possible to redirect blacklisted domains to a chose website ? (So, other than the internal 10.10.10.1 from pfblockerNG/pfsense appliance)
Before, I used adguardHome which redirected every BL to a pixelserv-tls website. And it worked well, I'd like to reproduce this setup.
