PfBlocker
-
Reinstalled and now I'm not getting any CIDRs or Packets in the widget.
 -
fixed javascript again, try reinstall in 15 minutes.
-
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 -
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. -
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 !!
-
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
-
Increase Firewall Maximum Table Entries under System: Advanced: Firewall and NAT
you may have to increase Firewall Maximum States at some point -
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? -
Increase Firewall Maximum Table Entries under System: Advanced: Firewall and NAT
you may have to increase Firewall Maximum States at some pointI'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
-
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. -
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.
-
@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
-
No, its 128mb RAM limit for php set on pfsense.
-
Sorry yes it was MB, not GB's.. assumed still that was kB's. :-[ :-[
-
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?
-
What action did you choose for it?
You need at least one rule on interface to get pfBlocker working.
check firewall -> rules
-
Ah that was the reason! Didn't know that, thanks!
-
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
-
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. ;)
-
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… ?
