IP-Blocklist
-
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.
-
I tried all three lists on the configuration page to no avail.
-
IP-Blocklist 3.0.1 released!
fixed uninstall problem.
updated perl to 5.12
updated netCIDR to 0.14pfsense 1.2.3 has been tested.
pfsense 2.0BETA not tested.
Completely uninstall IP-Blocklist. If you still have a link for IP-Blocklist then run "rm -R /usr/local/www/packages/ipblocklist" and "rm /usr/local/etc/rc.d/IP-Blocklist.sh" before re-installing 3.0.1
-
You are all kinds of awesome. Started working right away.
Thanks -
-
So I rm the package rm -R /usr/local/www/packages/ipblocklist" and "rm /usr/local/etc/rc.d/IP-Blocklist.sh"
I reinstalled, doesn't block any .gz listRemoved, uninstallation went fine, the menu are not present in Firewall menu :)
Install again, still You are blocking 0 Networks/IPs
I modified /etc/inc/config.inc from 128MB to 256M and /usr/local/lib/php.ini from 32M to 128M
no change (not sure if I have to reboot or not)Uninstall is my next move
-
So I rm the package rm -R /usr/local/www/packages/ipblocklist" and "rm /usr/local/etc/rc.d/IP-Blocklist.sh"
I reinstalled, doesn't block any .gz listRemoved, uninstallation went fine, the menu are not present in Firewall menu :)
Install again, still You are blocking 0 Networks/IPs
I modified /etc/inc/config.inc from 128MB to 256M and /usr/local/lib/php.ini from 32M to 128M
no change (not sure if I have to reboot or not)Uninstall is my next move
Uninstall the package from your package manager page and then re-install. That should do it. The rm -R command was only for those that still had a link after uninstalling and still had the package installed.
-
It seem to working perfectly, without any issues. However, how do I know it's actively blocking in real time, is there's a way to monitor this similar to logfile? I enabled Logging, and I don't see it under Status > System Logs
-
hm, I seem to be failing at everything, lol.
Uninstall IP-Blocklist OK, but link remains.
Executed the CL as suggested above to remove the link, and the link remains (when clicked, 404 - Not Found). Reboot / reinstall / uninstall in any/every order doesn't seem to help, IP-Blocklist 3.0 keeps installing (instead of 3.0.1), and Running, but Blocking = 0 Networks.
-
An old config is preventing you from getting the new version. I forget where the directory is but I think it somewhere near /usr/etc/pkgs or something like that. Just delete everything IP-Blocklist/ipblocklist.
I can't tell for sure since I'm away from home right now (working on my CCENT/CCNA). If you can't get it working let me know, I can probably get a VM of pfsense up if I need to.
-
just a small feature request, can you add this to bottom of whitelist page like "You're currently unblocking #### IPs"
-
Found a cpl ipblockist.* in /usr/local/pkg -deleted them, same prob(s) still exist - no worries though, thanks for the tip :)
-
An old config is preventing you from getting the new version. I forget where the directory is but I think it somewhere near /usr/etc/pkgs or something like that. Just delete everything IP-Blocklist/ipblocklist.
I can't tell for sure since I'm away from home right now (working on my CCENT/CCNA). If you can't get it working let me know, I can probably get a VM of pfsense up if I need to.
Hey good buddy. I was on a wicked old version, like 2.2.1, something like that. I am having no luck getting the latest to work for me. I tried looking all over the fs, using your other awesome package btw, and couldn't find anything in terms of remnants from a past config.
The newest package installs fine, but when I add .gz lists I still have 0 showing for number of blocks with service Running. Any ideas? Thanks again!
-
An old config is preventing you from getting the new version. I forget where the directory is but I think it somewhere near /usr/etc/pkgs or something like that. Just delete everything IP-Blocklist/ipblocklist.
I can't tell for sure since I'm away from home right now (working on my CCENT/CCNA). If you can't get it working let me know, I can probably get a VM of pfsense up if I need to.
Hey good buddy. I was on a wicked old version, like 2.2.1, something like that. I am having no luck getting the latest to work for me. I tried looking all over the fs, using your other awesome package btw, and couldn't find anything in terms of remnants from a past config.
The newest package installs fine, but when I add .gz lists I still have 0 showing for number of blocks with service Running. Any ideas? Thanks again!
I have some ideas. First are you using 1.2.3 or the BETA 2.0? I have been having problems keeping this package working smoothly for those with BETA2.0. Someone was kind enough to agree to send me a laptop for development but unfortunately it hasn't arrived yet.
If you're on 1.2.3 then we should be able to figure it out quickly. Just to confirm you have IP-Blocklist ver 0.3.0 or 0.3.1 correct?
Can you try this .gz file: http://iblocklist.dbnservers.net/files/bt_ads.gz Just to be sure.Edit: By the way thank you for your suggestion for a whitelist feature a long time ago. I hope you can enjoy the package here soon.
-
I was very excited to see the whitelist! I can't wait to start using it. I have been plenty happy with the package so far, as you can tell, I haven't upgraded since I first installed it :)
I am on pfSense 1.2.3 with IP Blocklist 0.3.1 and I did as you suggested, adding this list: http://iblocklist.dbnservers.net/files/bt_ads.gz
Still shows running with 0 blocked.
-
I was very excited to see the whitelist! I can't wait to start using it. I have been plenty happy with the package so far, as you can tell, I haven't upgraded since I first installed it :)
I am on pfSense 1.2.3 with IP Blocklist 0.3.1 and I did as you suggested, adding this list: http://iblocklist.dbnservers.net/files/bt_ads.gz
Still shows running with 0 blocked.
This might be a really stupid question but do you have the enable check box checked before clicking save?
SSH in to your system and check the contents of /usr/local/www/packages/ipblocklist/lists The .gz file should be in that directory if it got downloaded correctly. Also check the contents of /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw and see if there is anything in there.
-
No worries man.
Yes the box is checked to enable.
# ls -l /usr/local/www/packages/ipblocklist/lists total 132 -rw-r--r-- 1 root wheel 133982 Dec 30 18:00 bt_ads -rw-r--r-- 1 root wheel 0 Dec 30 22:25 ipfw.ipfw # -
So it looks like the ads file does get downloaded but for some reason it's not being processed to ipfw.ipfw.
Check the format of the bt_ads file. If it looks good then run /usr/local/www/packages/ipblocklist/convert-execute.sh from the command line manually so you can see any errors if any.
