IP-Blocklist
-
YahOOO
I'm not certain which format worked, but I am no blocking 64 IP addresses.
Tommy, YOU ARE A HERONow, why won't the I-Block list list work??
Not as important as having my list work, I can assure you.
Thank you
-
YahOOO
I'm not certain which format worked, but I am no blocking 64 IP addresses.
Tommy, YOU ARE A HERONow, why won't the I-Block list list work??
Not as important as having my list work, I can assure you.
Thank youGlad that's working.
So the I-Blocklist.com list url is http://list.iblocklist.com/?list=rynxmrknfjysesjtjlxy&fileformat=p2p&archiveformat=gz&id=ljbowdish&pin=2728 but when you open this list in a browser it redirects to http://list.iblocklist.com/f/sgtbrdkspntjshbzbimf/rynxmrknfjysesjtjlxy.gzSo http://list.iblocklist.com/f/sgtbrdkspntjshbzbimf/rynxmrknfjysesjtjlxy.gz is your true URL. I-Blocklist uses multiple mirrors to host files and the first link is just a refferer to the mirror list. The second url is where that link takes you, to the .gz file.
The version of fetch on pfsense doesn't follow links intelligently which requires users to find the true URL. Pro tip: Open the I-Blocklist.com link in a browser and download the file. Go back into the download history and copy the URL where the download came from. This is the True URL.
-
Glad that's working.
So the I-Blocklist.com list url is http://list.iblocklist.com/?. Pro tip: Open the I-Blocklist.com link in a browser and download the file. Go back into the download history and copy the URL where the download came from. This is the True URL.A tip from a PRO. Thank you.
-
lol. Perhaps one day I may get around this by using wget, but I don't like adding bells and whistles unless you need to. KISS is how you get stable packages.
Maybe fetch will get an upgrade one day, but until then the user will have to ensure they have the true URL. Once you have that URL, you don't have to worry about that list anymore.Thank you for your time sir and your generous donation!
-
p2p format?? That's what I downloaded.
I saw something about CDIR format. Which is preferred?? -
p2p format?? That's what I downloaded.
I saw something about CDIR format. Which is preferred??p2p format is the only supported format right now. Soon, the package will move to CIDR only.
I created a poll on this. It has a list of pro's and con's and is still open for voting
http://forum.pfsense.org/index.php/topic,39649.0.html -
If this has already been asked, I apologize, but I'm wondering: Is there a best practice for blocking domains? While searching for blocklists, I found a very extensive collection but it only listed the domains, not the actual IP's.
-
If this has already been asked, I apologize, but I'm wondering: Is there a best practice for blocking domains? While searching for blocklists, I found a very extensive collection but it only listed the domains, not the actual IP's.
Not sure on that one. It seems like a simple thing to script though. Feed a list of domains and for each domain ping it to have DNS resolve the IP and output that into an IP list. Should be less than 10 lines to script.
-
This seems to be a never ending battle. I'm adding 20-30 Ip's every night.
Is there a better list?? -
This seems to be a never ending battle. I'm adding 20-30 Ip's every night.
Is there a better list??Context? List for what and why are IP's being added every night?
-
I really want to get this to work… I've tried all the suggestions in this thread, but nothing seems to work. Host package locally, get true URL, reinstall pfsense from scratch, and so on...
What happens is this: I add the URL, click 'save/update', and nothing. No update, no page activity, nada. I've left it for hours and it just sits there. Am I missing something? If I'm just dense, please let me know, but I don't see any obvious fix for this issue in the forum. Flame away if there is a fix and I missed it... Thanks!
-
What version of pfsense are you running?
Can you provide a sample list (url)?-
Ensure the Enable checkbox is checked before you click save/update
-
Use firefox or Chrome. IE is not supported
-
-
i tried to uninstall the package. in the log i get :
php: : The command '/usr/local/pkg/pf/IP-Blocklist.sh start' returned exit code '2', the output was 'not running root: IP-Blocklist was found not running 0 table deleted. 0 table deleted. rm: /tmp/rules.debug.tmp: No such file or directory /usr/local/pkg/pf/IP-Blocklist.sh: cannot create /usr/local/www/packages/ipblocklist/errorOUT.txt: No such file or directory rm: /tmp/rules.debug.tmp: No such file or directory 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 cat: /usr/local/www/packages/ipblocklist/interfaces.txt: No such file or directory 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 15
using pfsense 2.1-ipv6 (today snapshot)
-
What happens when you reboot and then try to uninstall?
-
What version of pfsense are you running?
Can you provide a sample list (url)?-
Ensure the Enable checkbox is checked before you click save/update
-
Use firefox or Chrome. IE is not supported
Looks like I found the problem. I only use IE ;) But for brevity, I am using bleeding-edge pfsense. The URLs are the true redirect URLs, and I also hosted a package on my web server but was still unable to get it to update. I'll go ahead and try with a portable version of FF and see how it goes. Thanks for the assist!
-
-
What version of pfsense are you running?
Can you provide a sample list (url)?-
Ensure the Enable checkbox is checked before you click save/update
-
Use firefox or Chrome. IE is not supported
Looks like I found the problem. I only use IE ;) But for brevity, I am using bleeding-edge pfsense. The URLs are the true redirect URLs, and I also hosted a package on my web server but was still unable to get it to update. I'll go ahead and try with a portable version of FF and see how it goes. Thanks for the assist!
IE was the cause. Tried Chrome portable and the rules updated like magic. Thanks for the assist!
-
-
No problem!
-
Hi, I'm getting this error message on the latest RC3 embedded builds:
"Warning: fopen(lists.txt): failed to open stream: Read-only file system in /usr/local/www/packages/ipblocklist/ipblocklist_list.php on line 69 Warning: fclose(): supplied argument is not a valid stream resource in /usr/local/www/packages/ipblocklist/ipblocklist_list.php on line 75 "
-
Hey Tom,
I see the package has come a long way since we first spoke. I might have lost a bit track of the project and have some questions ;)
Did you now completely remove the email function or are you running it trough pfSense its own email routine?
Is there an auto update function so it automatically downloads new lists every night?
And probably one request i look for the most, whitelist a single ip or a range of ips instead of using lists. Some of the ips i need to access are blacklisted as part of a complete range which actually makes no sense but they are probably better save then sorry. So a whitelist function as with snort would be very nice!-m4rcu5
-
Hey Tom,
I see the package has come a long way since we first spoke. I might have lost a bit track of the project and have some questions ;)
Did you now completely remove the email function or are you running it trough pfSense its own email routine?
Is there an auto update function so it automatically downloads new lists every night?
And probably one request i look for the most, whitelist a single ip or a range of ips instead of using lists. Some of the ips i need to access are blacklisted as part of a complete range which actually makes no sense but they are probably better save then sorry. So a whitelist function as with snort would be very nice!-m4rcu5
Hello.
I completely removed the email function. It is no longer required. Email was used as a tool to be notified when the package stopped working. This is not the case with the newer versions since the package is very stable now.
Auto updating takes place on it's own. Every time your filter is modified, reloaded, etc. the package will re-download the lists and re-apply them. Filter reloads happen several times a day without any user intervention.
As far as the whitelist a single IP or range: You will have to create a custom list. It's really easy and you can host it on your pfsense router! It's the best of both worlds. The whitelist functionality is already there, you just have to maintain your own list and it's real easy to do so.
