PfBlockerNG
-
@Mr.:
Some weird stuff ???
Hey Mr. J.
You are mixing some things up here :)
The pfBlockerNGSuppress alias does not need to be referenced to any Firewall Rules.
Suppression -
Suppression process occurs when Lists are downloaded from the Threat Sources.
When a List is downloaded, if the list contains 1.2.3.4/32 and the Suppress Alias has 1.2.3.4/32, then this IP is suppressed from the Blocklist.
If a list has 1.2.3.4/32 and the Suppress Alias has 1.2.3.0/24, then this IP is suppressed from the Blocklist.
If a list has 1.2.3.4/24 and the Suppress Alias has 1.2.3.4/32, then the Single 1.2.3.4/32 is suppressed, and all of the other IPs in this Range are added to the Blocklist.
When you click on the "+" icon in the Alerts tab, it will add the IP to the Suppress Alias, and also removes the IP from the Aliastable. However, the Suppressed IP is still in the Blocklist, and will be removed from the List at the Next Cron Update for the particular List. This will prevent these Suppressed IPs from being blocked.
Whitelisting -
When you whitelist, you are creating a new pfBNG alias and typically set it for "Permit Outbound". You can enter the Whitelisted IPs in the custom Box in the alias.
The best method is to suppress the IP above. But if you have a Block occuring from a CIDR under a /24, you can't suppress that (ie /20 etc…) To overcome that, you need to allow the IP "Permit Outbound" which will create a state in the pfSense State table that allows the return of that IP without being Blocked by the pfBNG Block/Reject rules. In the Alerts Tab, you can see the List that Blocked the IP, if no IP is shown below the List, then the Block occurred by a /32 Blocklist entry. If its blocked by a CIDR, it will show the IP and CIDR below the List. You then can decide if its a /24 to use Suppression, or use the Whitelist for other CIDR ranges.
Other questions -
The Permit Rules need to be above the Block/Reject rules. Ensure that in the Alias, you set "Logging" or enable Global logging in the General Tab which will enable Logging for all Aliases globally.
When you add a manual Rule, it can't have "pfB_" in the description, these will be removed by the Cron task each hour. To create "Alias" type rules, you need to enter the Description starting with "pfb_" (Lowercase)… This is explained in detail in the Alias "List Action" Section.
You cannot Use Domain names with pfBlockerNG currently. You will need to convert the domain into an IP and add that to a Custom list. In v2.0 I will also have Domain Name Blocking (DNSBL).
You can use a service like Hurricane Electric to collect IPs for Domain names that are changing more frequently and collect the list with the "html" format.
http://bgp.he.net/search?search%5Bsearch%5D=twitter&commit=Search
http://bgp.he.net/search?search%5Bsearch%5D=facebook&commit=Search
http://bgp.he.net/search?search%5Bsearch%5D=spotify&commit=Search
http://bgp.he.net/search?search%5Bsearch%5D=dropbox&commit=Search -
@Mr.:
@Mr.:
Changing to http worked, BB; Juniper updated :-*
Weird that Firefox does not complain about it, but pfBlockerNG does(?)
The difference is that the browser handles the Certs a little different then the "fetch" shell FreeBSD command. Here is a link… Maybe one of the pfSense Devs will chime in on this issue?
Thanks BB. That links says it'll be fixed by updating OpenSSL. Such a thing is 'core maintenance', not a bug that needs to be fixed, no(?)
yes that what I was saying… The fetch command uses OpenSSL as part of pfSense. So that issue is a core pfSense issue and not from pfBlockerNG.
-
Is there a comprehensive guide that covers the main features of the current version? I want to use it mainly to block ads
-
You can use a service like Hurricane Electric to collect IPs for Domain names that are changing more frequently and collect the list with the "html" format.
http://bgp.he.net/search?search%5Bsearch%5D=twitter&commit=Search
http://bgp.he.net/search?search%5Bsearch%5D=facebook&commit=Search
http://bgp.he.net/search?search%5Bsearch%5D=spotify&commit=Search
http://bgp.he.net/search?search%5Bsearch%5D=dropbox&commit=SearchFantastic… these hidden features/hacks that should be in a pfBNG FAQ or OP or something.
-
I was waiting the pfBlockerNG new version to do adblock using the unbound, but until it's released I add a VIRTUAL IP to the Lan interface, made a script to convert http://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&mimetype=plaintext to unbound advanced rules to redirect to the VIRTUAL IP and setup a nginx to listen to both 80 and 443 on the VIRTUAL IP and respond to all with "204 No Content". For my surprise is working better that I was expecting.
-
Is there anyway to EXclude an ip from the pfblocker? I have a PS4 and when I have the top 20 countries selected it affects game play online and when i disable it doesn't block some of the ads. So is there anyway to exclude an IP address?
-
Is there anyway to EXclude an ip from the pfblocker? I have a PS4 and when I have the top 20 countries selected it affects game play online and when i disable it doesn't block some of the ads. So is there anyway to exclude an IP address?
There is a post about this five posts before this one! And also in several places in this thread… Either Suppress the IP (/32 or /24 Ranges only) or Create a Permit Outbound Alias with the IP listed in the Custom Input Entry. Ensure the Permit Rule is before the Block/Reject Rules.
-
Is there anyway to EXclude an ip from the pfblocker? I have a PS4 and when I have the top 20 countries selected it affects game play online and when i disable it doesn't block some of the ads. So is there anyway to exclude an IP address?
There is a post about this five posts before this one! And also in several places in this thread… Either Suppress the IP (/32 or /24 Ranges only) or Create a Permit Outbound Alias with the IP listed in the Custom Input Entry. Ensure the Permit Rule is before the Block/Reject Rules.
Woah… sorry to push a button there. I actually tried setting it up with the permit rules before the block/reject but then it wouldnt block anything. Just thought there might be an easier solution.... Ill try the suppressing... thanks!
-
If it's a Top20 Block, then you have to use the "Permit Outbound" method, as suppression will only work on /32 or /24 ranges. In the alias enter just the IP range required and set it to "permit outbound". It shouldn't interfere with other block/reject rules.
-
Hello BBcan177,
If pfblockerng integrate with mailreport in the future? For example, I add "botnet" alias and set action to deny outbound. When infiltrated computers traffic is outbound, and send mail trigger by mailreport(Report Logs).
But I can only use firewall log (raw) filter in report Logs,so i can't filter by botnet alias
Or I can use other methods?
Thanks!
-
Does pfBlockerNG support 2.1.5? or should i just stick to pfBlocker?
Thanks
-
It does not unless you use an unofficiel package repository :)
-
NEVERMIND: I was able to get this resolved from help on IRC. It looks like, despite running the php cleanup script, I had some original pfBlocker aliases still around. Deleting them fixed the problem.
I'm a bit new to pfsense and not a network guy. I implemented PFBlockerNG and, overall it seems to be working well. The problem is that I am getting the errors shown in the attachment. I used the php script earlier to set the lists up. Not sure how to resolve these. Any suggestions would be appreciated.
-
It does not unless you use an unofficiel package repository :)
Hi,
can you please give us more details how to install PFBlockerNG in 2.1.5
thank you
-
Well, you don't. Simple.
-
Update to 2.2+ and it will work fine. If you haven't you need to. Keeping your software up to date is part of security. Skip 5 or 6 versions and the updates become more difficult.
-
pfBlockerNG had support for 2.1.x. but the current version only supports 2.2 and above. Sorry about that.
-
Hello BBcan177,
If pfblockerng integrate with mailreport in the future? For example, I add "botnet" alias and set action to deny outbound. When infiltrated computers traffic is outbound, and send mail trigger by mailreport(Report Logs).
But I can only use firewall log (raw) filter in report Logs,so i can't filter by botnet alias
Or I can use other methods?
Thanks!
Hi ntct,
You can try the following :
View the Firewall or pfBNG Alerts log and find the Rule Number associated with the Alias. If you don't see the rule number in the Firewall logs, you can edit the log settings to display the Rule column.
In mail reports, when you select "Filter Logs (Raw), enter the "filter" as - Example rule number 90 :
90,
This will search the log for those characters. Please note that any Firewall rule changes can alter the Rule Number.
Hope this helps.
-
Hello
Issue
Fatal error: Call to undefined function subnetv6_expand() in /etc/inc/util.inc on line 714Fix in this thread works
-
Hi stanthewizard,
Are you using the latest version of pfBNG? If not, please upgrade as that issue has been fixed.
