PfBlockerNG
-
I'm getting this error in the update log
===[ DNSBL Process ]================================================ Missing DNSBL stats and/or Unbound DNSBL conf file - Rebuilding -
Hi trumee,
Some of those download fails are due to cURL errors. See the messages below. Set those to "Flex".
SSL: no alternative certificate subject name matches target host name 'feeds.dshield.org'
SSL certificate problem: unable to get local issuer certificate Retry in 5 seconds…Also Dangerulez and VMX are being blocked by other Firewall Lists.
[ pfB_PRI3 - DangerRulez ] Download FAIL [ 01/03/16 20:11:47 ]
[ 188.40.39.38 ] Firewall IP block found in: [ pfB_Top_v4 | 188.40.0.0/16 ][ pfB_PRI3 - VMX ] Download FAIL [ 01/03/16 20:12:04 ]
[ 195.209.40.11 ] Firewall IP block found in: [ pfB_Top_v4 | 195.208.0.0/15 ] -
Hi I have just upgrqaded to pfsense 2.3B and am having a problem with the pfBlockerNG webserver service. The service will not start for some reason. I do get a crash report from pfsense.
@DougD:
pfSense moved from lighttpd to nginx in the beta which broke pfBNG (along with all other packages relying on lighttpd). I believe the author is working on an update.
https://forum.pfsense.org/index.php?topic=104854.0
Yes the recent changes in pfense 2.3 from Lighttpd to NGINX broke the DNSBL feature… I will be submitting a PR to fix this up soon....
-
I'm getting this error in the update log
===[ DNSBL Process ]================================================ Missing DNSBL stats and/or Unbound DNSBL conf file - RebuildingIts not an error… Its just a notice to say that its rebuilding the database. Possibly due to a "Force Reload" or re-enabling pfBlockerNG... or adding/removing a DNSBL Alias/Feeds...
-
@BBcan177, this is going to take some explaining. :) This feature affects other services, but let's just use AWS as an example.
AWS controls (among many, many others) the entire
54.240.128.0/18range, which means that all/24ranges from54.240.128.0/24-54.240.191.0/24are included. Since AWS allows others to use their servers, it's highly likely that many of those/24ranges are going to be flagged.Let's say that
128,129,140,141,142,143,144get flagged in a particular/24. As far as AWS is concerned, there's no correlation which implies that130,139or145are the same individual or group. This is especially true for CloudFront where the IP assignments mean nothing.So the entire
/24net gets blacklisted when, in actuality, for these particular subnets, the relationships between IPs on the same/24subnet is almost zero.What I'd like would be for a way to say: "Hey, go ahead and parse out something like this: https://ip-ranges.amazonaws.com/ip-ranges.json and, if the IPs are within those ranges, still blacklist them, but don't add them to the list for reputation processing."
Thoughts?
-
What I'd like would be for a way to say: "Hey, go ahead and parse out something like this: https://ip-ranges.amazonaws.com/ip-ranges.json and, if the IPs are within those ranges, still blacklist them, but don't add them to the list for reputation processing."
Hi abujammy, Its best to use the Country code exclusion for Reputation and add "USA" to the list of exclusions.
-
Wow! BBcan177. Wow.
I've been gone for such a long time, I come back and pfBlockerNG is a hit! This is so cool. I'm so glad that you stepped up and helped move this idea. Thanks to Marcello Coutinho for helping me get pfBlocker (back when it was IP blocklist and country Block) off the ground from it's first inception back when it was release 0.1.
This is absolutely awesome. And you gave throwback credit to me and Marcello Coutinho.
Well done! This is why I love the pfsense community. We all work together to make our worlds better.
-
Wow! BBcan177. Wow.
I've been gone for such a long time, I come back and pfBlockerNG is a hit! This is so cool. I'm so glad that you stepped up and helped move this idea. Thanks to Marcello Coutinho for helping me get pfBlocker (back when it was IP blocklist and country Block) off the ground from it's first inception back when it was release 0.1.
This is absolutely awesome. And you gave throwback credit to me and Marcello Coutinho.
Well done! This is why I love the pfsense community. We all work together to make our worlds better.
Thanks… Most don't realize all the effort that goes into developing and maintaining a package with an ever changing landscape... ;) welcome back...
-
Hello,
what did you prefere as blocked iplist?
did you have some web service that you know where i can buy access to some blocklist that i can insert by URL and forget it?
did you know also some of this service for Whitelist (like googlebot and similar)
tnx for your help.Peppe
-
Is it possible to block a list of dynamic IP's but only specific ports?
We get a lot of spam H.323 calls originating from AWS (185+ EC2 IP ranges) and DigitalOcean (10+ IP ranges) and others. We'd like to automate the blacklisting but only on port's 1503 and 1720.
Expert Mode Question: Most of the originator calls are named "unknown" or "cisco" and it would be great to parse those out and block those, though I'm betting that's beyond the scope of pfBlockerNG.
-
Hello,
what did you prefere as blocked iplist?
did you have some web service that you know where i can buy access to some blocklist that i can insert by URL and forget it?
did you know also some of this service for Whitelist (like googlebot and similar)
tnx for your help.Peppe
Here is link to a script to import ~50 blocklists…
https://forum.pfsense.org/index.php?topic=86212.msg549973#msg549973I think there are some Whitelists available... But I don't have those URLs myself... Google search and/or hopefully other users can share some URLs for whitelisting...
-
Is it possible to block a list of dynamic IP's but only specific ports?
We get a lot of spam H.323 calls originating from AWS (185+ EC2 IP ranges) and DigitalOcean (10+ IP ranges) and others. We'd like to automate the blacklisting but only on port's 1503 and 1720.
Expert Mode Question: Most of the originator calls are named "unknown" or "cisco" and it would be great to parse those out and block those, though I'm betting that's beyond the scope of pfBlockerNG.
You can use the "Adv. Inbound Firewall" rule settings to protect only certain ports/Dest IPs etc… I will be adding "Adv. Outbound Firewall" rule settings in the next release. You can also use "Alias" type rules, and manually create the firewall rules to suit more complex setups...
-
pfBlockcerNG IPv4-lists: Changes from script: as of 2016-01-18
Re: https://forum.pfsense.org/index.php?topic=86212.msg510369;topicseen#msg510369
After perusing the log from the CRON run for pfBlockerNG_import.php script as listed here, it appears that there are a couple changes that might reduce errors that I have documented below.
Might want to delete the "no access," "discontinued" and "not found" or change status to "off."
Cheers,
Todd
*Startlist
- Abuse_Spyeye
from: https://spyeyetracker.abuse.ch/blocklist.php?download=ipblocklist
to: discontinued
as per: https://spyeyetracker.abuse.ch/ :
SpyEye Tracker has been disconntinued. More information will follow soon on https://www.abuse.ch
Thanks for all your support!
- Snort_BL
from: https://labs.snort.org/feeds/ip-filter.blf
to: http://talosintel.com/feeds/ip-filter.blf
as per: http://blog.snort.org/2015/09/ip-blacklist-feed-has-moved-locations.html :
Wednesday, September 2, 2015
IP Blacklist feed has moved locations!
For those of you using the IP Blacklist feed on labs.snort.org, we've had to move the URL to the new link.
You can find it at the following URL: http://talosintel.com/feeds/ip-filter.blf
- Infiltrated
from: http://www.infiltrated.net/blacklisted
to: no access
as per: http://www.infiltrated.net/blacklisted
Forbidden
You don't have permission to access /blacklisted on this server.
- Geospy
from: http://www.geopsy.org/blacklist.html
to: not found
as per: http://www.geopsy.org/blacklist.html
Not Found
The requested URL /blacklist.html was not found on this server.
*Endlist
- Abuse_Spyeye
-
Is it possible to import "Easylist Germany" to "DNSBL Easylist" from AdBlock Plus into pfBlockerNG?
Easylist Germany: https://easylist.adblockplus.org/de/
-
@BBCan17
I am having trouble viewing the pfblockerNG alerts.On the main index page, I can see (for example) X packets for "pfB_NAmericav4" (I created an inbound rule/alias to block everything inbound on WAN that's not from United States).
I can see that it blocked 475 packets.
Clicking on it bring me to the alerts page, which says "Found 29 Alert Entries - Insufficient Firewall Alerts found."
Why does it only find 29 of the 475 blocked packets?
I've disabled remote logging for the moment to hopefully eliminate a variable. I've also
-disenable/re-enable pfbng
-force update
-force cron
-force reload
-clear logs (from firewall settings tab)pics below
-
I am having trouble viewing the pfblockerNG alerts.
Why does it only find 29 of the 475 blocked packets?Hi oddworld19,
The Alerts Tab takes its info from the pfSense Firewall Log. So if the Firewall log doesn't contain those Alerts, it won't show in the pfBNG Alerts Tab.
You should disable the "Log Firewall Default Block" option. They are filling your log with unneeded data. You could keep the last two "Bogons" and "Private" as those shouldn't fill your logs as much.
Then clear your firewall logs. Followed by Disable and Re-Enable of pfBlockerNG to clear the widget packet Counts and see how it goes from there.
There is a also known issue that I reported to the Devs, but haven't had a response. But that is only specific if you define Ports in the firewall rules. From your post, it doesn't look like you have this issue.
https://forum.pfsense.org/index.php?topic=99929
update:
The Widget has a customization setting to define the "Max packets for Alerts Tab pivot"… Make sure this is set to meet with your requirements.
-
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
-
@Ip:
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
Can you post a screenshot of the Alias? Did you select the "List Action" and define the "Alias" name?
-
@Ip:
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
Can you post a screenshot of the Alias? Did you select the "List Action" and define the "Alias" name?
Well, the alias name is kind of personal ;). Contains one space but no "pfBlocker" or "pfB_". List action is "Deny Both".
-
@Ip:
@Ip:
The "IPv4 Custom list" seem to be inactive in pfBlockerNG. It worked fine before. I have several IPs I want to block manually in that list but it is not working. Force update and force reload has no effect. The custom list does not appear on the dashboard either. Anyone familiar with this?
Can you post a screenshot of the Alias? Did you select the "List Action" and define the "Alias" name?
Well, the alias name is kind of personal ;). Contains one space but no "pfBlocker" or "pfB_". List action is "Deny Both".
Its probably not going to create the alias if its just a "single space" as the Alias name… Give it a proper name and it should be fine. It can't contain and special or International characters.
