Excellent !!! Cant wait for that ;) Your a star!!

Great work!! Looking forward to the new IP block lists  :)

Thank you for your post ;) Always good to block windows ;)

Check the  pfblockerng.log  for details. You can try to clear out all the previously downloaded feeds: Uncheck - Enable pfBlockerNG Uncheck - Keep Settings Save Then check both checkboxes Force Update

Awesome thanks for the very detailed and easy to understand explanation! Keep up the good work!!

@BBcan177: They 80 and 443 are forwarded to my nextcloud server and 443 UDP to my openVPN server. For this Permit Inbound you should define a new alias with the two destination IPs of those two servers. I would assume that they are static since you have port forwards in place? If you wanted to control the outbound that is defined in the permit outbound firewall rule settings, so it can be defined as required. Did you run a Force update after the changes? Did you enable floating rules? Is so, it would be placed in the floating rule tab. I didn't enable floating rules but didn't realized I need to run a Forced update.  After the update the rule was there. So I have now prevented anyone outside the US from gaining access to my nextcloud and openVPN servers as this rule is above my default WAN: block IPv4 and IPv6 rules.  Thanks for your help, and patience. [image: pfBlockerAmericaRule.jpg] [image: pfBlockerAmericaRule.jpg_thumb]

@justsomeguy6575: Makes sense. Thanks for the explanation and all the work you put into this. am I correct in assuming it's not possible to block say github.com/gentilkiwi/mimikatz/releases/download/2.0.0-alpha-20141213/ but not block github.com itself? No DNS Filtering (DNSBL) will block the full domain or sub-domain DNS resolution… You would have to use a Proxy to filter by a URL.

worked ty

If I read the thread so far correctly, you are in a position that you have added DNS blackholes for facebook.com and google.com, but are unhappy that the domain fbcdn.net and traffic to facebook's IP space are not blocked when you expected them to be. The behaviour you're seeing is correct for the configuration you have so far, if you want other domains blocked (like fbcdn.net) then you need to block them in your list as you have done for the other domains.  Many other domains for both facebook and google will also not be blocked (for example youtube.com even though it is part of google). Even when you block the DNS request pfSense will not stop traffic going to IP addresses directly (for example pinging 31.13.70.7 would still work).  To block traffic entirely you would need to add their domain/AS numbers to IP4 & IP6 lists (Google are AS15169 and facebook are AS32934) and tick the 'domain/AS' box.  I can't remember if you need to include AS prefix as part of the number or not, I'm sure someone will be able to confirm that for you.

Did you enable the "DNSBL Permit Rule" option?  If not, enable that and select all of the LAN Subnets in the select box that need to access the DNSBL VIP. This will create a floating permit rule which will allow those other subnets. Floating rules are processed first, followed by the other Interface Rules. Rules are also processed Top to Bottom. You don't need those two other NAT Port forward rules.

@bartkowski: Or the RAW format https://gist.githubusercontent.com/BBcan177/4a8bf37c131be4803cb2/raw/396eb85f00418569cd5e82f71b9d96275163d970/MS-2 Best to use the RAW format. Keep in mind that you need to remove the last part of the Gist URL or you will not download any further commits to the Gist. Here is the URL that can be used in the package: https://gist.githubusercontent.com/BBcan177/4a8bf37c131be4803cb2/raw

Thank you for the link and explanation.

You can add this to the IPv4 and v6 tabs as required and it should pull in the respective IP addresses. It will pull all the IPs into one alias. The domain names will not be parsed tho.

When you click on the suppression icon, pfBlockerNG will Whitelist the domain and it's CNAMEs.  8) I you do the suppression directly in the DNSBL Whitelist, you have to find the CNAMEs and add them to the list.  ;)

