PfBlocker
-
version 0.1.4 is almost done.
some fixes and new gui options will be included for even more control on lists.
-
Yeah that dawned on me after I posted ;) If your running any sort of service that is open to the public, email/web/ntpd/ftp/etc then yeah it makes sense.. Might have to give it a test run, what would be nice is if it logged hits to this rule in a different log vs just firewall log so could see what kind of traffic getting from the bad IPs – for curiosity sake.
I don't really run anything open to the public other than p2p and ntpd (pool.ntp member) My ssh and openvpn access is locked down to require cert, etc. So no issue with bruteforce and and have linux box that runs sshd blocking IPs on 4 bad attempts anyway to keep the logs from filling up.
-
If possible could you add in block lists for the following hostile lists:
- Russian Business Network (bad), dshield and botnet CnCs - http://rules.emergingthreats.net/fwrules/emerging-Block-IPs.txt
- Compromised hosts - rules.emergingthreats.net/blockrules/compromised-ips.txt
- Russian business network malvertisers - http://rules.emergingthreats.net/blockrules/rbn-malvertisers-ips.txt
- Ciarmy list - http://ciarmy.com/
I blocked these inbound and outbound on my firewall already by linking a URL alias to these lists so it downloads them and then put that Alias in a block all traffic to and from on LAN & WAN interfaces and that stops my network talking to these IPs.
It would be nice though to have a tool where I could say click to block them and it will put the correct block in the firewall. You can get seperate lists for Dshield, RBN etc. I think this would help extend lots of blocking capabilities of bad hosts, malware command and control servers, bad servers distributing malware etc to normal users.
-
If possible could you add in block lists for the following hostile lists:
- Russian Business Network (bad), dshield and botnet CnCs - http://rules.emergingthreats.net/fwrules/emerging-Block-IPs.txt
- Compromised hosts - rules.emergingthreats.net/blockrules/compromised-ips.txt
- Russian business network malvertisers - http://rules.emergingthreats.net/blockrules/rbn-malvertisers-ips.txt
- Ciarmy list - http://ciarmy.com/
I blocked these inbound and outbound on my firewall already by linking a URL alias to these lists so it downloads them and then put that Alias in a block all traffic to and from on LAN & WAN interfaces and that stops my network talking to these IPs.
It would be nice though to have a tool where I could say click to block them and it will put the correct block in the firewall. You can get seperate lists for Dshield, RBN etc. I think this would help extend lots of blocking capabilities of bad hosts, malware command and control servers, bad servers distributing malware etc to normal users.
It will be in version 0.1.4. these lists has only single ips.
-
The first one (http://rules.emergingthreats.net/fwrules/emerging-Block-IPs.txt) is a mix of single IPs and CIDR, apparently discrete lists concatenated one after another.
-
The first one (http://rules.emergingthreats.net/fwrules/emerging-Block-IPs.txt) is a mix of single IPs and CIDR, apparently discrete lists concatenated one after another.
That list seems to be a combination of some lists on iblocklist.com. It looks like it's already available in a format that pfblocker could use in version 1.3.
Check iblocklist.com for any lists that you want. I'm guessing chances are it's there. -
interesting package !
can I use all list with an Alix box ? (AMD Geode / 256 MB RAM), I use 37% of RAM on my system.
-
pfBlocker version 1.4 is out.
Main improvements:
-
Url Lists now has it's own tab and many new options, including reading local files instead of urls
-
Each continent as well top spammers has it's own alias and rule action.
-
pfBlocker now reads CIDR, ips and network rages on files/urls.
-
More intuitive way to choose action in lists.
-
More control checks to avoid pfctrl error messages
I will wait feedback about these changes and stability before coding update frequency lists.
We are almost there.
-
-
just updated to new version and there is a problem with widget
enabling it will cause other widgets (not all) not to be displayed (ex : interface statistics)
-
Congratulations guys! :)
This looks like an outstanding package. Genuinely useful.Steve
-
just updated to new version and there is a problem with widget
enabling it will cause other widgets (not all) not to be displayed (ex : interface statistics)
I will take a look.EDIT
Fixed. Reinstall package in about 15 minutes to get fixed widget file.
-
nice work!!! its working nicely on my 2.1-dev box
-
After a reboot, I did receive an error alert but the list still loaded:
There were error(s) loading the rules: /tmp/rules.debug:21: cannot load "/var/db/aliastables/pfBlockerTopSpammers.txt": No such file or directory /tmp/rules.debug:23: cannot load "/var/db/aliastablespfBlockerBadGuys.txt": No such file or directory pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [21]: table <pfblockertopspammers>persist file "/var/db/aliastables/pfBlockerTopSpammers.txt"</pfblockertopspammers> -
This happens when pfBlocker is running While filter reloads. Boot is one of these cases.
This is not a big deal as pfBlocker call filter reload when finish.
-
I figured it would be normal but wanted to share just in-case
-
I would recommend you to detect that you are at boot phase and do not don anything.
I generally do not like that packages call filter_configure() but rather would like packages to go and use pfctl themselves and exploit the anchors, though it needs more familiarity with pfctl.
-
just updated to new version and there is a problem with widget
enabling it will cause other widgets (not all) not to be displayed (ex : interface statistics)
I will take a look.EDIT
Fixed. Reinstall package in about 15 minutes to get fixed widget file.
thx, I confirm that it works now !
-
@ermal:
I would recommend you to detect that you are at boot phase and do not don anything.
OK, I will find a way.
@ermal:
I generally do not like that packages call filter_configure() but rather would like packages to go and use pfctl themselves and exploit the anchors, though it needs more familiarity with pfctl.
The first generation of this package (countryblock) was editing /tmp/rules.debug. cmd asked tommyboy to change the way package apply rules.
The fist idea to improve stability was using pfsense 2.0 native options to edit rules. So current version of pfblocker create aliases, rules and then apply with filter_configure(). This was the best way I found to apply rules when users saves pfBlocker's conf. -
Great package. I have installed the latest version and I am wondering what happened to the deny inbound/outbound option? There are cases where you may block traffic to and from these countries (like countries which both do a lot of attacks, spam etc and host a lot of malware you do not want your users contacting. Is it possible to put that back in please? Thank you
-
Re-Installed 0.1.4 working fine
one detail … Package Info link still points to Country Block http://forum.pfsense.org/index.php/topic,25732.0.html
