PfBlocker

KongGulerod

I`ve removed scroll call in widget.
reinstall package in about 15 minutes.

Seems to work fine now… no forced scrolling to the top when refreshing numbers.

Thanx !!

AhnHEL

Getting this error now trying to enable pfBlocker, and the widget still looks like the pic i posted above.

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10499768 bytes) in /usr/local/pkg/pfblocker.inc on line 281

RonpfS

Increase Firewall Maximum Table Entries under System: Advanced: Firewall and NAT
you may have to increase Firewall Maximum States at some point

RonpfS

@marcelloc:

fixed javascript again, try reinstall in 15 minutes.

Reinstalled and now the Dashboard doesn't scroll anymoire ;D
Being at it 8) is-it possible to have the option to Enable pfBlocker by default on reinstall?

AhnHEL

@RonpfS:

Increase Firewall Maximum Table Entries under System: Advanced: Firewall and NAT
you may have to increase Firewall Maximum States at some point

I'm already up to 2 million entries, even increasing to 200 million doesnt resolve issue. Been using pfBlocker since it was first introduced and havent had an issue until now.

Edit:

Using the Top Spammers works fine, it has something to do with the iBlocks lists. Using the same bunch of lists that I PM'd you back during this post.

http://forum.pfsense.org/index.php/topic,42543.msg219723.html#msg219723

RonpfS

I ran into that kind of issue when I played with the Level 1 at some point. I was using alias only.
It looked like the table were locked by Firewall Rules, when I disabled pfblocker, the table would still showed up.
I removed pfBlocker and the table were still there under Diagnostics: Tables!!!
I install pfblocker and at some point I recovered. But I am not using Level 1 at this time.

marcelloc

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10499768 bytes) in /usr/local/pkg/pfblocker.inc on line 281

It looks like very large lists.

Try to remove some lists and enable pfBlocker.

Metu69salemi

@onhel:

Getting this error now trying to enable pfBlocker, and the widget still looks like the pic i posted above.

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10499768 bytes) in /usr/local/pkg/pfblocker.inc on line 281

do you have 128GB harddisk? meaning 134217728 bytes divided with 1024 twice is exactly 128GB

marcelloc

No, its 128mb RAM limit for php set on pfsense.

Metu69salemi

Sorry yes it was MB, not GB's.. assumed still that was kB's. :-[ :-[

raind0wn388

I tried getting pfblocker to start, doesn't appear to be running in any of my system logs or processes. Tried reinstalling over and over, and the CIRDs in the dashboard widget still show a red down arrow. Any ideas how I can start the process manually via the shell?

marcelloc

What action did you choose for it?

You need at least one rule on interface to get pfBlocker working.

check firewall -> rules

raind0wn388

Ah that was the reason! Didn't know that, thanks!

jroberts31xray

Good work guys! Nice new tools, usability and not to mention it works perfectly :P…..thanks for bringing two of my fav PF tools together.....Love it!

btw if anyone is using PF 2.0 as a "bridged router" ...set both options to "lan" .... just something i found out the hard way. ;D

marcelloc

Good work guys! Nice new tools, usability and not to mention it works perfectly …..thanks for bringing two of my fav PF tools together.....Love it!

Thanks for your feedback.

Consider donating to these package developers, we will feel fantastic too. ;)

sofakng

Does using these large lists slow down the routing at all? It seems like thousands of IPs in the PF tables would slow it down a bunch… ?

tommyboy180

@sofakng:

Does using these large lists slow down the routing at all? It seems like thousands of IPs in the PF tables would slow it down a bunch… ?

It depends entirely on your system. Most hardware platforms will not be affected by 100's of thousands of IP's but an embedded system may. It completely depends.

Basically you want to limit your usage to less than 75 to 80 percent of your available RAM. If you're running other addons like squid then you may want to use less than 50 percent of available RAM.

In the cases where the system is slowed down by larger lists or the accumulation of large list the effects will be so small that you will not notice unless you host or depend on real time apps that are time sensitive. Other wise everything should be okay.

rdunkle

updated to pfsense 2.01. Removed country block and ipblock. Installed pfblocker
pfblock appears to work fine.
I am seeing a frequent messages in system log:
Dec 29 12:13:35 <user.notice>fw root: IP-Blocklist was found not running
Dec 29 12:16:26 <user.err>fw apinger: ALARM: WANGW(192.168.75.1) *** delay ***
Dec 29 12:16:36 <user.notice>fw check_reload_status: Reloading filter
Dec 29 12:16:42 <user.notice>fw root: IP-Blocklist was found not running
I do not see IP-Blocklist in the installed packages.
I see a reference in the config.xml :
–-------

<ipblocklist_settings><config><enable>0</enable></config></ipblocklist_settings>

why is IP-Blocklist trying to get restarted ?
Is there another file that still thinks IP-Blocklist is installed ?</user.notice></user.notice></user.err></user.notice>

marcelloc

maybe you need to delete its remaining script.

'/usr/local/pkg/pf/IP-Blocklist.sh'

Also look for ipblocklist scripts in /usr/local/etc/rc.d

I see a reference in the config.xml

follow these steps:

backup configuration
open /conf/config.xml
remove these entries
save file
reboot pfsense

taryezveb

I keep getting these messages in the system log:

Dec 29 17:01:02 php: : There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 17:01:02 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 17:00:53 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded'

Dec 29 17:00:23 php: : There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 17:00:23 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 17:00:15 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded'

Dec 29 16:59:45 php: : There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 16:59:45 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 16:59:36 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded'

Dec 29 16:59:06 php: : There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 16:59:06 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded The line in question reads [19]: table <pfblockertbg>persist file "/var/db/aliastables/pfBlockerTBG.txt"

Dec 29 16:58:58 php: : The command '/sbin/pfctl -o basic -f /tmp/rules.debug' returned exit code '1', the output was '/tmp/rules.debug:19: cannot define table pfBlockerTBG: Cannot allocate memory pfctl: Syntax error in config file: pf rules not loaded'

But in the Dashboard everything looks good.

2011-12-29-170804_1438x884_scrot.png_thumb

2011-12-29-171601_1438x884_scrot.png_thumb </pfblockertbg></pfblockertbg></pfblockertbg></pfblockertbg></pfblockertbg></pfblockertbg></pfblockertbg></pfblockertbg>