PfBlocker

fragged

pfBlocker doesn't add any inbound rules for interfaces with no allow rules as there's a default deny all rule in place.

thebiznes

I meant when selecting pfblocker I cant use block inbound the default as stated on the page without the dashboard widget showing down and the firewall rules showing nothing there also. The only way I can get any thing working is block both inbound and outbound and Permit outbound.

The packets are they attempts? The ad one seems to draw more traffic to the firewall especially in permit outbound. For the minute I have disabled pfblocker until I can understand it's workings.

fragged

The package simply adds firewall rules based on your settings. That's all. I have no idea how the widget works for the status arrows, but the numbers are blocked connections matching any IP in that particular list. You can enable logging for the pfBlocker rules to see what it does on the System -> Firewall log.

In short, check firewall rules and log instead of the widget for what is actually going on.

marcelloc

@fragged:

That's all. I have no idea how the widget works for the status arrows,

It ckecks based on description rules applied to rules, if you have an alias with no rules, it will show as down. If you have rules applied to aliases, then it will show up and get the couter hit from pf.

thebiznes

Does it mean it is working applying the deny inbound? As you said it doesn't count. I can only get it working with deny both and permit outbound. I am probably getting confused with the operation being quite new to this so forgive me if I ask a stupid question.

marcelloc

@thebiznes:

Does it mean it is working applying the deny inbound? As you said it doesn't count. I can only get it working with deny both and permit outbound. I am probably getting confused with the operation being quite new to this so forgive me if I ask a stupid question.

Do you have rules on wan interface? If not, then pfblocker does not create a deny rule as pfsense is already blocking all inbound traffic.

MaxHeadroom

Hi,
is there the possiblility to make 2 alias rules for the same continent but different countries?
Or do i need to add custom country list ?

best regards max

marcelloc

@MaxHeadroom:

is there the possiblility to make 2 alias rules for the same continent but different countries?
Not on current version.

@MaxHeadroom:

Or do i need to add custom country list ?

It will be the best workaround for that.

pftdm007

Great package, but I hope someone can answer my question….

pfBlocker is working just fine, but seems to block legit sites such as github.com paypal.com. Not sure why these sites are blocked but I think they might be in some lists or countries I am blocking.

How can I somehow exclude these sites from being blocked by pfblocker? Im NO firewall guru and Im using pfsense's default firewall config.

There is an exclusion list in squidguard and a "whitelist" in snort so what can I do in pfblocker ???
Thanks!!

marcelloc

@lpallard:

There is an exclusion list in squidguard and a "whitelist" in snort so what can I do in pfblocker ???

You can create an exception list and allow it on blocker.

or

Change pfblocker action to alias only and create you own rules and aliases the way you need.

pftdm007

[quote]You can create an exception list and allow it on blocker.[/quote]

OK I figured out that you could create an exception list just as it was possible to create custom blocking lists..  But what confuses me is that these choices are the only ones available:

[code]Note:
'Deny Both' - Will deny access on Both directions.
'Deny Inbound' - Will deny access from selected lists to your network.
'Deny Outbound' - Will deny access from your users to ip lists you selected to block.
'Permit Inbound' - Will allow access from selected lists to your network.
'Permit Outbound' - Will allow access from your users to ip lists you selected to block.
'Disabled' - Will just keep selection and do nothing to selected Lists.
'Alias Only' - Will create an alias with selected Lists to help custom rule assignments.[/code]

Deny Both - I understand this will block the traffic TO & FROM the IP's so this is totally the opposite to what I want to do.
Deny Inbound - Unless I dont understand, accessing websites requires both inbound & outbound so if I block incoming traffic, the sites wont work.
Deny Outbound - Again unless I dont understand, accessing websites requires both inbound & outbound so if I block outgoing traffic, the sites wont work.
Disabled - Useless for my scenario..
Alias Only - I have no clue about this one.  Will read some documentation soon, or better maybe buy the pfsense book.

So I am left with only these two options but each of them does only half of the job, that is, allow traffic in either direction.  So to combine them, do I need to duplicate my list, in one of them I select Permit outbound, and the other one I select permit inbound?

Permit Inbound
Permit Outbound

Shouldnt the choice Permit both be present in the dropdown list??

marcelloc

Hi,

traxxus has suggested moving pfblocker old country lists to one free list http://www.ipdeny.com/ipblocks/

I can do it on my free time but if somebody needs it faster, consider donating to speed up new package versions.

att,
Marcello Coutinho

ttblum

Hello,

I have had two routers running pfBlocker that, when booted after a power outage, all inside hosts have lost internet access after the router came back up.

I can reproduce this on a test router, so far with the following conditions:

pfSense nanobsd version 2.0.3
pfBlocker version 1.0.2
WAN: Static IP
Gateway monitoring: disabled

