PfBlocker
-
I have a problem where the inbound block rule does not get created for the included country lists. I have been installing and testing packages so i have installed havp and snort and uninstalled them and then reinstalled them again, due to trying to identify a problem. Outbound rules can still be created and the alias for both inbound and outbound are fine. But when i select inbound rule deny on the country lists pages it does not create the rule. Even if i stop pfblocker and remove all the lists and readd and then enable pfblocker, it creates the alias and the outbound block but not the rules on wan.
edit: Ok I added a random rule with port 123 on wan and then readded then the lists appeared in the rules and when i changed another country list to inbound deny it showed up. So maybe it is just my rules are not refreshing right and is not related to pfblocker.
-
You need at least one rule created to pfBlocker work on selected interface.
-
Running 2.0-RELEASE (i386) built on Tue Sep 13 17:00:00 EDT 2011 Intel(R) Xeon(TM) CPU 3.06GHz w/ 3gb RAM.
Just loaded and reloaded pfBlocker and I'm finding that if I set outbound to be blocked to spamlist I can still get to India or Russia located sites. Any idea what I might need to do. I have my firewall maximum table entries at 500000.
Thanks.
-
Running 2.0-RELEASE (i386) built on Tue Sep 13 17:00:00 EDT 2011 Intel(R) Xeon(TM) CPU 3.06GHz w/ 3gb RAM.
Just loaded and reloaded pfBlocker and I'm finding that if I set outbound to be blocked to spamlist I can still get to India or Russia located sites. Any idea what I might need to do. I have my firewall maximum table entries at 500000.
Thanks.
What are the sites?
-
194.226.127.34 - http://eng.kremlin.ru
203.199.104.241 - http://www.airindia.inand http://www.prodisney.ru/index.php?page=clones.php
-
Running 2.0-RELEASE (i386) built on Tue Sep 13 17:00:00 EDT 2011 Intel(R) Xeon(TM) CPU 3.06GHz w/ 3gb RAM.
Just loaded and reloaded pfBlocker and I'm finding that if I set outbound to be blocked to spamlist I can still get to India or Russia located sites. Any idea what I might need to do. I have my firewall maximum table entries at 500000.
Thanks.
Are you blocking countries India and Russia or applying a spamlist from ipblocklist?
Enable pfblocker widget. there you can see alias package count hit.
-
I have the spamlist all selected; I was assuming that if the country is in there the entire country would be blocked. Am I wrong?
I will take a look at the widget today.
Thanks!
-
The default way to block spam is inbound as you do not want them to send email to you.
You can also change action to alias only and create a block rule only on inbound smtp connections.
-
If i enable the top spammers alias included in pfblocker on outbound those hostnames you specified are not accessible.
-
If i enable the top spammers alias included in pfblocker on outbound those hostnames you specified are not accessible.
Top spammers is just a shortcut for countries that send many spams.
The best way to block this is changing action to alias only and create an inbound rule denying smtp connections.
-
I chose alias only and set outbound and inbound block; I'm still getting to the sites. The one interesting thing is that before I chose the option block outbound this morning I had it set to block inbound yesterday before I went home and when I loaded the widget this morning it had some packets listed. It doesn't have anything listed right now… I may need to reboot the server; I'll try that later on today.
-
There is no need to reboot, all rules are applied when you save config.
try this:
-
select only one country
-
apply
-
got to diagnostics -> table
-
select alias you applied country
-
check if the websites ip is in any of network CIDRS listed
Just to be sure you understand how rules work.
inbound rules -> applied on source side of wan rules
outbound rules -> applied on destination side of lan rules
Floating rules -> apply rules to block pfsense to reach something -
-
I don't know what is happening, but I just put a specific rule in place of the pfBlocker and the Indian site is still not getting blocked; could it be due to squid?
Thanks!
-
I don't know what is happening, but I just put a specific rule in place of the pfBlocker and the Indian site is still not getting blocked; could it be due to squid?
Thanks!Finally an answer. It's squid. :)
Create the same rule on floating rules.
Squid goes to internet using localhost, so lan rules will not match any squid access.
-
Okay, so question… do I need to have both WAN and LAN selected in the floating rule? I had just one and things seemed to still go through; with both the sites were blocked. I guess it could be that it's cached on my pc here, but I am getting things blocked on another pc with just LAN selected.
Thanks for your help marcelloc!
-
Well, it's time for first release.
pfblocker 1.0 is out. No changes from last beta version.
-
Congratulations! Excellent work marcelloc!
-
Another question… am I supposed to see numbers in the packets column? Mine are blank... Thanks.
-
Another question… am I supposed to see numbers in the packets column? Mine are blank... Thanks.
Numbers will appear only when you have applied rules to aliases pfBlocker creates.
Also post pfsense version and hardware used.
-
Numbers will appear only when you have applied rules to aliases pfBlocker creates.
Also post pfsense version and hardware used.
I have the status showing up and running ver 1.0 pfBlocker on pfSense 2.0 x86; I don't know what else to tell you.
-
I guess the PfBlocker Widget counters are built by scanning the Firewall rule descriptions.
When you use pfBlocker Aliasname in Firewall rules, you have to start the description with pfBlocker Aliasname for the widget to keep track.
in your case "pfBlockerAsia bla bla lba'
however, if you description end with 'rule' it would be recognized as auto generated and removed by pfblocker on save.
I've changed important note for better understanding.
Aliasname something rule will be removed by package.
-
@RonpfS - Thanks for the tip… I would have never figured that out! I at least have 0's showing up now; I'll see if they populate with numbers.
-
Sorry for that. I forgot to include this info in field description.
It will be there in next release.
-
Hey all!
I'm currently am running pfSense RC1 2.0 and Country Block. County Block works perfectly and is very easy to use for a novice like me.
Is pfBlocker as easy to use as County Block to block IPs from specific countries? Are there any documents on-line I can read to learn how to use pfBlocker? I'm upgrading to the latest version of pfSense 2.0 next week and don't want to have any problems.
Unlike everyone else here, I'm not a programming guru. I'm learning, but I have a long way to go!
Thanks! :D
-
Wow - I looked at the screen shots and this is easy to for anyone to use. I'm impressed.
A dumb question - are social networks like Facebook, Twitter, etc? Or is it something else?
-
take a look on ipblocklist website or any other that distribute lists.
If you now socialnetworks ip ranges, you have an option to include in custom list.
-
Hi,
installed the release totay on an Alix running nanobsd pfsense 2.0 - but get this:
Nov 18 20:55:24 kernel: pid 32813 (php), uid 0, was killed: out of swap space Nov 18 20:55:24 php: : [pfblocker] pfblocker_xmlrpc_sync.php is starting.
How do I get rid of the swap issue (RAM issue probably as nanobsd shouldn't swap - but the RAM is at 35% when this happens). Power LED of Alix keeps blinking.
Only happens if this package is installed but then also if the only thing active is the TopSpammers list (deny inbound). All other disabled.Thanks!
-
Try to Increase Firewall Maximum Table Entries in system -> advanced
-
Try to Increase Firewall Maximum Table Entries in system -> advanced
increased to 1000000 and it happens still, in particular Reboot.
Oh, and blinkled stops working as a service and cannot be restarted when pfBlocker is active -
How many lists/countries do you have applied?
-
How many lists/countries do you have applied?
only pfBlockerTopSpammers, rest is disabled. May be a startup issue though as it gets calmer later (about 3 mins after router's webIF is accessible).
Another thing I have noted is that blinkled can be started again (much) later, probably after the power LED gets released from its error blinking task. -
@ghm:
Try to Increase Firewall Maximum Table Entries in system -> advanced
increased to 1000000 and it happens still, in particular Reboot.
Oh, and blinkled stops working as a service and cannot be restarted when pfBlocker is activeRaise the limit to 1500000 or 2000000.
You may also have to raise the number of Firewall Maximum States -
@ghm:
How many lists/countries do you have applied?
only pfBlockerTopSpammers, rest is disabled. May be a startup issue though as it gets calmer later (about 3 mins after router's webIF is accessible).
Another thing I have noted is that blinkled can be started again (much) later, probably after the power LED gets released from its error blinking task.Can you get boot log from serial console?
-
Can you get boot log from serial console?
Not easily as last time I got scrambled readings even though I used a null modem cable and 9600 8n1. I suspect the gender changer I had to fiddle in or the cable. Need to buy other cable I guess.
Weird thing is that I never had this issue running Countryblock. Same system.
-
Raise the limit to 1500000 or 2000000.
You may also have to raise the number of Firewall Maximum States…but I have only a small block list enabled anyway and my states are south of 200/23000 when this happens.
-
@ghm:
Weird thing is that I never had this issue running Countryblock. Same system.
Disable all lists and try a reboot.
On nanobsd version somebody posted a error during boot on url tables.PfBlocker uses only native pfsense 2.0 functions to fill up aliases and create rules.
unfortunately i have no alix box to debug it. -
Anyone else having problems with lists?
For some reason when PFBlocker is bringing in a list from a text file, it's making up it's own entries. Using the list for qwest ISP
Here is a copy paste of my current text file:
Qwest:67.40.0.0-67.42.255.255 Qwest:155.70.0.0-155.70.255.255 Qwest:205.168.0.0-205.171.255.255 Qwest:204.147.80.0-204.147.95.255 Qwest:71.208.0.0-71.223.255.255 Qwest:208.44.0.0-208.47.255.255 Qwest:66.77.0.0-66.77.255.255 Qwest:216.206.0.0-216.207.255.255 Qwest:71.32.0.0-71.39.255.255 Qwest:206.81.192.0-206.81.223.255 Qwest:206.196.128.0-206.196.159.255 Qwest:63.224.0.0-63.231.255.255 Qwest:65.112.0.0-65.127.255.255 Qwest:63.144.0.0-63.151.255.255 Qwest:63.152.0.0-63.159.255.255 Qwest:63.232.0.0-63.239.255.255 Qwest:209.3.0.0-209.3.255.255 Qwest:209.45.128.0-209.45.255.255 Qwest:209.180.0.0-209.181.255.255 Qwest:209.201.0.0-209.201.127.255 Qwest:209.211.0.0-209.211.255.255 Qwest:216.111.0.0-216.111.255.255 Qwest:216.160.0.0-216.161.255.255 Qwest:207.108.0.0-207.109.255.255 Qwest:207.159.64.0-207.159.127.255 Qwest:207.224.0.0-207.225.255.255 Qwest:206.80.192.0-206.80.223.255 Qwest:205.215.192.0-205.215.223.255 Qwest:204.245.64.0-204.245.127.255 Qwest:204.131.0.0-204.134.255.255 Qwest:204.98.0.0-204.98.255.255 Qwest:204.26.64.0-204.26.127.255 Qwest:199.117.0.0-199.117.255.255 Qwest:198.36.128.0-198.36.255.255 Qwest:198.186.195.0-198.186.198.255 Qwest:198.233.0.0-198.233.255.255 Qwest:198.243.0.0-198.243.255.255 Qwest:192.104.175.0-192.104.180.255 Qwest:192.41.239.0-192.41.243.255 Qwest:168.103.0.0-168.103.255.255 Qwest:151.116.0.0-151.119.255.255 Qwest:150.159.0.0-150.159.255.255 Qwest:148.155.0.0-148.158.255.255 Qwest:144.163.0.0-144.163.255.255 Qwest:137.106.0.0-137.107.255.255 Qwest:130.13.0.0-130.13.255.255 Qwest:75.160.0.0-75.175.255.255 Qwest:72.164.0.0-72.166.255.255 Qwest:70.56.0.0-70.59.255.255 Qwest:68.176.0.0-68.177.255.255 Qwest:69.8.192.0-69.8.255.255 Qwest:67.0.0.0-67.7.255.255 Qwest:67.12.0.0-67.14.159.255 Qwest:67.128.0.0-67.135.255.255 Qwest:67.144.0.0-67.148.255.255 Qwest:66.86.0.0-66.86.255.255 Qwest:65.128.0.0-65.159.255.255 Qwest:65.100.0.0-65.103.255.255 Qwest:97.112.0.0-97.127.255.255 Qwest:174.16.0.0-174.31.255.255
Here is what PFBlocker sets for the table:
130.13.0.0/16 130.200.0.0/14 130.224.0.0/12 131.0.0.0/11 132.154.0.0/16 132.172.0.0/16 134.0.0.0/13 134.24.0.0/14 134.80.0.0/14 135.0.0.0/13 135.32.0.0/13 137.96.0.0/15 137.106.0.0/15 138.17.128.0/18 140.112.0.0/14 142.64.0.0/13 143.160.0.0/12 144.163.0.0/16 145.72.0.0/14 148.152.0.0/14 150.159.0.0/16 151.64.0.0/12 151.116.0.0/14 155.70.0.0/16 162.11.72.96/28 168.103.0.0/16 174.16.0.0/12 192.41.232.0/21 192.104.168.0/21 194.224.0.0/12 198.36.128.0/17 198.186.192.0/22 198.233.0.0/16 198.243.0.0/16 199.117.0.0/16 204.26.64.0/18 204.98.0.0/16 204.128.0.0/14 204.147.80.0/20 204.245.64.0/18 205.168.0.0/14 205.215.192.0/19 206.80.192.0/19 206.81.192.0/19 206.196.128.0/19 207.108.0.0/15 207.159.64.0/18 207.224.0.0/15 208.44.0.0/14 209.3.0.0/16 209.45.128.0/17 209.180.0.0/15 209.201.0.0/17 209.211.0.0/16 216.111.0.0/16 216.160.0.0/15 216.206.0.0/15 254.64.0.0/13 254.96.0.0/13 255.128.0.0/13 255.160.0.0/13
I've looked over the list a few times and can't find any typos. One of the ranges includes dell.com
143.160.0.0/12
No where is that defined in the list, but somehow it ends up in the table.
I took a small chunk of the file and it looks like PFBlocker isn't correctly pulling in any of the addresses with only 2 digits in them.
I'm not running 2.0 release yet… but I'm not sure if that would have anything to do with this.
-
I am getting this in the System Log. Any ideas?
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 cat: /usr/local/www/packages/ipblocklist/interfaces.txt: No such file or directory 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 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 rm: /usr/local/www/pac
-
Bman2121,
When you pass a range, pfBlocker will find a CIDR that matches it.
I saw in your list a realy large range( > /16).
Change this list to a CIDR format and see what happens. -
hankjrfan00,
It's related to ip-blocklist package.
If you had removed it, maybe you need to delete this remaining script.'/usr/local/pkg/pf/IP-Blocklist.sh start'
Also look for ipblocklist scripts in /usr/local/etc/rc.d