PfBlocker
-
From Countryblocks site…
We have temporarily suspended certain services as our donation stream has suffered a significant decrease here in the fourth quarter. We are pursuing some other financing options to help us focus on providing you with our services. This temporary suspension may last a few hours or a few days. If you would like to help us expedite the process please consider making a donation to Country IP Blocks through the PayPal link (on their site)
-
If you can, please donate to Country IP Blocks
Site: http://www.countryipblocks.net/
We need to support this site.
-
Just released version 0.1.4.6 with fixes in float rules check and about section in gui.
Reinstalled, Floating rules are still there after a pfBlocker save, great ::)
Counter updates when pinging from pfsense box.
Counter is reseted on firewall rule changes.When I select loopback interface, where does it put the rules?
-
When I select loopback interface, where does it put the rules?
Nothing :)
As we only use pfsense's framework components, interface selection includes loopback.
If you select just loopback, pfBlocker send you a warning.
-
On reinstall we always get the Reload status missing alias error: php: : New alert found: # unresolvable dest aliases
This is because pfBlocker is disabled by default on install.if you click ACKNOWLEDGE ALL in the Package Installer window, you ended up with:
Installation of FAILED! ------------------------- Installation halted.
Everything is fine and working after you enable pfBlocker.
-
On reinstall we always get the Reload status missing alias error: php: : New alert found: # unresolvable dest aliases
Please, remove custom alias before removing package.
pfBlocker is just doing what you asked him to do (do not touch my rules).if you click ACKNOWLEDGE ALL in the Package Installer window, you ended up with:
Installation of FAILED! ------------------------- Installation halted.
when you click ACKNOWLEDGE ALL you reload the page, and then get a 'reinstallation' error.
This is not related to pfBlocker.
-
I've pushed a fix in cron call to check if pfBlocker is enabled or not.
if you have installed pfBlocker before now + 15 min, reinstall package.
-
Done.
Everything is running fine. -
Great news, thanks for your feedback.
-
I'm running on Alix 2D13.
Installed pfSense-1.2.3-RELEASE-2g-nanobsd.img.gz on a 2GB card.
Version 2.0-RELEASE (i386) built on Tue Sep 13 18:02:53 EDT 2011
Platform nanobsd (2g)
CPU Type Geode(TM) Integrated Processor by AMD PCS
Uptime 31 days +
I'm running Peerblocker on a local windows xp machine.
Is is possible to have a stripped down pfsense server - to do the same job as peerblocker (http://www.peerblock.com/) ?
(it now has 2.301.808.963 IPs and counting..)Or should I look else where ?
-
It seems that peerblocker is another thing and meant for windows.
Unless you convince a unix knowledgable to port it to unix i do not think you will have much success in that way.
-
I'm running on Alix 2D13.
Installed pfSense-1.2.3-RELEASE-2g-nanobsd.img.gz on a 2GB card.
Version 2.0-RELEASE (i386) built on Tue Sep 13 18:02:53 EDT 2011
Platform nanobsd (2g)
CPU Type Geode(TM) Integrated Processor by AMD PCS
Uptime 31 days +
I'm running Peerblocker on a local windows xp machine.
Is is possible to have a stripped down pfsense server - to do the same job as peerblocker (http://www.peerblock.com/) ?
(it now has 2.301.808.963 IPs and counting..)Or should I look else where ?
pfBlocker does the same job as peerblocker. pfBlocker replaces IP-Blocklist and IP-Blocklist was created to mimic peerblocker. You can use the same lists that you are using in peerblocker and apply them to pfBlocker. This way you get protection not just on a single machine but your entire network.
pfBlocker is Peerblock for pfsense.
-
We need a way to verify that PfBlocker is downloading lists properly and blocking. It should display the number of IP's being blocked from downloaded lists.
-
We need a way to verify that PfBlocker is downloading lists properly and blocking. It should display the number of IP's being blocked from downloaded lists.
There is. Marcello built that into the widget. You can add it on the home page HUD by pressing the '+' button.
This widget counts the CIDRs currently applied in your tables that pfblocker creates.
-
@ Tommyboy - Thanks for that I did not know to look at the widget.
I am getting the following error with PFblocker now. It reports "out of memory" but RAM usage is only about 53%:
: The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:20: cannot define table pfBlockerLevel1Inbound: Cannot allocate memory /tmp/rules.debug:22: cannot define table pfBlockerLevel1Outbound: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded'
Does anybody know how to remedy this?
-
Getting more errors:
There were error(s) loading the rules: /tmp/rules.debug:20: cannot define table pfBlockerLevel1Inbound: Cannot allocate memory
/tmp/rules.debug:22: cannot define table pfBlockerLevel1Outbound: Cannot allocate memory
/tmp/rules.debug:36: cannot define table pfBlockerPrimaryThreats: Cannot allocate memory
pfctl: Syntax error in config file: pf rules not loaded The line in question reads [20]: table <pfblockerlevel1inbound>persist file "/var/db/aliastables/pfBlockerLevel1Inbound.txt"My router is a laptop router and is not out of memory.</pfblockerlevel1inbound>
-
ipv6kid,
-
Increase even more Firewall Maximum Table Entries
-
clear ipblocklist table in diagnostics-> table
-
check if the value of table-entries in /tmp/rules.debug is the same in Firewall Maximum Table Entries
-
check also if table-entries is declared twice in /tmp/rules.debug
This should correct your errors. Basically what is happening is system variable has set a ceiling on the tables. You can manually override this by changing that value to allow larger tables.
-
-
ipv6kid,
Also check lists description. Level1 ipblocklist includes only 'good' networks.
Blocking a grey list may not be a good choice.
-
First, thanks for the reply. I have set the maximum Firewall tables to 550,000 just to be safe but under Diagnostics > Tables there is no PFblocker drop down selection.
I am still getting memory allocation errors even though I've done all of this and reset the states. Could it be anything else?
-
You said to make sure I didn't have double "table-entries", what if I used the same list to deny inbound and outbound? Would that cause this error?