If the internet connection to the router is severed before bootup (without losing link light), then no traffic from the inside is allowed to go through the router (even if internet connectivity is restored to the router after bootup). An attempted connection to yahoo.com looks like:

tcp 98.139.183.24:80 <- 192.168.1.100:51349 CLOSED:SYN_SENT
tcp 192.168.1.100:51349 -> 98.139.183.24:80 SYN_SENT:CLOSED

No traffic from the inside is shown as being blocked in the firewall logs.

The following is logged on bootup:

Jun 3 09:45:37 php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerTopSpammers.txt.tmp' 'https://127.0.0.1:443/pfblocker.php?pfb=pfBlockerTopSpammers'' returned exit code '1', the output was 'fetch: transfer timed out'
Jun 3 09:45:32 php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerSouthAmerica.txt.tmp' 'https://127.0.0.1:443/pfblocker.php?pfb=pfBlockerSouthAmerica'' returned exit code '1', the output was 'fetch: transfer timed out'
Jun 3 09:45:27 php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerAsia.txt.tmp' 'https://127.0.0.1:443/pfblocker.php?pfb=pfBlockerAsia'' returned exit code '1', the output was 'fetch: transfer timed out'
Jun 3 09:45:22 php: : The command '/usr/bin/fetch -T 5 -q -o '/var/db/aliastables/pfBlockerAfrica.txt.tmp' 'https://127.0.0.1:443/pfblocker.php?pfb=pfBlockerAfrica'' returned exit code '1', the output was 'fetch: transfer timed out'
Jun 3 09:49:21 php: : Restarting/Starting all packages.
Jun 3 09:49:21 php: : No pfBlocker action during boot process.
Jun 3 09:49:21 php: : No pfBlocker action during boot process.
Jun 3 09:49:21 php: : No pfBlocker action during boot process.
Jun 3 09:49:21 php: : No pfBlocker action during boot process.

justsomeguy6575

I can't get pfblocker to load this list doc.emergingthreats.net/pub/Main/RussianBusinessNetwork/RussianBusinessNetworkIPs.txt

Has anyone used this list before?

pftdm007

I recently added new lists in pfblocker. Immediately, pfsense started displaying errors in yellow at the top of the window:


[filter_load]There were error(s) loading the rules:

/tmp/rules.debug:151: macro pfBlockerpfblockerallowed not defined/tmp/rules.debug:151: syntax error
/tmp/rules.debug:159: macro pfBlockeresurveillance not defined/tmp/rules.debug:159: syntax error
/tmp/rules.debug:160: macro pfBlockerdropedrop not defined
/tmp/rules.debug:162: macro pfBlockerlevel1 not defined/tmp/rules.debug:162: syntax error
/tmp/rules.debug:172: macro pfBlockeresurveillance not defined/tmp/rules.debug:172: syntax error
/tmp/rules.debug:173: macro pfBlockerdropedrop not defined/tmp/rules.debug:175: macro pfBlockerlevel1 not defined
/tmp/rules.debug:175: syntax errorpfctl: Syntax error in config file: pf rules not loaded The line in question reads [151]: pass in log quick on $WAN reply-to ( re0 WAN-IP ) from $pfBlockerpfblockerallowed to any keep state label USER_RULE: pfBlockerpfblockerallowed auto rule

What happens?

marcelloc

@lpallard:

What happens?

Maybe something with the list that pfblocker code could not detect or get around.

pftdm007

@marcelloc:

@lpallard:

What happens?

Maybe something with the list that pfblocker code could not detect or get around.

Do you need something specific to help debugging? Logs?
I didnt do anything out of the ordinary so I think this shouldnt happen unless the package was in beta stage which is not.

marcelloc

Did you removed pfblocker lists before deleting custom firewall rules?

pf is complaining about 4 missing aliases.

justsomeguy6575

@justsomeguy6575:

I can't get pfblocker to load this list doc.emergingthreats.net/pub/Main/RussianBusinessNetwork/RussianBusinessNetworkIPs.txt

Has anyone used this list before?

Any ideas on this list? Also pfsense says it detected a crash and this is the info it contains:

Crash report begins. Anonymous machine information:

i386
8.3-RELEASE-p8
FreeBSD 8.3-RELEASE-p8 #1: Tue Jun 11 06:34:27 EDT 2013 root@snapshots-8_3-i386.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8

Crash report details:

PHP Errors:
in /usr/local/pkg/pfblocker.inc on line 262
in /usr/local/pkg/pfblocker.inc on line 262
in /usr/local/pkg/pfblocker.inc on line 262
in /usr/local/pkg/pfblocker.inc on line 262

Filename: /var/crash/minfree
2048

ttblum

Hi, I meant to add that this only happens when pfBlocker is installed and active.

I have had two routers running pfBlocker that, when booted after a power outage, all inside hosts have lost internet access
after the router came back up.