PfBlocker

RonpfS

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.

marcelloc

@RonpfS:

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).

@RonpfS:

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.

marcelloc

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.

RonpfS

Done.
Everything is running fine.

marcelloc

Great news, thanks for your feedback.

kilko

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 ?

eri--

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.

tommyboy180

@kilko:

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.

ipv6kid

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.

tommyboy180

@ipv6kid:

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.

ipv6kid

@ 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?

ipv6kid

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>

tommyboy180

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.

marcelloc

ipv6kid,

Also check lists description. Level1 ipblocklist includes only 'good' networks.

Blocking a grey list may not be a good choice.

ipv6kid

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?

ipv6kid

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?

marcelloc

If you need to inbound and outbound rules on same table, choose alias on list action and then create a manual rule in wan and other in lan.

If you still want list1, you may need 1.000.000 or more.

You can't see pfBlocker table because you got erros during apply.

ipv6kid

Yeah I just noticed some of these lists run into the hundreds of thousands of tables. I am running an old clunky dell laptop from 2003-ish. With only 768 MB of RAM, and when I enabled more states into the 2 million range, RAM usage shot up and it started swapping.

I'm also running SNORT on top of this, so I'm going to need a gateway with more RAM.

It seems to be working without errors now, I've disabled and re-enabled PFblocker… after deleting all the large block lists.

I can now see the pFblocker "tables" under Diagnostics > Tables.

I also think some of these "debug" errors were due to logging being enabled, so if anybody else is still having issues, try disabling that. Where does this even log to anyways? I couldn't find where it was logging to in the console unless it was going directly to system logs.

Thank you very much!

tommyboy180

FYI,

I'm running Level1, Level2, and Level3 on a system with only 256MB RAM. You don't need more RAM, just increase your Firewall Maximum Table Entries.

marcelloc,
Level1, Level2, and Level3 lists do have 'good' guys in the list but it's an Anti-P2P list. All the IPs have been involved in anti-P2P behavior. That's why I always run Level1 lists at a min. It's actually one of the main reasons why I made IP-Blocklist.

RonpfS

I use dshield, drop, hijacked etc on Pfsense Box.

I use the level 1, badpeers, etc on Seed Box with PeerBlock.