PfBlocker

KongGulerod · Dec 20, 2011, 5:56 PM

Thanx for a great package - I like how it integrates and uses pfSense 2.0 firewall aliases and WAN/LAN rules :-)

A small observation and fix request (latest pfSense 2.0 release + latest pfBlocker):

After placing the pfBlocker widget on the bottom part of my long pfSense 2.0 dashboard page with vertical scrollbar, I observed that the dashboard page/scrollbar automatically reverted back to the top of the page at a fixed interval (every 5-10 secs).

This is a bit annoying if I am looking at data from a widget in the bottom part of the dashboard page - and every 5-10 seconds the page jumps to the top (internal pfBlocker refresh?) and I have to manually use the scrollbar/mouse/arrow-keys to navigate back down to the bottom of the page.

If I temp. removed the pfBlocker widget from dashboard the mis-behaviour went away also.

Hope you can reproduce this scenario and look forward to next release :-)

marcelloc · Dec 20, 2011, 6:12 PM

I observed that the dashboard page/scrollbar automatically

Thanks for the feedback.

I`ve removed scroll call in widget.

reinstall package in about 15 minutes.

If you have many widgets, consider testing widescreen package. It may help you.

AhnHEL · Dec 20, 2011, 6:44 PM

Reinstalled and now I'm not getting any CIDRs or Packets in the widget.

![Screen Shot 2011-12-20 at 1.47.33 PM.png](/public/imported_attachments/1/Screen Shot 2011-12-20 at 1.47.33 PM.png)
![Screen Shot 2011-12-20 at 1.47.33 PM.png_thumb](/public/imported_attachments/1/Screen Shot 2011-12-20 at 1.47.33 PM.png_thumb)

marcelloc · Dec 20, 2011, 7:18 PM

fixed javascript again, try reinstall in 15 minutes.

LEPM · Dec 20, 2011, 9:35 PM

pf 2.0 i386 + squid+squidguard+pfblocker 1.0 and 1.0.1 works very well (deny inbound)

pfblocker 1.0.1+ deny both, crash pfsense!!
reboot and crash,crash…
changing to deny inbound,works well again

marcelloc · Dec 20, 2011, 10:22 PM

Can you be more specific on what kind of crash you have?

I'm using deny both with no issues or crashes.
Boot process is fine too.

KongGulerod · Dec 20, 2011, 10:27 PM

@marcelloc:

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 · Dec 21, 2011, 5:18 AM

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 · Dec 21, 2011, 6:07 AM

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

RonpfS · Dec 21, 2011, 6:19 AM

@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 · Dec 21, 2011, 8:27 AM

@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 · Dec 21, 2011, 8:49 AM

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 · Dec 21, 2011, 9:55 AM

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 · Dec 21, 2011, 10:46 AM

@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 · Dec 21, 2011, 10:50 AM

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

Metu69salemi · Dec 21, 2011, 10:56 AM

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

raind0wn388 · Dec 21, 2011, 5:19 PM

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 · Dec 22, 2011, 3:08 AM

What action did you choose for it?

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

check firewall -> rules

raind0wn388 · Dec 21, 2011, 5:38 PM

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

jroberts31xray · Dec 26, 2011, 9:48 PM

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