PfBlocker
-
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).
-
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.
-
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.
-
-
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.
-
-
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
-
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-p6Platform pfSense
CPU Type Intel(R) Pentium(R) 4 CPU 1.80GHz -
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.
-
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
-
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 ?
-
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 :)
-
Great, Thanks :)
-
I'm seeing double entries for each rules list auto generated by pfblocker under firewall's rules… Is that's normal?
-
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?
-
All of my rules are set to "Deny Inbound"
-
Hi there. I'm running into a problem syncing my two pfSense 2.0.1 systems. The aliases do not appear to be synced when I make a change within pfBlocker. If I add an alias by hand, that syncs fine. Here is the error being reported in the log of the slave system when I try to turn on the TopSpammers rule:
php: : The command '/usr/bin/grep -v '^#' '/var/db/aliastables/pfBlockerTopSpammers.txt.tmp' > '/var/db/aliastables/pfBlockerTopSpammers.txt'' returned exit code '1', the output was ''
Any hints or thoughts?
Thanks!
-
biogoon,
I'll try to simulate it this weekend.
-
All of my rules are set to "Deny Inbound"
I have no duplicates here, can you send screenshots of your configuration as well system version?
-
I think I may have found a small bug with the package… I haven't re-read all 22 pages but did some searching within the topic and couldn't find it.
I'm using squid to improve web performance and for logging.. I have setup a couple of list within pfBlocker to block inbound(WAN) and outbound(LAN) Since squid uses localhost, i figured it would need to be a floating rule for it to catch. After reading a few post, but hunch was right..
After creating the floating rules, they seem to work.. But anytime I make a change within the pfBlocker config pages or just re-save, it deleted the floating rules. I'm thinking this is because pfBlocker deletes and re-creates the Alias's when the configuration its save..
I tried to create a new alias and nest the pfBlockers alias's into it but pfSense didn't like that.. I thought about creating brand new url table alias but then that would be a waste of memory.
any thoughts?
-
What description did you configured on floating rule?
If it was pfBlockeraliasname something rule, then pfBlocker will remove it.
Try 'pfBlockeraliasname for squid' and see if it survive an apply
