IP-Blocklist
-
Hi again,
Will it be possible to enable blocking only for some IP's on local network? Let say that you want to allow or denied different blocklists for different IP's on network. So one IP on local network can access everything and another would be blocked according to blocklist.
It's possible now. Take a loot at the interface options. If you create another network then you can allow/deny lists to a specific network.
-
So if I understand you correctly, blocklists will work for specific computer on local network?
example:
-
Yes, if that computer is on a separate interface.
-
use browser GC or MF to reinstall.
IP-Blocklist Version 3.5 released!
blocklists are saved on system to ease updates
Corrected issues with uninstall
available for pfsense 2.0 -
i need to unblock facebook.com from iblock list.
i vi to usr/local/www/pakages/iblocklist/list/bt_level2.gz
del favebook inc: <ip address="">save / update
but squid still show block.
please guide.
many thanks</ip>
-
i need to unblock facebook.com from iblock list.
i vi to usr/local/www/pakages/iblocklist/list/bt_level2.gz
del favebook inc: <ip address="">save / update
but squid still show block.
please guide.
many thanks</ip>
Why not just create a whitelist with all Facebook IP's.
-
i need to unblock facebook.com from iblock list.
i vi to usr/local/www/pakages/iblocklist/list/bt_level2.gz
del favebook inc: <ip address="">save / update
but squid still show block.
please guide.
many thanks</ip>
Why not just create a whitelist with all Facebook IP's.
hi tommy , how to create the white list ? please help many thanks.
example . -
It's the same format as the blacklist.```
DESCRIPTION:xxx.xxx.xxx.xxx-xxx.xxx.xxx.xxxExample:``` Facebook:66.220.144.0-66.220.159.255
Store the whiltelist as a .txt on a webserver or the pfsense box and add it.
-
I have read all thread regarding to ipblocklist package, but didn't find the solution for the issue appeared some time here.
Have 2 pfsense boxes 2.0 and 1.2.3. Installed on both ipblocklist package. On 1.2.3 it works just fine, on 2.0 I got this error:
Current Status = NOT running
/tmp/rules.debug:31: Rules must be in order: options, normalization, queueing, translation, filtering
You are blocking 0 Networks/IPsI don't know how to get that fixed, as I'm not a bsd expert. I deinstalled the package, rebooted, installed it back - got the same result.
Any advise to right direction of getting it working to pfsense 2.0 ?Thanks.
-
I have read all thread regarding to ipblocklis package, but didn't find the solution for the issue appeared some time here.
Have 2 pfsense boxes 2.0 and 1.2.3. Installed on both ipblocklist package. On 1.2.3 it works just fine, on 2.0 I got this error:
Current Status = NOT running
/tmp/rules.debug:31: Rules must be in order: options, normalization, queueing, translation, filtering
You are blocking 0 Networks/IPsI don't know how to get that fixed, as I'm not a bsd expert. I deinstalled the package, rebooted, installed it back - got the same result.
Any advise to right direction of getting it working to pfsense 2.0 ?Thanks.
Try rebooting. If that doesn't work then list your installed packages.
-
Try rebooting. If that doesn't work then list your installed packages.
Thanks Tom,
I tried to reboot as I stated in my post. Removed, rebooted, installed back - the same results. Did a few times.
Here is my installed packages list (a lot of them are not relevant to the problem I think):
GeoIP-1.4.8_1
.. list of system packages was cut …
xproto-7.0.22 -
Sorry I meant to just list your installed pfsense packages.
-
Sorry I meant to just list your installed pfsense packages.
Bandwithd, Cron, IP-Blocklist, snort, RRD Summary.
-
Sorry I meant to just list your installed pfsense packages.
Bandwithd, Cron, IP-Blocklist, snort, RRD Summary.
Anyone can advise of what's wrong with that setup ? We run pfsense 2.0. Reboot didn't help. Thanks.
-
Sorry. I have plans to take a look at it. My work is undergoing an inspection that takes weeks so my priorities have temporarily shifted during this time. Hopefully I can take a look at it soon.
-
Hi,
is there any why to allow connection to blocked IP's on port 80? And if there is any way to manualy add my own IP's to whitelist? Let says that I like to unlock only one specific IP which is in blocklist.
This feature is implemented in pfBlocker package.
You can assign lists to populate an alias and then create your own rules if you want.
-
I have read all thread regarding to ipblocklist package, but didn't find the solution for the issue appeared some time here.
Have 2 pfsense boxes 2.0 and 1.2.3. Installed on both ipblocklist package. On 1.2.3 it works just fine, on 2.0 I got this error:
Current Status = NOT running
/tmp/rules.debug:31: Rules must be in order: options, normalization, queueing, translation, filtering
You are blocking 0 Networks/IPsI don't know how to get that fixed, as I'm not a bsd expert. I deinstalled the package, rebooted, installed it back - got the same result.
Any advise to right direction of getting it working to pfsense 2.0 ?Thanks.
Uninstall ipblocklist on 2.0 and try pfBlocker package.
-
Level1 list does not looks like bad guys, why its blocked by default?
-
I added the level1 list to demo the syntax of the URL. I constantly get questions on the forum why a URL isn't working and it's always because it's not the direct URL. Adding this as default has helped cut down on those problems.
If we can use wget or some option with fetch to follow the URL then this problem will be a thing of the past. For now though, the direct URL is required.
-
I've got a quick question about the package. Does IP Blocklist auto-update the block lists? Other than that, thanks for a great package!