IP-Blocklist

tommyboy180 · May 7, 2010, 1:10 AM

I am still trying to get a hold of a dev. I have emailed them and contacted them on the freenode chat room.

I can email you a globals.inc file if you need. PM me.

tommyboy180 · May 12, 2010, 8:58 PM

Version 0.1.9 is complete.

Changes:

If enabled the block list will apply on start-up.
Fixed "out of memory" errors. You can now have a lvl1,2,&3 list applied at the same time. New limit is 900,000 entries
Removes duplicate entries to speed up process

This version is considered very stable. I have tested on 1.2.2 and 1.2.3.

Supermule · May 13, 2010, 9:20 AM

Nice work Tommy!!

Have you had any luck getting hold of the dev's??

@tommyboy180:

Version 0.1.9 is complete.

Changes:

If enabled the block list will apply on start-up.

Fixed "out of memory" errors. You can now have a lvl1,2,&3 list applied at the same time. New limit is 900,000 entries

Removes duplicate entries to speed up process

This version is considered very stable. I have tested on 1.2.2 and 1.2.3.

Cino · May 13, 2010, 2:59 PM

When I try just the level1 list, i get this error after a min or 2 of clicking save/update

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 81 bytes) in /etc/inc/util.inc on line 381

The status states it is running but the Enable IP-Blocklist is not checked, even tho i checked it before clicking on save/update

I've tried the level 2 and level 3 list and did not get the same error… Worked like it should I think...

tommyboy180 · May 13, 2010, 6:23 PM

Yes. The web server runs out of memory. You can increase the memory limit in the php.ini file

The script still operates as it should and the lists still get applied as they should. The only downside that I can see from this error is that the "Enabled" checkbox seems to not be checked when in fact it is.

I chose not to have the package edit the php.ini memory limit because I didn't want to crash a pfsense install that had limited memory.

You are correct that it does work as it should even with the error.

Cino · May 13, 2010, 7:36 PM

Thanks again!!! Would you happen to know which php.ini file to change and how would I get it to stay after a reboot?

peterclark4 · May 21, 2010, 7:49 AM

Will this automatically update the lists like PeerBlock/PeerGuardian does?

g4m3c4ck · May 22, 2010, 9:39 PM

Just to be sure where exactly do the tarballs content go? And will the howto instructions break the current pkg system?

tommyboy180 · May 22, 2010, 11:55 PM

This package gets updated on start-up and every time you click save.

The tar archive is if you wanted to experiment without the package system. Just change your package system settings back to default after you install. This is only temporay until a DEV is kind enough to commit my package.

tommyboy180 · May 23, 2010, 4:15 PM

IP-Blocklist is now available as a package!

Sambo · May 23, 2010, 9:00 PM

@tommyboy180:

This package gets updated on start-up and every time you click save.

Are you referring to the package itself or the blocklists? Is there a way to automatically update your blocklists daily or whatever without restarting the firewall?

tommyboy180 · May 23, 2010, 9:03 PM

On start-up the blocklists will get updated.

To have the lists updated on a specific schedule you have to create a cron job. The file to run is /usr/local/etc/rc.d/IP-Blocklist.sh

Sambo · May 23, 2010, 9:41 PM

@tommyboy180:

On start-up the blocklists will get updated.

To have the lists updated on a specific schedule you have to create a cron job. The file to run is /usr/local/etc/rc.d/IP-Blocklist.sh

Sweet, thanks. That would be a feature request from me then; GUI based scheduled blocklist updates :)

ari · May 24, 2010, 7:25 AM

I would be interested in being able to tie this into Fail2Ban. Do to do we'd need a simple API to add items to the list. For example a RESTful api:

/api/blocklist/add?ip=1.2.3.4&expire=3600&key=kjdsft34jk8

peterclark4 · May 24, 2010, 11:24 AM

This wouldn't play nice with the NanoBSD install until I added lines to mount the CF card for R/W access and then back to R/O access at the point of where it writes to the lists.txt file in ipblocklist_list.php.

simby · May 24, 2010, 3:27 PM

I have this problem in pfsense 2.0 beta 1

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 81 bytes) in /etc/inc/util.inc on line 785

tommyboy180 · May 24, 2010, 4:25 PM

@simby:

I have this problem in pfsense 2.0 beta 1

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 81 bytes) in /etc/inc/util.inc on line 785

Take a look at Cino's post above.

jideel · May 25, 2010, 8:45 AM

Hello,

Sorry, but i can't get it to work.
I'm using pfSense 1.2.3 release and IP-Blocklist 0.1.9.
The box is used in a multi-wan context, plus some IPsecs, plus PPTP, plus Squid/Squidguard (use only on WAN1).
I tried to use the following list : http://list.iblocklist.com/?list=cn, and it seems to be well added in the GUI, but the status is always shown as "NOT running" in red.
I enabled/disabled the module, saved/updated, there's no error such as the memory error, and no message in the logs.
Any idea ?
Thank you.

sofakng · May 25, 2010, 12:09 PM

How much do these additional tables slow down the router?

It seems like "normal" firewalls only block a very small number of hosts (50?) but these lists seem to contain thousands of entries and it seems like it would take a lot of time to process every packet against so many hosts…

peterclark4 · May 25, 2010, 12:52 PM

@peterclark4:

This wouldn't play nice with the NanoBSD install until I added lines to mount the CF card for R/W access and then back to R/O access at the point of where it writes to the lists.txt file in ipblocklist_list.php.

I still don't think that this is playing well with my NanoBSD install. I'm getting no errors and the current status is "Running" but it doesn't appear to be blocking any connections.