IP-Blocklist
-
Do you have to manually apply updated filters or does IP-Blocklist automatically refresh the list?
For example if I load a list from a site called www.sitelist.com/block.gz, will IP-Blocklist refresh everyday to get the lasted additions to this list?
The package will re-download the list every time it's applied. Without any modifications this could be every 5 minutes or once a day, this is because Ipblockist is re-applied on filter reload. Now if you need to make sure it's being downloaded every day then install a cron job.
I think it's safe to say that your package is re-applying the list every day or at least every other day.
-
Not really sure where I could get the logs to show what's going on. The situation is this.
IP-Blocklist works fine, but after a few hours, the whitelist is forgotten and it ignores it entirely. If I login to the router and hit "Save/Update", it'll start using the whitelist again. Obviously this isn't ideal. Any idea what I could do to figure out why it stops using it? I can't find any messages indicating that the whitelist isn't found, it's stored on the same server the blocklist is coming from…
-
I removed the IP-Blocklist and I get this error every time I reload the firewall filter. Is there anyway to manually remove it using the command-line? FYI, I also get this same error when I just disable the IP-Blocklist. :'(
Thanks,
Rhett
System Logs:
php: : The command '/usr/local/pkg/pf/IP-Blocklist.sh start' returned exit code '1', the output was 'not running root: IP-Blocklist was found not running Status: 404 Not Found Content-type: text/html No input file specified. 0 table deleted. 0 table deleted. ls: /usr/local/www/packages/ipblocklist/lists: No such file or directory rm: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/local/pkg/pf/IP-Blocklist.sh: cannot create /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/bin/sort: open failed: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory mv: rename /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP to /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory rm: /usr/local/www/packages/ipblocklist/Wlists/whitelistTEMP: No such file or directory /usr/bin/sort: open failed: Wlists/whitelist: No such file or directory rm: /tmp/rules.debug.tmp: No such fi -
I removed the IP-Blocklist and I get this error every time I reload the firewall filter. Is there anyway to manually remove it using the command-line? FYI, I also get this same error when I just disable the IP-Blocklist. :'(
Thanks,
Rhett
System Logs:
php: : The command '/usr/local/pkg/pf/IP-Blocklist.sh start' returned exit code '1', the output was 'not running root: IP-Blocklist was found not running Status: 404 Not Found Content-type: text/html No input file specified. 0 table deleted. 0 table deleted. ls: /usr/local/www/packages/ipblocklist/lists: No such file or directory rm: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/local/pkg/pf/IP-Blocklist.sh: cannot create /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP: No such file or directory /usr/bin/sort: open failed: /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory mv: rename /usr/local/www/packages/ipblocklist/lists/ipfw.ipfwTEMP to /usr/local/www/packages/ipblocklist/lists/ipfw.ipfw: No such file or directory rm: /usr/local/www/packages/ipblocklist/Wlists/whitelistTEMP: No such file or directory /usr/bin/sort: open failed: Wlists/whitelist: No such file or directory rm: /tmp/rules.debug.tmp: No such fitry rm -R /usr/local/www/packages/ipblocklist
Remove the xml and inc file from /usr/local/pkg
Also see if the start script is in /usr/local/rc.d -
Thank you for the information.
I deleted a file and things are working good again.
Looks like you need to have your uninstaller delete the following file:
/usr/local/pkg/pf/IP-Blocklist.sh -
Thank you for the information.
I deleted a file and things are working good again.
Looks like you need to have your uninstaller delete the following file:
/usr/local/pkg/pf/IP-Blocklist.shThank you. I will update that!
-
try rm -R /usr/local/www/packages/ipblocklist
Remove the xml and inc file from /usr/local/pkg
Also see if the start script is in /usr/local/rc.dHow to remove the xml and inc files using the webGUI? Also, I'm using windows and experience root2020's problem. TIA
-
The uninstaller seems to remove those two files. Do an uninstall via the GUI and then just remove the "/usr/local/pkg/pf/IP-Blocklist.sh"
Goto > Diagnotics > Command Line and type in the following
rm /usr/local/pkg/pf/IP-Blocklist.sh -
tnx. no more error on the syslog with ipblock… however, i have tx underrun. need to search the forum about that one.
Thanks again. ;) -
Hello,
samething with countryblock.sh
Thanks,
-
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.I can add to this. I was having the same issue with a mistype such that on the main tab there was a similar error message to Systex. An uninstall-manual flush/reinstall did nothing. I did not reboot however. What I have realized is that everything is fine but the message was stale and showing in the frame and this never refreshed. I right clicked on the frame and manually reloaded the frame where the error message was and this fixed everything for me as far as the display and the error message is concerned.
-
I got it installed with a couple of lists, when I check syslog i always get this message: "root: IP-Blocklist was found not running", if i goto Firewall > IP-Blocklist status says its running with a number of networks blocked, any idea what the issue here is?
Thank you
-
I got it installed with a couple of lists, when I check syslog i always get this message: "root: IP-Blocklist was found not running", if i goto Firewall > IP-Blocklist status says its running with a number of networks blocked, any idea what the issue here is?
Thank you
I think I may know what the issue is. I'm still doing work on the package but the binary files are no longer in the repo. This will be fixed very soon!
-
How does one create an importable whitelist? I play Guild Wars and NC interactive is blocked with Level-1 blacklist. I want to whitelist the subnets for Guild Wars, but have ended up beating my head on a brick wall trying to import. I don't have sufficient skills to edit within the Linux shell. Any other suggestions?
NC INTERACTIVE, INC:206.127.144.0-206.127.159.255
Thanks!
-
pfsense 2.0 R3
tommy can you fix the log for ipblocklist the
Enable Logging? does not stay enable once you click
save/update.Also was just wondering if you can make a
dashboard widget that can display the log files for
ipblocklist and country block so that we
can see what is being block thanks. something like to one for snort
and havp. -
pfsense 2.0 Rc3
built on Tue Jun 21 16:50:25 EDT 2011
Package does not block any IP.
System log (root: IP-Blocklist was found not running) -
Pfsense 2.0-RC3
tommyboy180 ip-blocklist will not update the list form iblocklist is it because they made some changes to the update url
like this address no longer seem to work http://iblocklist.aodcommunity.com/files/wujnnzxrgppvpdujdetm/bt_ads.gz
but if enter into a into a browser it downloads.
their new update format looks like this
http://list.iblocklist.com/?list=bt_ads&fileformat=p2p&archiveformat=gz
but when added to ip-blocklist it also does not download
their are no errors in the log for ip-blocklist.Thanks tommyboy180 for all the great work and great packages
-
Pfsense 2.0-RC3
tommyboy180 ip-blocklist will not update the list form iblocklist is it because they made some changes to the update url
like this address no longer seem to work http://iblocklist.aodcommunity.com/files/wujnnzxrgppvpdujdetm/bt_ads.gz
but if enter into a into a browser it downloads.
their new update format looks like this
http://list.iblocklist.com/?list=bt_ads&fileformat=p2p&archiveformat=gz
but when added to ip-blocklist it also does not download
their are no errors in the log for ip-blocklist.
Thanks tommyboy180 for all the great work and great packageshttp://iblocklist.taltos.org/files/wujnnzxrgppvpdujdetm/bt_ads.gz is the url for that file. To find the real url just download the file like normal in your browser and go back into your downloads and look at the url in your browser history.
I'm not sure how often the url scheme changes on that site so checking the url or saving it to a website you own may help with stability.
Thanks for your support! If you know php then perhaps we could work together on the project!
-
Tommyboy,
I have yet to upgrade to 2.0.x, as I will probably wait for final release (however I did test it and it looks great). This means I am still running 1.2.3.
I have recently worked with your latest, 0.3.2. As we've talked before in this thread, I do use the nanobsd (embedded) version and I do have a SATA 160GB drive mounted separately of the OS in my lil Soekris box. With the debugging/output that I think is now available (versus previous versions), I was able to modify all the scripts that were getting an error, not being able to write to the embedded file system, ie: read-only. Now they're all writing to my SATA drive and the IPblocklist package has been running for 72 hours without a crash. This is a lot better than before where the service would crash, or it would act silly, or whatever.
The files that needed to be written were files like: ipfw.ipfw, whitelist, and wlists.txt (i think thats all of them). (again once IPblocklist could write somewhere, it worked fine… maybe for embedded systems you could write it all to tmp? And then just have it reload them to tmp if the system gets reset?, not sure.), or where in the scripts it needs to write these files, invoke the /etc/rc.conf_mount_rw and then back /etc/rc.conf_mount_ro when done? (just a thought)
I am using a custom list that I created which basically just blocks 98% of all countries that I load from an internal webserver.
Maybe by now this whole thread includes this kind of information, or you probably already know.
I just wanted to say thanks. :)
-
Tommyboy,
I have yet to upgrade to 2.0.x, as I will probably wait for final release (however I did test it and it looks great). This means I am still running 1.2.3.
I have recently worked with your latest, 0.3.2. As we've talked before in this thread, I do use the nanobsd (embedded) version and I do have a SATA 160GB drive mounted separately of the OS in my lil Soekris box. With the debugging/output that I think is now available (versus previous versions), I was able to modify all the scripts that were getting an error, not being able to write to the embedded file system, ie: read-only. Now they're all writing to my SATA drive and the IPblocklist package has been running for 72 hours without a crash. This is a lot better than before where the service would crash, or it would act silly, or whatever.
The files that needed to be written were files like: ipfw.ipfw, whitelist, and wlists.txt (i think thats all of them). (again once IPblocklist could write somewhere, it worked fine… maybe for embedded systems you could write it all to tmp? And then just have it reload them to tmp if the system gets reset?, not sure.), or where in the scripts it needs to write these files, invoke the /etc/rc.conf_mount_rw and then back /etc/rc.conf_mount_ro when done? (just a thought)
I am using a custom list that I created which basically just blocks 98% of all countries that I load from an internal webserver.
Maybe by now this whole thread includes this kind of information, or you probably already know.
I just wanted to say thanks. :)
Excellent. Would you be interested in helping write code and take this package to the next level? I'm getting more busy every day with normal day-to-day things and my school work. I'm actually in an Oracle class right now away from home. If you want to help out and dedicate a couple hours a week to this project that would super awesome.
Have you considered using Countryblock to block just countries? You should find it more stable for embedded installs. There are a couple hosting companies that are using countryblock and they have found it to be quite stable.
When I am able to find the time I will release a new version that will detect if embedded and put the files that must be written to and read from in /tmp.
