PfBlockerNG
-
Hey guys, just wondering if something is wrong or if this is supposed to happen.
I'm using 5 of the aliases from BBcan's import script. I'm denying incoming (3 selected ports) and all outgoing using floating rules.
After a few days I have thousands of packets listed against a couple of the aliases and hundreds against the others. However in my firewall logs I only have 7 events (all outgoing).
All floating rules are set to log and the global logging setting in PFblocker is set to on as well.
I realise I only want limited firewall events to be able to sift through easily but I would have thought there would be a few more?
-
Hello guys, I am looking for some insight as to what the heck I am doing wrong here.
I have rules.
I have pfblockerNG.
I need a rule above the block rules so I move it on top.Everything is fine until CRON runs then it moves my rule below the pfblockerNG rules.
I would suggest to have a look at 'Rule Order' at the 'General' tab and think about it for a while…
unfortunately, The rule order is not very helpful. For example, I have a mail filter that I want to allow all inbound traffic. On another vlan I have a web server that I want pfblocker to block all the inbound traffic to. None of the "rule order" allow for that to happen. I need to custom sort my rules. If it reloads the order, It blocks inbound legit email.
-
Yeah, so if you need to custom sort your rules, then use the aliases. The package unfortunately lacks artificial intelligence to recognize what custom order your need.
-
Is there any ETA on the pfBlockerNg 2.0? Very interested in the possible ad blocking feature.
-
Well I think it's almost done.
-
Yeah, so if you need to custom sort your rules, then use the aliases. The package unfortunately lacks artificial intelligence to recognize what custom order your need.
+1 on this. Works Great!
-
I'm also looking forward to 2.0… There is a definite need here.
1. SquidGuard kills my Squid3 for some reason (<-- Edit, I actually got this working, which is nice).
2. DansGuardian is broken/repricated
3. E2Guardian is problematic, even when manually installedHowever, my pfBlockerNG works perfectly... Just want more. :)
Jason Bottjen
-
Here is an update on pfBlockerNG v2.0 w/DNSBL
https://forum.pfsense.org/index.php?topic=102470.0
-
Hello guys, I am looking for some insight as to what the heck I am doing wrong here.
I have rules.
I have pfblockerNG.
I need a rule above the block rules so I move it on top.Everything is fine until CRON runs then it moves my rule below the pfblockerNG rules.
I would suggest to have a look at 'Rule Order' at the 'General' tab and think about it for a while…
unfortunately, The rule order is not very helpful. For example, I have a mail filter that I want to allow all inbound traffic. On another vlan I have a web server that I want pfblocker to block all the inbound traffic to. None of the "rule order" allow for that to happen. I need to custom sort my rules. If it reloads the order, It blocks inbound legit email.
Change pfb rules to aliases and you can put them in any order you want
-
Hello, everyone i have one problem. i have installed pfblockerNG and setup IPv4 Alias/List Configuration to create IPv4 Lists (example source: http://list.iblocklist.com/?list=xshktygkujudfnjfioro&fileformat=p2p&archiveformat=gz).But this rule block the important website (like Hotmail or other website). i don't want to delete this list. i have any other method?(like whitelist but i don't know how to do).
-
pfBlockerNG is now version 2. You should go here: https://forum.pfsense.org/index.php?topic=102470.0
-
Somtimes the reporting of the Alerts misses the list matching! I had this problem today.
List 1 - Alias_Deny (De-Duplication enabled)
List 2 - Alias_NativeInterface 1
Block List 1The IP1 is in both lists, because Alias_Native does not passes by the De-Duplication process.
I had a hit on Interface 1 of IP1 and in the alert tab appeared the information that the hit is from List 2 (that does not even appears on the Interface)
Thank You all
-
Apologies as I'm new at this and I've read this full thread but am still not quite clear on the following …
I have created Deny Outbound rules on my interfaces (auto-rules) with no problems. Now I want to create rules to restrict inbound access to open ports. I understand I can do this a couple of ways (1) block country access to an alias containing the open ports, or (2) I could create a "permit inbound" rule with whitelisted countries to specific ports and destination IPs (and drop the normal PFsense NAT rules which currently allow anyone to access open ports).
However, I can't quite figure out how to physically implement either of these options. When I try to create the permit inbound rule (for example, with selected countries in North America), it creates the inbound rule but my prior deny outbound rule disappears. It seems that when I change my selections in pfB and save, it overwrites and replaces any prior rules created. I figure it must be something simple I'm doing wrong but I don't know what and can't seem to be able to create multiple different rules based on the same country list (with perhaps different selected countries from that list, for each of the rules)?
The only way I can almost do what I want is if I create all my rules as "Deny Both" and then in the advanced inbound rules, I list the alias for the open ports and the protocol(s). This has two problems though: I think I'm better to permit a small number of countries in rather than block a huge number of countries; and, I want fewer countries allowed in than I want to be able to go to on the outbound (I visit websites countries that have no need to access open ports). Doing it this way, the same country list is used both outbound and inbound.
Thanks
-
However, I can't quite figure out how to physically implement either of these options.
Hi rantech,
If you want to customize the rules, create a new Alias and in the "Source" field, add each of the Countries that you want to include in the Alias. Then manually create rules in the Firewall that references this Alias.
Please see the following links:
https://forum.pfsense.org/index.php?topic=102071.0
https://forum.pfsense.org/index.php?topic=86212.msg548324#msg548324
https://forum.pfsense.org/index.php?topic=86212.msg553921#msg553921 -
Is it possible to create two different alias from the same country list, one for inbound and a different one for outbound? Both that are logged and updated by pfB?
I think I would create the first alias and change the name and then create the second alias ?
-
Just create one pfBNG alias 'Alias Native' type and add the Countries. You can create as many rules based on this one alias.
-
I don't think I'm explaining well … For example, I actually want/need to have an two different alias for North America.
"Outbound_Block_North_America" would be a list that contains 60% of the countries and this will be countries I want to block outbound access to in North America. I will block only a few countries as I want to visit internet sites in most countries in North America. I would create a "Block outbound to Outbound_Block_North_America"
"Inbound_North_America" would be a list that contains only Canada and the United States since these are the only two countries in North America that should be allowed inbound. I would create a "Permit Inbound_North_America to Open_Ports" rule for these.
Just can't quite see how to create these two different Alias from North America and have them coexisting at the same time - maybe it's not possible? Apologies for dragging this out.
FYI: I'm not getting the "Alias Native" option in the drop down. I have only "Alias Block", "Alias Permit", and "Alias Match". I just installed pfBlocker this past week, into PFSense 2.2.4 (i386).
-
ok I misunderstood your questions the first time around. It seemed like you wanted to create two of the same Alias configurations… So what you are proposing is fine.
I notice in the Top20 tab that it is missing the "Alias Native" option. I will add that soon. However, the "native" option is available in all the other Continent tabs inc (v4/v6 tabs)
I suggest you make a new Alias (and not use the Continent tabs), and add the path to the CC folder directly, as per the following link:
https://forum.pfsense.org/index.php?topic=102071.msg569296#msg569296Then once the two aliases are created, run a "Force Update" to get those built. Then create your Firewall rules with your requirements and reference the appropriate alias.
-
Thanks - that does exactly what I want and worked fine! One minor thing to point out, the instructions for adding the country data to the list are:
"'Country code': /usr/pbi/pfblockerng-amd64/share/GeoIP/cc/US_v4.txt (Change 'US' to required code)"
However, depending on your hardware, you might need to change "amd64". In my case, it didn't work until I changed this to "i386".
Thanks again!
-
Thanks - that does exactly what I want and worked fine! One minor thing to point out, the instructions for adding the country data to the list are:
"'Country code': /usr/pbi/pfblockerng-amd64/share/GeoIP/cc/US_v4.txt (Change 'US' to required code)"
However, depending on your hardware, you might need to change "amd64". In my case, it didn't work until I changed this to "i386".
Thanks again!
I am running out of real estate on the pages to add more help text! Not that many people read it! :) Thanks for the feedback!