IP-Blocklist
-
I tried using the fetch method listed above, yet when I look at the IP Blocklist page it shows enabled, but that it's blocking 0 IP's (networks). Is that correct or is there a bug in the koolaid?
Also - will entries in the whitelist over-ride the entries in the blocklist? Just curious because I've noticed come sites that we normally access (online banking for example) are blocked in the level1 list.
Sort of confused….
thanks
Your list format is probably wrong. Look at the first post for the FAQ.
Entires in the the Whitelist do over-ride the blacklist. -
Got a really good question from ToxIcon!
tommyboy can i use this list with Ipblocklist
http://maliciousnetworks.org/fire-blocklist.txt
The answer is no. You the list syntax must follow COMMENT:xxx.xxx.xxx.xxx-xxx.xxx.xxx.xxx (The peerguardian format).
But I have good news it's really easy to convert your lists with Regex tools. I like to use http://gskinner.com/RegExr/ to convert my lists.Example:
The lists above has the format like:
109.108.130.188 AS8553
109.196.134.41 AS39150
109.196.143.33 AS39150
109.196.143.60 AS39150So using http://gskinner.com/RegExr/ do a find and replace. Paste your list into the body.
Do a find for \b\d{1,3}.\d{1,3}.\d{1,3}.\d{1,3}\b
and replace with \nSPAM:$&-$&We end up with:
SPAM:109.108.130.188-109.108.130.188 AS8553
SPAM:109.196.134.41-109.196.134.41 AS39150
SPAM:109.196.143.33-109.196.143.33 AS39150
SPAM:109.196.143.60-109.196.143.60 AS39150Now you need to remove the AS8553 part, so we do another find and replace with the output you have (copy the output back into the main body).
Do a find for AS
and replace with #$&Your output should look like:
SPAM:109.108.130.188-109.108.130.188 #AS8553
SPAM:109.196.134.41-109.196.134.41 #AS39150
SPAM:109.196.143.33-109.196.143.33 #AS39150
SPAM:109.196.143.60-109.196.143.60 #AS39150So there you have it ToxIcon. Using regex you can convert any lists into the proper format that is supported by the package.
-
IPBlocklist works great on 2 of my pfSense boxes.
One other pfSense box is a problem. I can't seem to get IPBlocklist going.
All are pfSense 2.0-BETA4.
The problem box is currently 2.0-BETA4 (i386)
built on Sat Nov 6 00:43:13 EDT 2010On the problem box, I've install IP-Blocklist every couple of months or so (back to pfSense 2.0-BETA1). Problem box remains a problem.
I use FF. The package installs without error.
I then…
1. Paste my list link into the form and press '+'.
( ex: http://iblocklist.charlieprice.org/files/bt_spyware.gz - I've tried several good .gz links.)
2. Check 'Enable IP-Blocklist.
3. Click Save/Update.Then the 'Current List' disappears entirely.
(I can bring it back by pressing '+', but that doesn't effect anything.)My Status is always....
Current Status = Running
You are blocking 0 IPs
I have tried every possible combination of buttons; Save, Save/Update, etc.
I have uninstalled Country Block (the only other package) and tried IPBlocklist by itself.
I have tried rebooting between installs and configs.
I have tried a number of different versions of pfSense 2.0-BETA.My results have been 100% consistent. Status Running - Blocking 0 IPs.
I'm uncertain on what to try, or where to look next.
If you or anyone else, have any thoughts, I'd be grateful to hear them.Thanks.
NVPS - a note:
At one location, spam rates are down by over 50%.
At another; I haven't had a single drive-by malware episode (were regular occurrences).
I credit CountryBlock as an important part of that result.
Thanks again. -
IPBlocklist works great on 2 of my pfSense boxes.
One other pfSense box is a problem. I can't seem to get IPBlocklist going.
All are pfSense 2.0-BETA4.
The problem box is currently 2.0-BETA4 (i386)
built on Sat Nov 6 00:43:13 EDT 2010On the problem box, I've install IP-Blocklist every couple of months or so (back to pfSense 2.0-BETA1). Problem box remains a problem.
I use FF. The package installs without error.
I then…
1. Paste my list link into the form and press '+'.
( ex: http://iblocklist.charlieprice.org/files/bt_spyware.gz - I've tried several good .gz links.)
2. Check 'Enable IP-Blocklist.
3. Click Save/Update.Then the 'Current List' disappears entirely.
(I can bring it back by pressing '+', but that doesn't effect anything.)My Status is always....
Current Status = Running
You are blocking 0 IPs
I have tried every possible combination of buttons; Save, Save/Update, etc.
I have uninstalled Country Block (the only other package) and tried IPBlocklist by itself.
I have tried rebooting between installs and configs.
I have tried a number of different versions of pfSense 2.0-BETA.My results have been 100% consistent. Status Running - Blocking 0 IPs.
I'm uncertain on what to try, or where to look next.
If you or anyone else, have any thoughts, I'd be grateful to hear them.Thanks.
NVPS - a note:
At one location, spam rates are down by over 50%.
At another; I haven't had a single drive-by malware episode (were regular occurrences).
I credit CountryBlock as an important part of that result.
Thanks again.Are all boxes using the same build version? I tested the list and it works fine. The only thing that I can think of is that pfSense 2.0-BETA4 is just that, BETA so I can't vouch for how the package is being handled in that particular version.
I don't have a 2.0BETA4 box to test with so unfortunately you or someone else is going to have to test. I'm glad that SPAM is down and thank you for your support.
I wish I had a better answer for you but I don't have any resources to test 2.0BETA4 right now. -
IPBlocklist works great on 2 of my pfSense boxes.
One other pfSense box is a problem. I can't seem to get IPBlocklist going.
All are pfSense 2.0-BETA4.
The problem box is currently 2.0-BETA4 (i386)
built on Sat Nov 6 00:43:13 EDT 2010 …Are all boxes using the same build version? I tested the list and it works fine. The only thing that I can think of is that pfSense 2.0-BETA4 is just that, BETA so I can't vouch for how the package is being handled in that particular version.
I don't have a 2.0BETA4 box to test with so unfortunately you or someone else is going to have to test. I'm glad that SPAM is down and thank you for your support.
I wish I had a better answer for you but I don't have any resources to test 2.0BETA4 right now.OK. That is an answer, if not precisely one I was fishing for.
FYI, all 3 are different build dates; all within 40 days of now.
Today, I moved the drive from a PIII ThinkPad to a P4 Inspiron and wiped/reloaded pfSense.
After the preliminary setup, I loaded IP-Blocklist as the first package and… same result.At least we know it can work in pfSense 2. I suspect one day we'll also know how.
Thanks for the reply.
NV
-
~~WARNING: Duplicate entries per list cancel out
I just found something that could be a problem if you make your own lists. If you make your own list like I do and you accidentally have a duplicate entry in the list it will cancel out and will not be blocked. This is a bug that is caused by the Perl script that interprets your lists.
Example duplication:
unkn:194.71.107.25-194.71.107.25
ad:194.71.107.25-194.71.107.25This will result in the IP not being blocked. The Fix: Just be careful when creating your own lists. If your paranoid run you "sort happybirthday.txt | uniq
" your lists!Again this will only apply to people that make their own lists. Publishers of official IP lists filter for duplicates for you.~~
This bug is fixed. Duplicate lists are not an issue any longer!
-
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.
