https://forum.pfsense.org/index.php?topic=137625.0

Thank you. It seems to have started working now by itself before I tried your suggestion. I can see many entries in the alerts page. I had initially configured the wrong time zone (nearly 12 hours difference) when setting up pfsense. Sometime later, I changed to my timezone. This was done after I configured pfblockerng. I think that may have caused some issue. @BBcan177: Goto the general tab and uncheck "Keep Settings", then uncheck "Enable pfBlockerNG" followed by a Save. This will wipe all previously downloaded files. Re check both boxes then Force Update. I did this now just to be sure. Its blocking fine after that.

You can't "Suppress" IPs for GeoIP blocked IPs… Create a "Whitelist" Alias in the IPv4 and/or v6 tab. Add the IPs that you want to allow into the Custom list at the bottom. Set the Action to "Permit Outbound" Goto the General tab and ensure that the "Rule Order" places the Permit rules above your Blocked rules..

Fantastic! Thank you.

Here is a URL for the MalwareBytes hpHosts feeds:    https://www.hosts-file.net/ Feed URLs here:  https://hosts-file.net/?s=Download I would not recommend to use the  hphosts.zip feed, as that is only updated once per month… There are new malicious domains added daily, and any False positive domains will not be removed for the full month....  This also applies to the hphosts-partial Feed…  So instead use the individual Feeds for DNSBL... Hope that helps!

When you see "Update not required", then the Feed that the pkg is downloading is already up to date, so there is no reason to re-download and re-process the same feed again….  It also shows the Remote and Local timestamps in the logs...

I have had poor results with that Feed… I'd disable due to the FPs in the feed...

Turn "Global logging" off… Then in the TOP20 Tab disable the Logging... Alternatively, instead of using the TOP20 tab, you can make an IPv4/6 Alias with any GeoIP combinations and configure the options as required. Click on the Blue Infoblock icons for further details.

That is a LEGEND.

Here is the PR to fix this bug… Thanks! https://github.com/pfsense/FreeBSD-ports/pull/424/files

Here is the PR to fix this bug… Thanks! https://github.com/pfsense/FreeBSD-ports/pull/424/files

Well that actually makes sense. I wasn't making the mental distinction between the IP logging vs DNS logging. Sure enough, under alerts they are there. Alerts also shows which DNSBL list it is on too which the log file doesn't appear to show. Thanks.

This is addressed in the upcoming release of the package. MaxMind contains a "Represented" list of IPs for Countries. Unfortunately, MaxMind can list IPs in a GeoIP one month, but list none for the following month. The Database doesn't contain any blank dummy data to act as a placeholder. So its safe to ignore the log message as there were no IPs listed by MaxMind for those Represented GeoIPs for this specific month. The next release will create a placeholder GeoIP file for each empty represented GeoIP.

I saw that they appeared different. Went to the rules, then floating rules, and saw what you meant, source and destination. Thank you dok.

I know this thread is 3+ months old, but I stumbled upon it and think I know what the issue was. I had stumbled upon this Reddit thread and added the WindowsTelemetry hostslist. After I added to a DNSBL feed and forced an update, DNS resolution slowed to a crawl. After removing it, forcing another update and then rebooting pfSense via CLI, everything was resolved.

The above solution was a false positive. It did not work.  I ended up removing the Host Overrides in DNS Resolver to get it working. However, ads are now appearing.  We'll, I am paying for the lower tier with ads. So I can live with it. Enjoying it ad free was nice while it lasted though.

HI BBCan.. Your link shows this: IP information 191.238.35.129 IP address 191.238.35.129 Location Boydton, Virginia, United States (US) flag Registry lacnic Is there a difference between physical IP location and GEO based lookups? Jon

Each lan segment should be able to access the DNSBL VIP via ping and browsing to the IP. There is a DNSBL permit rule option that you can select which will create a floating permit rule for the selected lan segments. Also check the NAT rules and see if there is another NAT rule that is interfering with the DNSBL NAT rules.

With this domain as an example: api.content-ad.net With TLD enabled, it will not block all sub-domains unless content-ad.net is in the blocklist, since net is the TLD. So you could add that domain to a cuatomlist and Reload for it to take effect.

if you want to use GEOIP and TOR, you can create a TOR alias and add the TOR exit node feeds. Set the Action to "Permit Outbound".  Then ensure that the Rule Order option has the permit rules above the Block/Reject rules. Firewall rules are processed top to bottom.