PfBlocker

marcelloc

Not sure, I did it on a x64 virtual machine and I do not get php limit errors.

All files are uploaded.

EDIT

With all these large files, my virtual machine gets 100% cpu for more then a minute and even with a very large table size, it reach virtual machine memory limit (384Mb).

marcelloc

Something interesting about table-entries limit:

I've set up maximum table entries to a very high value 99999999999 at gui and could see it reflected on /tmp/rules.debug

BUT

on pfctl -sa I get this:
LIMITS:
states hard limit 1000000
src-nodes hard limit 1000000
frags hard limit 5000
tables hard limit 1000
table-entries hard limit 1215752191

I saw my virtual machine freezing console with 99999999999 value, so I reduced it on gui to 5000000

EDIT

After 2G RAM, Firewall Maximum Table Entries set to 5000000 and a reboot

I get no erros with both large lists applied

as x64 version already has ini_set("memory_limit","256M");, I've just included ini_set('memory_limit', '250M'); on line two of /usr/local/pkg/pfblocker.inc

taryezveb

@marcelloc:

Something interesting about table-entries limit:

I've set up maximum table entries to a very high value 99999999999 at gui and could see it reflected on /tmp/rules.debug

BUT

on pfctl -sa I get this:
LIMITS:
states hard limit 1000000
src-nodes hard limit 1000000
frags hard limit 5000
tables hard limit 1000
table-entries hard limit 1215752191

I saw my virtual machine freezing console with 99999999999 value, so I reduced it on gui to 5000000

EDIT

After 2G RAM, Firewall Maximum Table Entries set to 5000000 and a reboot

I get no erros with both large lists applied

as x64 version already has ini_set("memory_limit","256M");, I've just included ini_set('memory_limit', '250M'); on line two of /usr/local/pkg/pfblocker.inc

Interesting, and yes when I edited /etc/inc/config.inc I saw it already had ini_set("memory_limit","256M"); . I have a x64 install. Nevertheless when I get a chance I will try your last settings again and reboot. Thanks for the info.

taryezveb

@marcelloc:

EDIT

After 2G RAM, Firewall Maximum Table Entries set to 5000000 and a reboot

I get no erros with both large lists applied

as x64 version already has ini_set("memory_limit","256M");, I've just included ini_set('memory_limit', '250M'); on line two of /usr/local/pkg/pfblocker.inc

Yes! :) I tested the above and no more errors, sort of; I'll explain below.

I did the following:

Edited /usr/local/pkg/pfblocker.inc adding the following on the first line where the comments end[from the top]. Right after this line:
*/ <- this is line number 31
ini_set("memory_limit", "250M"); <- this would be line number 32

Then set the Firewall Maximum Table Entries: 5000000 and did a reboot. But received these errors:
Dec 31 18:13:44 php: : There was an error while parsing the package filter rules for /usr/local/pkg/squid.inc.

Dec 31 18:13:44 php: : The command '/sbin/pfctl -nf /tmp/rules.test.packages' returned exit code '1', the output was 'no IP address found for 550.164.3.166/32 /tmp/rules.test.packages:17: file "/var/db/aliastables/pfBlockerBluetack.txt" contains bad data'

After some testing those errors are due to using the following list:
http://list.iblocklist.com/?list=bt_proxy&fileformat=p2p&archiveformat=gz

NOTE: I tried several times removing and adding that list, with the same result.

Once I removed that list I got this:
Dec 31 18:46:28 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was 'no IP address found for 75.35.185. /tmp/rules.debug:19: file "/var/db/aliastables/pfBlockerTBG.txt" contains bad data no IP address found for ÿ0.0.0.0/8 /tmp/rules.debug:95: file "/etc/bogons" contains bad data pfctl: Syntax error in config file: pf rules not loaded'

More testing and the error above was due to this list:
http://list.iblocklist.com/?list=bt_level1&fileformat=p2p&archiveformat=gz

But this time after removing the list above and re-adding the error went away. I guess there are some issues with those lists. Will try to contact the author to see if that can be fixed.

So in the end, no more errors and Squid works as a transparent proxy using pfBlocker as well now :)

For reference these are the lists that I'm currently using error free:

<pfblockerlists><config><aliasname>Bluetack</aliasname>

<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_level1&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_level2&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_level3&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_ads&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_spyware&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_templist&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_hijacked&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_dshield&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=bt_bogon&fileformat=p2p&archiveformat=gz</url></row>
<action>Deny_Inbound</action>
<cron>EveryDay</cron></config>
<config><aliasname>TBG</aliasname>

<row><format>gz</format>
<url>http://list.iblocklist.com/?list=ijfqtofzixtwayqovmxn&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=ecqbsykllnadihkdirsh&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=tbnuqfclfkemqivekikv&fileformat=p2p&archiveformat=gz</url></row>
<row><format>gz</format>
<url>http://list.iblocklist.com/?list=ewqglwibdgjttwttrinl&fileformat=p2p&archiveformat=gz</url></row>
<action>Deny_Inbound</action>
<cron>EveryDay</cron></config></pfblockerlists>

