PfBlocker
-
This is 2.1.4 right? 2.2 Alpha will fail loading/updating these lists, that has been reported and they are working on it. Another thing is a lot of those lists duplicate each other, ie. have the same IP's in the lists.
Read this thread:https://forum.pfsense.org/index.php?topic=78062.0
Remove Prime, it is a combination of several the lists you already have as aliases and is not needed, read the description of Prime. Prime might be the problem since it itself is absolutely huge… If removing Prime doesn't help then:
Back up pfBlocker.inc then Look for a line in the pfBlocker.inc that looks something like this:```
if ($uname['machine'] == 'amd64')
ini_set('memory_limit', '256M');Change the 256M to 512M and see if that helps. @panz: > I have "splitted" my (big) list: now each I-Block list matches one pfBlocker list (with Alias_only) selected (see attached screenshot). Lists are set on I-Block URL to be in CIDR. > > I'm still receiving this error message when I try to start pfBlocker > > ``` > Fatal error: Allowed memory size of 262144000 bytes exhausted (tried to allocate 18 bytes) in /usr/local/pkg/pfblocker.inc on line 253 > ``` -
Thank you @wcrowder for the fast response. I don't like any list in particular: I wanted to test each of them with a firewall rule for each list so - by analyzing the logs - I'll be able to keep the lists that hit the blocking rule the most of times.
I can't still believe that a Unix OS can't handle a simple task like this: as I wrote in this thread, my stupid Windows 7 machine with the same amount of RAM can load ALL those lists in PeerBlock FAST! And it works flawlessly, blocking and notifying 24/7.
-
You can not compare pfSense to Peer-block, in comparison Peer-block is truly useless. How may Windows 7 machines act as firewalls to large networks, do you wonder why? pfSense is. Did you follow through the link to the thread I sent you above? Follow the instructions, remove the duplication? Here, I'll give it to you again: Read this thread:https://forum.pfsense.org/index.php?topic=78062.0
Thank you @wcrowder for the fast response. I don't like any list in particular: I wanted to test each of them with a firewall rule for each list so - by analyzing the logs - I'll be able to keep the lists that hit the blocking rule the most of times.
I can't still believe that a Unix OS can't handle a simple task like this: as I wrote in this thread, my stupid Windows 7 machine with the same amount of RAM can load ALL those lists in PeerBlock FAST! And it works flawlessly, blocking and notifying 24/7.
-
Yes, I removed the duplicates: I logged into pfSense with WinSCP and manually deleted those jsjdjdjjdjjddkkakirtitjjf.txt files. Then I deleted the pfBlocker package and all the files in the upper pkg dir that contained the word pfBlocker.
Strangely enough, after pfBlocker reinstallation, all the lists were still there, listed in the GUI, so maybe do I need to purge other files?
-
The xx.txt files need to be there. They are the county code files for country blocking. The duplicates I was talking about are IP's in the lists. Example: On the iBlockList website the iBlock Prime list already includes the US Government, Malicious, Piracy Related, Pornography, Ads and Trackers and Proxies lists so when you add Prime AND those lists you have DUPLICATION that you don't need…
Yes, I removed the duplicates: I logged into pfSense with WinSCP and manually deleted those jsjdjdjjdjjddkkakirtitjjf.txt files. Then I deleted the pfBlocker package and all the files in the upper pkg dir that contained the word pfBlocker.
Strangely enough, after pfBlocker reinstallation, all the lists were still there, listed in the GUI, so maybe do I need to purge other files?
-
Ok, I'm going to dedupe the lists. Where is the lists' list stored? Even after a package reinstall, the list is there.
-
Could we make a pfblocker community so we easily can share files and lists?
Maybe from within the package itself?
-
I'm emailing to I-Blocklist maintainer to ask him if he could implement a deduplication feature in the customized lists section. For now, I'll be happy if the pfBlocker package could handle a memory increase by itself. I don't want to mess with file editing in an appliance.
-
Not a bad idea.
I'm emailing to I-Blocklist maintainer to ask him if he could implement a deduplication feature in the customized lists section. For now, I'll be happy if the pfBlocker package could handle a memory increase by itself. I don't want to mess with file editing in an appliance.
-
Just wait for a pfBlocker update… ::)
-
-
It is being very actively forked, we will just have to wait for an announcement from the author doing the update… Or, you could read this thread more carefully. ;D Did you read the thread I posted to you Panz? :-*
Is MArcello still developing this?
Just wait for a pfBlocker update… ::)
-
Thanks! We need forks :)
-
<shaking head="">:-\ and thinking out loud… In the 30yrs I've done this every good Forum has a Troll.
Thanks! We need forks :)</shaking>
-
And youre doing it better than ANY out there ;)
<shaking head="">:-\ and thinking out loud… In the 30yrs I've done this every good Forum has a Troll.
Thanks! We need forks :)</shaking>
-
Wasnt me…dont use that at all
-
-
I really like the idea of blocking entire countries that my network has no business connecting to and put together a script to update pfBlockers country CIDR lists with the lists available from IPdeny.com
Edit - The script didn't work as intended and has been taken down
The download is at the bottom of http://legoclan.com/pfsense/ all feedback is welcome
-
Hi!
How can i fix this on PF 2.2 BETA?
Crash report begins. Anonymous machine information:
amd64
10.1-PRERELEASE
FreeBSD 10.1-PRERELEASE #28 30e366f(HEAD)-dirty: Fri Sep 19 23:30:48 CDT 2014 root@pf22-amd64-snap:/usr/obj.amd64/usr/pfSensesrc/src/sys/pfSense_SMP.10Crash report details:
PHP Errors:
in /usr/local/pkg/pfblocker.inc on line 256 -
I really like the idea of blocking entire countries that my network has no business connecting to and put together a script to update pfBlockers country CIDR lists with the lists available from IPdeny.com
The download is at the bottom of http://legoclan.com/pfsense/ all feedback is welcome
Hi f34rinc,
This will update the ISO files for pfBlocker but it doesn't update the XML Continent Files (ie - Africa) with the changes made to the Country Names. So there could be some inconsistencies.
There are files named
Africa_cidr.txt that have this type of header:
Continent: Africa
Country: Reunion
ISO Code: RE
Total Networks: 245
These files are used by this command to rebuild the XML files based upon the 6 Continent Files.
/usr/local/bin/php /usr/local/www/pfblocker.php uc
