PfBlockerNG
-
Would be much better to post the content of the failing lists or link to them. As for the Spyeye thing, Http/1.1 Service Unavailable is definitely not pfBNG issue.
-
Hi Mr. J.
Did I ever say that i really hate IBlock… I think every so often they have an issue with some of their mirrors and there is some malformed data in one of those lists. The mirrors that I use don't seem to have this issue. What would really help is getting a copy of the original downloaded files.
The files are in /var/db/pfblockerng/original
What i would need are the IBlock .gz and .orig files for these fails lists. Also a copy of the
/var/db/pfblockerng/masterfile
If you can send those to my email which is listed in the 'General' tab, I could take a look at it. Or put it in a dropbox or similar cloud storage and pm me the link.
After you copy those files, Try to run a "Force Reload" and see if that clears it. If not, Disable pfBlockerNG and Disable "Keep Settings" and run a "Force Update".... If it still doesn't clear it, disable the 'State' of those IBlock Lists and try the above process again without those Lists.
-
Would be much better to post the content of the failing lists or link to them. As for the Spyeye thing, Http/1.1 Service Unavailable is definitely not pfBNG issue.
Yes Abuse Spyeye seems to be down… Should disable the 'State' for now....
There also seems to be an issue with a few SSL sites (Juniper and dShield). When using https, the fetch command is getting some ssl errors which seem to be related to OpenSSL in pfSense.
-
HI, Guys
I'm noob to pfSense and pfBlokerNG, I have set up all the country block rules (e.g pfb_Europe_v4) in the floating rules tab, the rule order is pfSense Pass/match+pfbPass/Match+pfbBlock/Reject, I then set up a floating rule on the TOP of all other rules, to permits one of the LAN IPs to access WAN without being blocked by the country rules or blocked by SNORT:
Action: Pass
Quick: Ticked
Interface: LAN
Direction: any
TCP/IP version: IPv4
Protocol: any
Source: Type: Single hosts or alias
Address: AndroidMediaBox, which is a IP alias, 192.168.1.xxx
Destination: Wan netbut I can still see bunch of source ip (192.168.1.xxx, AndroidMediaBox) appeared at pfBlockNG Alerts tab as well as at the System logs/Firewall tab, that were blocked by the country rule (pfb_Europe_v4), Proto: UDP, CC: CH
I'm sure I'm doing something wrong, but can't figure it out, so need some helps to fix the issue. Thanks.
-
Hi pfcode,
Its best to make a new pfBlockerNG alias called "Whitelist". Add any IPs that you want to access (these are the destination IPs, not the local LAN IP) in the custom entry box at the bottom of the Whitelist Alias. Set the "List Action" to "Permit Outbound".
The rule order setting should ensure the this "Permit" rule is above the "Block" rules.
-
Hi pfcode,
Its best to make a new pfBlockerNG alias called "Whitelist". Add any IPs that you want to access (these are the destination IPs, not the local LAN IP) in the custom entry box at the bottom of the Whitelist Alias. Set the "List Action" to "Permit Outbound".
The rule order setting should ensure the this "Permit" rule is above the "Block" rules.
Hi, BB
Thanks for the answer and suggestion, Yes, I was using pfBlockerNG Whitelist alias but gave up later, because there were so many Apps installed on that Android Media Box, P2P TV, IPTV app, …, so adding destination IPs in the custom entry box is PITA, tons of different IPs.
My concern is why the rule I put on the top of the floating rule doesn't work properly.
-
Hello all, long time lurker, first time poster
Got a few noob questions in regards to pfblockerNG. Only other packages i've installed are snort and ntopng. Everything is working well with pfblockerNG except suppression and allowing traffic to pass. For example, a list that I'm currently using (http://list.iblocklist.com/?list=ijfqtofzixtwayqovmxn&fileformat=p2p&archiveformat=gz) is blocking Facebook. I see entries in the Alerts that relate to Facebook, so i clicked on the + to add it to the suppression list.
Here's a screentshot of the specific IP address:
The Ip address shows up in the suppression list that pfblocker creates:
Without the list enabled, I am able to access Facebook no problem (with snort running on WAN with plenty of ET rules). However, with this list enabled, i find that suppression is not working. Am i doing something wrong?
Also, on a related note, i'm trying to allow "akamaitechnologies" (most likely, content hoster for Facebook) pass through my lists; suppression is not working as there's many servers/hostnames that i cannot keep adding as they constantly change, including the port numbers. How can i allow all this type of traffic to pass? see screenshot below:
thanks for any help!
-
My concern is why the rule I put on the top of the floating rule doesn't work properly.
Rule looks ok. Try to clear the firewall logs and clear the Firewall State table.
-
Hello all, long time lurker, first time poster
Hi cassius, I would not recommend those two IBlock lists. They have too many false positives. I wrote a script which was posted in the thread by doktornotor a few posts back which has better Blocklists than these from IBlock.
Also you can only use "Suppression" for a /24 or /32 Block… Take a look at the Alerts Tab and underneath the List column, will show the IP and CIDR of the Block. Hover over the list column, and you will get a "Popup" Description on how to Whitelist IPs.
-
I use a custom ipv4 list ( /var/db/pfblockerng/spammers.txt ) with 1200+ address listed like such: 212.71.238.0/24 and it appears that sometimes pfblockerng misses blocking some of the address in the list. It seems it doesn't block any /16 ranges either. Every morning I discover some duplicate spam addresses and find that I already entered them in the custom list. When this happens I also enter the address into the IPv4 Custom Address(es) section at the bottom, hit save, then update > full reload. I'm concerned that the size of the custom list might cause problems because it is stored as 'Base64' format. I think the old version worked with the /16 /20 /24, etc. ranges and they were blocked. Is there anywhere I might look at to ensure that the spammers.txt file is consumed and acted upon correctly? Thank you.
-
I may start my own thread, but I'll give my experience.
I'm newer to pfsense.
I had pfBlockerNG setup and working great. Site had a power outage and after pfsense came back online, nothing would route / talk to the outside world. Firewall Logs showed no blocking. If I disabled pfBlocker (tick box), everything started working perfectly.
Not sure what to think.
Any advice on approaching this to diagnose it? -
Site had a power outage and after pfsense came back online, nothing would route / talk to the outside world. Firewall Logs showed no blocking.
- Reinstall
- Restore configuration backup
- Get UPS
-
Try a "Force Reload". If that has issues, then uncheck "keep settings" in the general tab, then disable pfBlockerNG. This should clear all of the downloaded files. Then re-check "keep", re-enable pfBlockerNG and run a "Force Update".
-
Hello!
Trying to (re)install pfBlockerNG from scratch - but the package does not appear in the package manager…? Any ideas?
Thanks!
-
If you have it installed it won't appear in the "Available" tab as its already installed… You can goto "Installed Packages" Tab and click the "Pkg" Icon for pfBNG...
-
If you have it installed it won't appear in the "Available" tab as its already installed… You can goto "Installed Packages" Tab and click the "Pkg" Icon for pfBNG...
Very odd - I uninstalled it and it confirmed uninstallation, removed it from the installed package view but then I did not think to refresh the page… I just so happened to click on the installed package list and lo-and-behold, it was still there!
Uninstalled it again... Reinstalled - now all appears to be well!
-
My Alerts -> Auto-Resolve quit auto-resolving a bit back.
It's a small thing among pfBlockerNG greatness, yet I miss it.IPs are still resolving in the Firewall logs when I click !. That seems a good sign.
What I tried:
I've reviewed pfBlockerNG settings and don't see anything amiss.
I've tried adjusting interfaces and other options in the DNS resolver
I've tried telling pfSense to only use the DNS servers listed in General
I've reinstalled pfBlocker package.What I have:
pfSense 2.2.2 x64 running on a Dell quad core Xeon w/ 4GB RAM
Lots of lists in pfBlockerNG, some really large.
Also running Snort, Squid3+SquidguardAny thoughts anyone?
Appreciated. -
How long is your alert list?
-
How long is your alert list?
Dang. You've hit on it.
I had tried with different deny sizes - between 30 and 100 but I always left the Match at 30.
After your reply I set match to 0 and deny to 30 and it works again.Thanks dude!
-
pfBlockerNG v1.09 Release Notes:
-
Several under-the-hood code changes.
-
Added a 'Cron Interval' setting in the 'General' Tab. Previously Cron would run each hour.
-
Added function to check if the Cron task has changed, and only update if required (reduce config backups)
-
The 'Update Tab' uses the new Cron Interval setting to show the Next Cron task and Time remaining.
-
Improved the logging to the pfblockerng.log (Reduce empty lines and some other tweaks)
-
The parsing of IPs on downloads has been adjusted to remove the '/32' CIDRs (and leave just the IP address). Also parse for Ranges before parsing for CIDR or Single IP addresses.
Next release will move away from a Regex Style function to a faster, more efficient string functions. -
Input Validation has been added to the IPv4/6 Tabs. Unfortunately, if there is an error, it doesn't save the last inputted settings, and you will need to re-enter all of the input data.
-
GUI changes to combine like-fields together. ie - 'General' Tab, Inbound Ports options, and the Continent pages now have the IPv4/6 Tables side-by-side.
-
Added ability to move Aliases in the IPv4/6 Tabs. 'Click+hold' and move the Alias to any line position required.
-
Widget has been overhauled to make it more efficient. Added 'Wrench Icon' which will allow for some customization's.
-
Widget now allows pivoting from the Packet Count column to the Alerts Tab, and it will load the approproate filters to show the associated Alerts. Please note that if the the pfSense Firewall Log has been cleared, old Alerts will not show in the 'Alerts Tab'.
Also added an 'Advanced' Inbound Firewall Rules Settings':
This will allow you to create pfSense 'Port' and 'Destination' Aliases which can be used with the Auto-Rules created by pfBlockerNG.
Since pfSense is a stateful firewall by design, a 'Deny Inbound' or 'Deny Both' will create an Inbound rule in the WAN Firewall Rules tab. Previously it will log Alerts for Packets that are already being blocked by the pfSense Default implicit Deny rule.
This new feature will allow fine-tuning of the Inbound Rules to Alert only on the Open Ports that you have configured in these new settings. If you require a more complicated rule, please continue to use the 'Alias Type' Rules instead.
Here is a screenshot, showing some Port and Destination Aliases.
NOTE: Please DO NOT use "pfB_" or 'pfb_' in the start of the Alias name!!For the IP aliases, please use the "IP Network Type" alias.
Screenshot showing the Adv. Inbound Settings using the pfSense Aliases created above:
Screenshot showing the Auto-Created Firewall rules using the pfSense Aliases:
-