I would like to Thank marcelloc for his time looking into this. A donation was made[yesterday, before marcelloc posted the fix]; will donate again when I can. Hope this change is added to the package for all to benefit, after a few more days of testing. To make sure this change does not affect anything else.

EDIT: Happy New Year :)

marcelloc

Thanks ;D. Did you mentioned these packages developers on donation?

taryezveb

@marcelloc:

Did you mentioned these packages developers on donation?

Yes, I broke it down on how the donation should broken up. Like so: $XX for the X package maintainer(s).

marcelloc

I'll include this ini_set('memory_limit', '250M') patch when pfblocker detects a x64 version.

There are other places to edit it, maybe a redmine for that as diagnostics-> tables also has a 128Mb limit even on x64.

taryezveb

@marcelloc:

I'll include this ini_set('memory_limit', '250M') patch when pfblocker detects a x64 version.

There are other places to edit it, maybe a redmine for that as diagnostics-> tables also has a 128Mb limit even on x64.

Great and yes good point, since Diagnostics -> Tables gives a similar: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /usr/local/www/diag_tables.php on line 89

But at least that does not affect things like the previous "Fatal error: Allowed memory size…" did.

tommyboy180

countryipblocks.net is testing their latest IPv4 Network Aggregation scripts and would like to have your help. They are in two formats:

PG2 and IP Range.

If you get a chance, please test them with us and give feedback so we can pass on to countryipblocks.

www.countryipblocks.net

RonpfS

I ran into an issue with pfBlocker when trying to copy the configuration onto a new install.

I am using aliases only, a Block in rule on WAN, a Reject out rule on LAN.
I have the following packages: Backup 0.1.5, Cron 0.1.5, Filemanager 0.1.1, pfBlocker 1.0.1, Snort 2.9.1 v 2.0.2
Running pfsense 2.0.1 x86

I saved the configuration including RRD data
I restored the configuration to a fresh 2.0.1 install on the same machine

It rebooted and started to install packages, but pfsense could not access the internet because of the pfBlocker was not running and the missing aliases break the firewall.
I could not recover, removing rules didn' work. I was spending too much time trying things and failing, I ended up cloning the old disk instead.

What is the way to recover from the pfBlocker aliases problem?
just removing the rules in the GUI didn't work. I didn't try to remove the table or alias.
I remove the rules in the config.xml, to no available.
Today I see that I should have removed the alias. Is this enough?
I do not have a spare machine to do testing.

What is the best way to copy the configuration ?
Was I supposed to install all the packages before restoring the configuration?
This might have worked if the Restore config script did the package install before the reboot.
(or download the package now before the reboot to prepare for package install)

I guess removing the rules and disabling pfBlocker before saving the configuration should work.

marcelloc

I restored the configuration to a fresh 2.0.1 install on the same machine

You may need to install packages before config restore

I did few upgrades with pfblocker installed with no erros, but I did not tried a system restore.

I'll try to reproduce it.

Are you using pfBlocker on full install or nanobsd?

I guess removing the rules and disabling pfBlocker before saving the configuration should work.

This should be the best option

RonpfS

@marcelloc:

Are you using pfBlocker on full install or nanobsd?

Full install from CD pfSense-2.0.1-RELEASE-i386.iso.gz

2.0.1-RELEASE (i386)
built on Mon Dec 12 18:24:17 EST 2011
FreeBSD 8.1-RELEASE-p6

Platform pfSense
CPU Type Intel(R) Pentium(R) 4 CPU 1.80GHz

taryezveb

@marcelloc:

I'll include this ini_set('memory_limit', '250M') patch when pfblocker detects a x64 version.

marcelloc,

Just wanted to report back. After using the above now for the last 6 days. I don't see that affecting anything.

marcelloc

countryipblocks.net released a new bogon network list on their site,

check this out. :)

http://forum.pfsense.org/index.php/topic,44867.msg233407.html#msg233407

taryezveb

I had to do a configuration restore today and I'm not getting any php memory error(s) so far. This includes reinstalling all packages. So, ini_set("memory_limit", "250M") in /usr/local/pkg/pfblocker.inc seems to not be needed here anymore, well at least so far. Will report back if I start to get the php memory error(s). But I wonder why it is working fine now without editing /usr/local/pkg/pfblocker.inc ?

marcelloc

when you apply a new list, pfblocker may increase memory usage do download list and apply it to alias.

when you upgrade downloaded files are not removed. The ini_set("memory_limit", "250M") will be merged to next release and used when x64 instalation is detected.

Thanks for your feedback :)

taryezveb

Great, Thanks :)

firestrife23

I'm seeing double entries for each rules list auto generated by pfblocker under firewall's rules… Is that's normal?

marcelloc

If you checked deny both, then will be two rules with the same list on each interface firewall rules.

Can you check if they are identical?

firestrife23

All of my rules are set to "Deny Inbound"