Thanks.  That might have something to do with it.  I think the log entries that refer to the number of entries added/deleted refer to the alias files?  Even if the permit file is deleted upon saving the config, it wasn't clear to me that the corresponding entries would be removed from the alias file until the force update was run.  Therefore I would have expected the log nevertheless to show the number of entries being deleted. I've excerpted the relevant log entries below.  In this example, I disabled Switzerland and enabled Japan in one step, saved, then ran force update.  You can see that there is no reference to deleted entries, and the "last updated list summary" still refers to Switzerland (though it's been properly removed from the other sections). Thanks. **Saving configuration [ 05/12/17 10:13:15 ] ... [ Removing List(s) : InboundPermCH ] Archiving Aliastable folder Archiving selected pfBlockerNG files. **Saving configuration [ 05/12/17 10:15:38 ] ... UPDATE PROCESS START [ 05/12/17 10:15:55 ] ... ===[  IPv4 Process  ]================================================= ... [ InboundPermGB ] Reload [ 05/12/17 10:18:32 ] . completed .. [ InboundPermJP ] Downloading update [ 05/12/17 10:18:35 ] .. completed .. ... ===[  Aliastables / Rules  ]========================================== No changes to Firewall rules, skipping Filter Reload ... Updating: pfB_iBlockList 64 addresses added.11 addresses deleted. Updating: pfB_Inbound_permit 4583 addresses added. Archiving Aliastable folder Archiving selected pfBlockerNG files. ===[ FINAL Processing ]=====================================   [ Original IP count  ]  [ 490720 ]   [ Final IP Count  ]  [ 432383 ] ===[ Permit List IP Counts ]=========================   22599 total   18016 /var/db/pfblockerng/permit/InboundPermGB.txt     4583 /var/db/pfblockerng/permit/InboundPermJP.txt ... ====================[ Last Updated List Summary ]============== ... May 12 00:17 InboundPermGB May 12 00:17 InboundPermCH May 12 10:18 InboundPermJP =============================================================== .. Alias table IP Counts -----------------------------   545732 total ...   22599 /var/db/aliastables/pfB_Inbound_permit.txt ... UPDATE PROCESS ENDED [ 05/12/17 10:20:18 ]

If it can help, you need to select the List action "Alias Permit" to prevent auto rule creation - I had the same issue as above.

The pfSense Max Table entries is a table setting for all aliastables in total… grep -c ^ /var/db/aliastables/*.txt And it usually needs about 30% more…

Yes I understand this however, I'm going to be turning on "both" not just "inbound" on the FW.  I'm easing my way into blocking country outbound SO I need to enabled GEO IP Block. I haven't quite figured out what was going on BUT it's possible this was a SNORT issue or perhaps a DNS resolution issue at the time. This might be a non-issue.  I've turned pfbng back on, have cleaned a few things up and it seems like all is well. Thanks for your feedback.

There aren't many IPv6 Feeds: https://www.spamhaus.org/drop/dropv6.txt https://www.myip.ms/files/blacklist/csf/latest_blacklist.txt Choose one of the following (recommend the first one): https://www.stopforumspam.com/downloads/listed_ip_30_ipv6.zip https://www.stopforumspam.com/downloads/listed_ip_1_ipv6.zip https://www.stopforumspam.com/downloads/listed_ip_7_ipv6.zip https://www.stopforumspam.com/downloads/listed_ip_90_ipv6.zip https://www.stopforumspam.com/downloads/listed_ip_180_ipv6.zip https://www.stopforumspam.com/downloads/listed_ip_365_ipv6.zip Note: v2.1.1_8 has an issue with IPv6 lists, use "Alias Type" settings until the next release.

Hey, so I ran into this a while ago… Went through and white listed all sorts of domains that amazon wanted me to let through. I honestly think it's an issue with their app.  If you keep white listing, you'll eventually find that they are serving ads from 3rd party sites as well. It ends up being a pretty big rabbit hole. Unfortunately i ended up giving up, i just go to amazon in Chrome with all the sites still blocked, and have no issues. I think the Amazon app doesn't know how to deal with not being able to get to a site. Where Chrome just moves on...