IP-Blocklist
-
I've been having an issue after installing IP-Blocklist. I can download a list (level_1 in my case), but when I check "enable" and "save/update", the machine will throw an error, "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 35 bytes) in /etc/inc/util.inc on line 380" 5-10 minutes afterwards. I suspect my machine is at fault since it's an old Dell PII maxed out at 512MB of RAM. The only other addons I'm running are cron, Country Block and Snort. Incidentally, IP-Blocklist was failing before I installed Snort and cron.
Thanks,
Jon -
@nipstech:
I've been having an issue after installing IP-Blocklist. I can download a list (level_1 in my case), but when I check "enable" and "save/update", the machine will throw an error, "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 35 bytes) in /etc/inc/util.inc on line 380" 5-10 minutes afterwards. I suspect my machine is at fault since it's an old Dell PII maxed out at 512MB of RAM. The only other addons I'm running are cron, Country Block and Snort. Incidentally, IP-Blocklist was failing before I installed Snort and cron.
Thanks,
JonThis has been addressed in the previous posts. Basically just let it run until the "working animation" in your browser stops. For more specifics look back on some previous posts.
-
I waited almost an hour with the fatal error screen and it never changed, however when I closed the browser session and reopened it, it showed that IP-Blocklist was running and was blocking x number of networks. Can I assume that the error can be ignored?
-
@nipstech:
I waited almost an hour with the fatal error screen and it never changed, however when I closed the browser session and reopened it, it showed that IP-Blocklist was running and was blocking x number of networks. Can I assume that the error can be ignored?
This behavior is normal. Did you look at the previous posts like I referred you to?
The previous posts explain that you don't have to wait for an hour, you just wait for the loading animation to finish.
The error can be ignored or fixed.
I love answering your questions and feel free to post any question but I did refer you to read on some past posts within this topic. Had you done that, you would have found your answer a lot sooner and wouldn't have wasted an hour.I'm glad you figured it out and got it working. I'm always looking for suggestion on how I can improve the package. Right now I have a list of things that I need to update soon, so hopefully that will be happen soon for those of you whom have been waiting patiently.
-
Thank You! :)
-
IP-Blocklist 3.0 is out!
Changes:
-
Email Notifications
-
Full BETA2.0 Support (tested on latest build)
-
Interface Filtering
-
Optional Outbound
-
And many bugs fixed!
Thank you all for your support!
-
-
Great! From where can it be downloaded and installed? It's not showing up in the available package list.
-
@nipstech:
Great! From where can it be downloaded and installed? It's not showing up in the available package list.
It's there. Do you have it installed already?
-
This is awesome. Thanks so much! The new whitelist is great - it's exactly what I was hoping for.
One thing, though: outbound blocks aren't logging. Should they? The setting is set to log. -
This is awesome. Thanks so much! The new whitelist is great - it's exactly what I was hoping for.
One thing, though: outbound blocks aren't logging. Should they? The setting is set to log.Glad you like it. Outbound doesn't log. I just never got to it. You can modify the script to log outbound on your own if you want. Just edit the script in /usr/local/www/packages/ipblocklist/ and /usr/local/etc/rc.d/ to include logging.
Perhaps I will add it soon as a minor update.
-
This is awesome. Thanks so much! The new whitelist is great - it's exactly what I was hoping for.
One thing, though: outbound blocks aren't logging. Should they? The setting is set to log.Glad you like it. Outbound doesn't log. I just never got to it. You can modify the script to log outbound on your own if you want. Just edit the script in /usr/local/www/packages/ipblocklist/ and /usr/local/etc/rc.d/ to include logging.
Perhaps I will add it soon as a minor update.
I would love to, but I wasn't able to make any sense of these. I don't know what makes the packet filter log drop rules.
-
This is awesome. Thanks so much! The new whitelist is great - it's exactly what I was hoping for.
One thing, though: outbound blocks aren't logging. Should they? The setting is set to log.Glad you like it. Outbound doesn't log. I just never got to it. You can modify the script to log outbound on your own if you want. Just edit the script in /usr/local/www/packages/ipblocklist/ and /usr/local/etc/rc.d/ to include logging.
Perhaps I will add it soon as a minor update.
I would love to, but I wasn't able to make any sense of these. I don't know what makes the packet filter log drop rules.
This is only a temporary fix until I update the package:
Sorry about that, I was on my way out the door when I replied. The two files you need to modify are /usr/local/www/packages/ipblocklist/convert-execute.sh and /usr/local/etc/rc.d/IP-Blocklist.shStarting at line 112 look for the line "if [ -f /usr/local/www/packages/ipblocklist/OUTBOUND ]; then"
The next line should have something like "echo "block quick from $i to <ipblocklist>label 'IP-Blocklist'" >> /tmp/rules.debug.tmp"Replace "echo "block quick from $i to <ipblocklist>label 'IP-Blocklist'" >> /tmp/rules.debug.tmp"
with "echo "block log quick from $i to <ipblocklist>label 'IP-Blocklist'" >> /tmp/rules.debug.tmp"So basically replace "block quick from" with "block log quick from"
Keep in mind that this forces logging on your outbound. Sometime in the near future I will push a minor update that will allow logging on IN and OUT traffic depending on your settings.
Note: for convert-execute.sh it's line 113 and for IP-Blocklist.sh it's line 118</ipblocklist></ipblocklist></ipblocklist>
-
Thank you so much, TommyBoy! I needed this to find what was being blocked and preventing me from playing modern warfare 2. =)
[EDIT]
Here is my whitelist to allow Ps3 online play. These were blocked by bt_level1.gz.
store.playstation.com:199.108.4.76-199.108.4.76
ena.net.playstation.net:198.107.158.197-198.107.158.198
ena.net.playstation.net:198.107.158.166-198.107.158.166
xmb.dl.playstation.net:208.111.185.235-208.111.185.235
xmb.dl.playstation.net:208.111.185.249-208.111.185.249 -
Can't uninstall ipblocklist…
I didn't find Countryblock right away, so installed ipblocklist instead...
After that, I found countryblock - and this was what I needed...ipblocklist is uninstalled, but still accessible from within the gui... can I remove it somehow ?
forgot to mention : i'm running it on the 1.2.3 platform, on a dual xeon server.
-
Can't uninstall ipblocklist…
I didn't find Countryblock right away, so installed ipblocklist instead...
After that, I found countryblock - and this was what I needed...ipblocklist is uninstalled, but still accessible from within the gui... can I remove it somehow ?
I think I know the problem. It's due to me changing the naming convention for 1.2.3 so I could push a differnt IP-Blocklist for BETA2.0.
You can edit your config.xml file and edit our the IP-Blocklist portion. Try re-installing and uninstalling if you're uncomfortable with editing your config. -
Don't mind fiddling within CONFIG.XML… I'll try this...
Uninstalling, re-installing and uninstalling didn't help yesterday... so i'll dig into the config.xml - thanks.I'll have to look into CountryBlock too- but I'll post the why's and how's in the other thread later on ;)
thank you for your reply.
-
Beginner problems here.
Usage
Add direct link to list and press (Example: Level1, Level2, Level3)
Compressed lists should have .gz extention and follows PeerBlock syntaxWarning! - Apply after firewall change or state reset. Use at your own risk.
Current Status = Running
You are blocking 0 Networks/IPs
Q: How do I know if the list got applied?
A: The package web interface will display the current status.
Links i've attempted to use
http://list11.iblocklist.com/files/bt_spyware.gz
http://iblocklist.whitacrecomputers.com/files/bt_level3.gz
and several other i've verified are in the correct format including small handmade lists hosted on the LANRunning Pfsense 1.2.3
Other packages installed: Dashboard
built on Sun Dec 6 23:21:36 EST 2009
FreeBSD 7.2-RELEASE-p5 i386Q: I have the "Enable" check box checked but I don't think its blocking any IPs
A: Any Errors will be at the bottom of the page when you press Save/Update
I get no error messages after Save/Update -
Same problem here on 1.2.3 Release
Doesn't block anything
Doesn't uninstall correctly, IP BlockList still available in menugot this in the log: Dec 5 14:05:45 root: IP-Blocklist was found not running
Usage Add direct link to list and press (Example: Level1, Level2, Level3) Compressed lists should have .gz extention and follows PeerBlock syntax Warning! - Apply after firewall change or state reset. Use at your own risk. Current Status = NOT running /tmp/rules.debug:87: cannot load "/usr/local/www/packages/ipblocklist/lists/ipfw.ipfw": No such file or directory You are blocking 0 Networks/IPsI uninstall, resintalled, uninstalled to no avail.
-
Same problem here on 1.2.3 Release
Doesn't block anything
Doesn't uninstall correctly, IP BlockList still available in menugot this in the log: Dec 5 14:05:45 root: IP-Blocklist was found not running
Usage Add direct link to list and press (Example: Level1, Level2, Level3) Compressed lists should have .gz extention and follows PeerBlock syntax Warning! - Apply after firewall change or state reset. Use at your own risk. Current Status = NOT running /tmp/rules.debug:87: cannot load "/usr/local/www/packages/ipblocklist/lists/ipfw.ipfw": No such file or directory You are blocking 0 Networks/IPsI uninstall, resintalled, uninstalled to no avail.
Yeah I just checked mine too. Uninstall does nothing
-
I will look into the uninstall problem tonight. As far as getting it running make sure your using direct links to lists. Try using one of the example lists.
