IP-Blocklist
-
Wow i did this whole write up on squid and forgot I am in the IP-blocklist thread. ::) Think I forget because when IP-blocklist is successful, access denied gets shoved into a squid page.
quick question, is it logged somewhere when somebody is blocked ?
-
Wow i did this whole write up on squid and forgot I am in the IP-blocklist thread. ::) Think I forget because when IP-blocklist is successful, access denied gets shoved into a squid page.
quick question, is it logged somewhere when somebody is blocked ?
lol :)
To answer the question, it goes into the firewall logs if you checked logging.
-
Sorry, I just saw it after I asked my question
-
Hey Tommyboy, any luck on getting IE to function with this? I personally use chrome but I want to implement some IP block stuff in a work environment where all they use is IE.
-
Hey Tommyboy, any luck on getting IE to function with this? I personally use chrome but I want to implement some IP block stuff in a work environment where all they use is IE.
I've tried to work with IE and it just wont work with me. I kicked it to the curb. If you absolutely need IE then see if the new IE BETA will work.
-
Some of the popular blacklists on the internet change very often. Is it possible to add a setting for IP-Blocklist to reload the blacklists automatically at a period specified by the user?
-
Some of the popular blacklists on the internet change very often. Is it possible to add a setting for IP-Blocklist to reload the blacklists automatically at a period specified by the user?
This has already been answered within this Topic. Please search the topic for the answer you are looking for.
-
I was thinking more along the line of user-friendly web-based GUI setting. With that said, setting up a cron job will works for me.
Thanks
-
I was thinking more along the line of user-friendly web-based GUI setting. With that said, setting up a cron job will works for me.
Thanks
I could build a GUI for it but the work is already done for me by the Cron Job package. Perhaps I could integrate. Not sure where I want to go with that. We'll see.
-
I'm running an embedded install of 2.0Beta5 and tried to make the changes listed in this thread in order to get it to work. However, I accidentally forgot a semicolon after the first line I added (require_once('config.inc')) and when I went to refresh the IP-Blocklist page I got the following error in the textbox:
Parse error: syntax error, unexpected T_ECHO in /usr/local/www/packages/ipblocklist/ipblocklist_list.php on line 5
Since then, I've tried everything I can to get back to a cleanly-installed state: I've undone the edits I made to that file, and I've even uninstalled and reinstalled the IP-Blacklist package, but whatever I do, I now always get that error. How can I get back to a clean slate without completely reinstalling pfsense?
-
I'm running an embedded install of 2.0Beta5 and tried to make the changes listed in this thread in order to get it to work. However, I accidentally forgot a semicolon after the first line I added (require_once('config.inc')) and when I went to refresh the IP-Blocklist page I got the following error in the textbox:
Parse error: syntax error, unexpected T_ECHO in /usr/local/www/packages/ipblocklist/ipblocklist_list.php on line 5
Since then, I've tried everything I can to get back to a cleanly-installed state: I've undone the edits I made to that file, and I've even uninstalled and reinstalled the IP-Blacklist package, but whatever I do, I now always get that error. How can I get back to a clean slate without completely reinstalling pfsense?
My best advice is to uninstall the package, check the file system (/usr/local/www/ipblocklist) and delete it, and then reboot. That should help you start from a clean slate.
-
I'm running an embedded install of 2.0Beta5 and tried to make the changes listed in this thread in order to get it to work. However, I accidentally forgot a semicolon after the first line I added (require_once('config.inc')) and when I went to refresh the IP-Blocklist page I got the following error in the textbox:
Parse error: syntax error, unexpected T_ECHO in /usr/local/www/packages/ipblocklist/ipblocklist_list.php on line 5
Since then, I've tried everything I can to get back to a cleanly-installed state: I've undone the edits I made to that file, and I've even uninstalled and reinstalled the IP-Blacklist package, but whatever I do, I now always get that error. How can I get back to a clean slate without completely reinstalling pfsense?
My best advice is to uninstall the package, check the file system (/usr/local/www/ipblocklist) and delete it, and then reboot. That should help you start from a clean slate.
Hmm, after uninstalling I looked in /usr/local/www/ and there was no file or directory ipblocklist. I then rebooted, and reinstalled the package. Same exact error as before. The strange thing, is that if I look at the file /usr/local/www/packages/ipblocklist/ipblocklist_list.php, it's the stock, unmodified form (i.e., correct syntax)!? I'm very confused as to what's going on.
-
I'm running an embedded install of 2.0Beta5 and tried to make the changes listed in this thread in order to get it to work. However, I accidentally forgot a semicolon after the first line I added (require_once('config.inc')) and when I went to refresh the IP-Blocklist page I got the following error in the textbox:
Parse error: syntax error, unexpected T_ECHO in /usr/local/www/packages/ipblocklist/ipblocklist_list.php on line 5
Since then, I've tried everything I can to get back to a cleanly-installed state: I've undone the edits I made to that file, and I've even uninstalled and reinstalled the IP-Blacklist package, but whatever I do, I now always get that error. How can I get back to a clean slate without completely reinstalling pfsense?
My best advice is to uninstall the package, check the file system (/usr/local/www/ipblocklist) and delete it, and then reboot. That should help you start from a clean slate.
Hmm, after uninstalling I looked in /usr/local/www/ and there was no file or directory ipblocklist. I then rebooted, and reinstalled the package. Same exact error as before. The strange thing, is that if I look at the file /usr/local/www/packages/ipblocklist/ipblocklist_list.php, it's the stock, unmodified form (i.e., correct syntax)!? I'm very confused as to what's going on.
Sorry. The directory is /usr/local/www/packages/ipblocklist/
Uninstall and check to make sure that it's deleted.
Try executing the .sh manually in your console if you get the same error again. -
Did we ever resolve the IP Blocklist service having this:
Current Status = NOT running
You are blocking 0 Networks/IPs
Even though the "Enable IP-Blocklist" is checked? It seems to happen after some period of time… haven't figured out how long, usually I check each day and it seems consistent.
I'm using embedded, don't know if its specific to this. (1.2.3-release)
-
Did we ever resolve the IP Blocklist service having this:
Current Status = NOT running
You are blocking 0 Networks/IPs
Even though the "Enable IP-Blocklist" is checked? It seems to happen after some period of time… haven't figured out how long, usually I check each day and it seems consistent.
I'm using embedded, don't know if its specific to this.
embedded doesn't like my package for some reason. Let me take some time to get an embedded environment running to get a fix for you here soon. Thanks.
-
Tommyboy we luv ya man. ;D
Did we ever resolve the IP Blocklist service having this:
Current Status = NOT running
You are blocking 0 Networks/IPs
Even though the "Enable IP-Blocklist" is checked? It seems to happen after some period of time… haven't figured out how long, usually I check each day and it seems consistent.
I'm using embedded, don't know if its specific to this.
embedded doesn't like my package for some reason. Let me take some time to get an embedded environment running to get a fix for you here soon. Thanks.
-
Tommyboy we luv ya man. ;D
Did we ever resolve the IP Blocklist service having this:
Current Status = NOT running
You are blocking 0 Networks/IPs
Even though the "Enable IP-Blocklist" is checked? It seems to happen after some period of time… haven't figured out how long, usually I check each day and it seems consistent.
I'm using embedded, don't know if its specific to this.
embedded doesn't like my package for some reason. Let me take some time to get an embedded environment running to get a fix for you here soon. Thanks.
I'm having trouble getting an embedded vm running. Is there an easy way to get embedded going within vmware?
-
Tommyboy, because the embedded is an image file, I use physdiskwrite to slap the .img file onto a flash disk. I always reference this howto as well:
http://pfsense.phoenixkv.net///tutorials/wrap_install/wrap_install.htm
You would probably have to mount the virtual disk made by vmware as a drive on your PC for physdiskwrite to detect it as a drive/partition. Or something of this nature. I am assuming you're trying to mount it like you would an ISO image and that won't fly. Or maybe you're farther ahead than this. I am not sure.
Tommyboy we luv ya man. ;D
Did we ever resolve the IP Blocklist service having this:
Current Status = NOT running
You are blocking 0 Networks/IPs
Even though the "Enable IP-Blocklist" is checked? It seems to happen after some period of time… haven't figured out how long, usually I check each day and it seems consistent.
I'm using embedded, don't know if its specific to this.
embedded doesn't like my package for some reason. Let me take some time to get an embedded environment running to get a fix for you here soon. Thanks.
I'm having trouble getting an embedded vm running. Is there an easy way to get embedded going within vmware?
-
Hello,
I have install Ip-Blocklist package ver:0.3.1 on my pfsense ver: 1.2.3-RELEASE
I have setting more ip list ( http://iblocklist.charlieprice.org/files/bt_spyware.gz , http://iblocklist.charlieprice.org/files/tbg_bogon.gz etc etc.. )All it's OK from the gui interface install and update.
The problem it's for automic list update :
i have comment out lines 3-14 of this file : /usr/local/etc/rc.d/IP-Blocklist.sh
i have do a cron to execute daly : /usr/local/etc/rc.d/IP-Blocklist.shThe problem is when i execute this batch : /usr/local/etc/rc.d/IP-Blocklist.sh it juste update firewall rules and note my list.
This script not downlad all .gz file and not take a list live update.
Only this script update all lists : ipblocklist.php
And i have add this line to not have memory error : ini_set("memory_limit","128M");Do you have a solution to automatic realy uptade the lists ?
Without solution, i have think to execute the ipblocklist.php with php command line.
Excuse my english .Best regards.
-
Hello,
I have install Ip-Blocklist package ver:0.3.1 on my pfsense ver: 1.2.3-RELEASE
I have setting more ip list ( http://iblocklist.charlieprice.org/files/bt_spyware.gz , http://iblocklist.charlieprice.org/files/tbg_bogon.gz etc etc.. )All it's OK from the gui interface install and update.
The problem it's for automic list update :
i have comment out lines 3-14 of this file : /usr/local/etc/rc.d/IP-Blocklist.sh
i have do a cron to execute daly : /usr/local/etc/rc.d/IP-Blocklist.shThe problem is when i execute this batch : /usr/local/etc/rc.d/IP-Blocklist.sh it juste update firewall rules and note my list.
This script not downlad all .gz file and not take a list live update.
Only this script update all lists : ipblocklist.php
And i have add this line to not have memory error : ini_set("memory_limit","128M");Do you have a solution to automatic realy uptade the lists ?
Without solution, i have think to execute the ipblocklist.php with php command line.
Excuse my english .Best regards.
I think you have a couple options. You can invoke the php via command line with or you can put the fetch code into the .sh on your own. The php code downloads the lists since it's easy to use a loop in php, but by all means put the fetch loop into the shell code.
The memory error is normal. You can safely ignore it. It only happens when you use large lists. You can cut down the size of your lists, increase your php mem size, or just ignore it. Even with the error the script will still execute properly.