@provels - Hi, I am running pfBlockerNG (v. 2.1.4_20). I don't use DNSBL, just the IPs. I started readding the blocklist IPs (e.g., BinaryDefense, EmergingThreats, firehol Level 1 to 3) and they now work.

Hi guys, I came back again and unbound is now working. Thanks for all of your replies.

Ok Thanks for all the help John.

I was not aware of the role of the .orig files. I tried clearing both (AfunList.orig from /var/db/pfblockerng/dnsblorig and AfunList.txt in /var/db/pfblockerng/dnsbl) and then force updating DNSBL. Both the orig and txt files were regenerated from the list feed As far as I can tell, the feed is correctly synced. @RonpfS said in pfBlockerNG rule download failure log entry- false positive?: Can you access the URL for AfunList in a browser? Yes. So I'm not sure why the log is reporting an error

@NollipfSense Good deal. Package probably didn't completely reinstall when you upgraded. If you install the daily snapshots now, it will go a lot faster as it just installs the update without package reinstalls (like 5 minutes total).

@Qinn Looks like it, at least for the present.

@Qinn If you see the line about "MaxMind last updated..." Then there is no failed download errors. Otherwise, you have more than 4 failed downloads, and you need to scroll the widget window down to see the last event and there should be the trashcan icon. Going from memory on this one.

@jahonix said in Rules ordering not working: @pftdm007 said in Rules ordering not working: I am using floating rules to make rules ordering easier for me. Please indicate if this is a problem. Not a problem if you consider this: Floating Rules notes Floating rules without quick set process as “last match wins” instead of “first match wins”. Therefore, if a floating rule is set without quick and a packet matches that rule, then it also matches a later rule, the later rule will be used. This is the opposite of the other tab rules (groups, interfaces) and rules with quick set which stop processing as soon as a match is made. See Floating Rules for more details on how floating rules operate. OK I read the pfsense documentation and get a better idea. Now I see that there is a ckeckbox called "Quick" in the rules. All of my floating rules ghave this box ticked. So from the documentation: "Apply filtering in a “last match wins” way rather than “first match wins” (quick)" I take that the first match will win. But first (or last) based on what? The rules ordering in pfblocker???

@provels @kiokoman I increased it 1600000. And It solved Thanks a lot! I wonder how this value calculated Thanks

Turns out uninstall/install looked like it kept the settings but it subtly changed the alias names for a custom alias from "pfB_GeoIPUSv4" to "pfB_GeoIPUSv4_v4" which broke several NAT rules. Error reported by pfSense for the rule was: Unresolvable source alias 'pfB_GeoIPUSv4' for rule ____ Editing the NAT rule and saving without changes corrected it. The NAT rule itself had the new name already, but the old name was being flagged as not resolving because the old name was still used in the matching firewall rule (the two were different).

Much thanks to all who jumped in on this...! I was able to install the pfBlockerNG package today 2.2.5_28. Things are running well.

The update is live now.

Thanks for the quick reply. I read the post before but I did not realize that it will cause this kind of error in pfBlocker.

system, advanced, firewall & nat

@TFTQKX said in NextDNS DNS filtering: It is free as of now. Check out https://nextdns.io/pricing : 300 K requests a month is peanuts .... It might be worth it - can't tell .... but it will not be "free" (for me).

Thanks, From my understanding, that only blocks sub-domains. So if it were "culture.vox.com", then the TLD would enforce that. I'm looking to go in the other direction of blocking URL's following the domain. Like "vox.com/culture"... I could be wrong... of course. Thanks, Steven

You can find which domain is whitlisted in pfblockernG.log [ EasyList_Privacy ] Downloading update [ 12/28/19 23:18:22 ] .. 200 OK. Whitelist: collector-cdn.github.com|csi.gstatic.com|metric.gstatic.com|s.youtube.com|s2.youtube.com| ---------------------------------------------------------------------- Orig. Unique # Dups # White # TOP1M Final ---------------------------------------------------------------------- 2994 2992 191 5 0 2796 ---------------------------------------------------------------------- IPv4 count=1

@johnpoz said in Database GeoIP [ GeoIP.Dat ] not found. Reputation function terminated.: Even if I knew - I wouldn't to be honest.. Anything that helps someone stay on of EOL product is counter productive.. You should of moved off 2.3.x two years ago when it was announced it was going to be EOL in a year, etc. Ok, agree with You. :) Try to shift pfSense to another server as fast as possible.