PfBlockerNG v2.0 w/DNSBL

erwintwr

hi guys

Thx firstly for a very awesome addon! - will definitely see if company can forward some $$'s your way :)

i am firstly implementing some block lists to allow specific country access, and after a few recommendations on the forum i only added a permit rule for the countries where we require access from, specifically targeting a specific port alias set,

pfblocker config is set to permit inbound , with enable custom port checked and an alias loaded with the ports i want open.
This morning i notice some alerts, with a permit firing for ports that is not in the alias rule
eg port 443 / 100 is not on the alias list - only 5401

the firewall rules summary page seems to be ok :

but if i click on edit on one of the rules, it strangely does not show the port that is being blocked

PFblocker config (Countries -> Africa)

Can anyone recommend maybe what i could be missing?

Thx

EDIT

never mind , managed to solve this ( a little bit of reading helps)

changed the protocol to TCP/UDP ( not any), and reloaded everything. seems to be ok now :)

MakesSense

@BBcan177:

Hi MakesSense,

Can you not add a local interface just for DNSBL?

Hi BBcan177,

Unfortunately I can't seem to find any way to add a LAN interface on this VPS system.
Is there any way to fake one? or any other alternative ideas?
I have about 150 people using the pfSense/pfBlockerNG server now but really struggling to figure out what is blocking.

asgard

Hi,

If pfBlockerNG could be configured to do online lookup against block lists like e.g. zen.spamhaus.org and bl.spamcop.net this would be a great new feature since these lists contains a lot more IP's then the drop lists. I'm currently using the Postfix Forwarder package for this but this package is no longer available since version 2.3.

theflu

I had a list in pfBlockerNG and I removed it. Its gone from the pfBlocker GUI, but it is still on my dashboard widget and I get these warnings all the time. Unresolvable destination alias 'pfB_iBlockYoyoAdServers' for rule 'pfB_iBlockYoyoAdServers auto rule' @ 2016-04-14 16:00:03

I tried update, cron and refresh all in pfBlockerNG

Ran:
pfctl -t pfB_iBlockYoyoAdServers -T kill

Output: 0 table removed

Ran: pfctl -s all
Did not see a table with that name

I have tried to uninstall pfBlocker w/keep setting uncheck. The list is still there when I reinstall.

pfSense 2.3

theflu

@theflu:

I had a list in pfBlockerNG and I removed it. Its gone from the pfBlocker GUI, but it is still on my dashboard widget and I get these warnings all the time. Unresolvable destination alias 'pfB_iBlockYoyoAdServers' for rule 'pfB_iBlockYoyoAdServers auto rule' @ 2016-04-14 16:00:03

I tried update, cron and refresh all in pfBlockerNG

Ran:
pfctl -t pfB_iBlockYoyoAdServers -T kill

Output: 0 table removed

Ran: pfctl -s all
Did not see a table with that name

I have tried to uninstall pfBlocker w/keep setting uncheck. The list is still there when I reinstall.

pfSense 2.3

I fixed my issue. I deleted the entries in Firewall >> Rules for LAN and WAN that reference the list I wanted to remove. The list is gone from the dashboard and I am not getting the error anymore.

robwalker5561

Hello,

I have just built a clean install of 2.3 and install pfBlockerNG and added a bunch of lists from i-BlockList

However, I am getting these lists blocking DNS traffic to the router itself

I've worked around this with a permit rule at higher priority … but it doesn't seem to be the right solution. Does this imply one of the lists has the LAN's non-routable addresses in it?

BBcan177

Hi robwalker5561,

Run these commands and it will show if there is a loopback address (Won't be the first time that IBlock does this :) ):

grep "127\.0\.0\." /var/db/pfblockerng/deny/*
grep "127\.0\.0\." /var/db/pfblockerng/dnsbl/*
grep "127\.0\.0\." /var/db/aliastables/*

If it finds a loopback, then enable "Suppression" in the General Tab, and run a "Force Reload" to clear it out…

robwalker5561

Thank you for the reply.

Those commands don't match any entries (nor does a regex for 192.168. or my WAN IP address)

The help for 'Suppression' says:

This will prevent Selected IPs from being blocked. Only for IPv4 lists (/32 and /24).

Which sound great … the correct approach is to then modify the pfBlockerNGSuppress alias manually with the local IP?

@BBcan177:

Hi robwalker5561,

Run these commands and it will show if there is a loopback address (Won't be the first time that IBlock does this :) ):
grep "127\.0\.0\." /var/db/pfblockerng/deny/*
grep "127\.0\.0\." /var/db/pfblockerng/dnsbl/*
grep "127\.0\.0\." /var/db/aliastables/*
If it finds a loopback, then enable "Suppression" in the General Tab, and run a "Force Reload" to clear it out…

BBcan177

From your original screenshot: How can you have both src and dst with a 192.168.1.x address range? Are you double Natting? WAN/LAN should be in separate IP ranges…

robwalker5561

Shouldn't be anything too complicated going on … at least not by design, I probably misconfigured something:

192.168.1.6 is a box on the LAN

192.168.1.1 is the gateway's LAN interface (a /24), its WAN is 192.168.209.14 which is NAT'd because that is all the modem exposes

The rules configuration is:

@BBcan177:

From your original screenshot: How can you have both src and dst with a 192.168.1.x address range? Are you double Natting? WAN/LAN should be in separate IP ranges…

BBcan177

Is this alert repeating? It says "no match" in the pic… So maybe it was being blocked previously. Clear the Firewall logs, and see if it re-appears...

yea

Hi

Using the latest version of pfsense and pfblockerng, when setting to allow an ipv4 rule, it generates an auto rule. I thought, when using the advanced inbound rules that this would modify the auto rule. Instead, it just appears to ignore these settings and create a default auto open rule for dest/port - though it correctly retains the src. Also, when modifying the auto rule every subsequent modification to the pfblocker rule rewrites and resets the auto rule.

Is this by design?

Thanks (fantastic package btw!)

BBcan177

@yea:

I thought, when using the advanced inbound rules that this would modify the auto rule.

Is this by design?

Thanks (fantastic package btw!)

Thanks!

See here:
https://forum.pfsense.org/index.php?topic=102470.msg612027#msg612027

Change the protocol settings. :)

yea

Apologies. I was entering addresses manually, not as the notes said. When using aliases it works perfectly.

robwalker5561

Interesting … I put things back the way they were (as far as I can tell) and I can't reproduce the problem now ... so all good

Thanks for your help!

@BBcan177:

Is this alert repeating? It says "no match" in the pic… So maybe it was being blocked previously. Clear the Firewall logs, and see if it re-appears...

Mr. Jingles

I just made acquaintance with a certain Latina, the sister of that other Latina. Might be introducing you to her shortly 8)

( ;D ;D ;D ).

BB, could you please look at the attached pic? This doesn't make sense, does it? This is Comodo firewall alerting because Java (used by my media indexing program) wants to go to your 10.10.10.1. Why would it want to do that?

We also had the 10.10.10.1 and NTP server, and I think something is weird. DNS Resolver –- EDIT, see second screenshot, wanted to make a pic of DNS resolver and now MRT.exe also wants to do 'stuff' at 10.10.10.1.

Something is wrong. Obviously must be something on my side, but what?

( :-* )

BB_weird_.jpg_thumb

BB_weird2_.jpg_thumb

Mr. Jingles

Btw, BB, prollally this is why suddenly this media manager now is DEAD SLOW, when for the past two years it was BLAZINGLY fast.

Can you PLEASE PLEASE PLEASE (please :P ) suggest a solution and/or workaround? Because now every movie lookup takes 2 minutes, it used to take a second. This is not good for my heart, and you know about my heart :-*

BBcan177

Hey Mr J… Take it easy with your heart and those Latinas :)

I see that you have multiple VLANs. In the DNSBL tab, there is an option to create a Floating Permit rule. Please check that option and select all of the LAN segments (vlans etc) that need to access the DNSBL VIP... I think the reason why your devices might be slow, is that they can't get to the DNSBL VIP address. That is most likely the issue with your time out (Slowness)...

For the "Three Amigo" issue... Take a look at the Alerts tab in the "DNSBL" section, and it will list whats being blocked by DNSBL... You can click the Suppression Icon if for any FPs... However, this issue might be related to my first comment...

rattis

Like this plugin, first and only one I'm using so far but I'm having a problem.

Some of the feeds block properly, while some do not. At first I thought this was just Easylist, but I just found another.

I did flush the dns cache on the windowd box first

chrisj@bikatol ~
$ ns
Default Server:  pfbox.localdomain
Address:  192.168.1.254

> 188server.com
Non-authoritative answer:
Server:  pfbox.localdomain
Address:  192.168.1.254

Name:    188server.com
Address:  95.211.219.66

> zypenetwork.com
Non-authoritative answer:
Server:  pfbox.localdomain
Address:  192.168.1.254

Name:    zypenetwork.com
Address:  69.89.31.176

> www188.nebraskacb.mcarder.chefpa.mggschmitt.dorystarla.com
Server:  pfbox.localdomain
Address:  192.168.1.254

Name:    www188.nebraskacb.mcarder.chefpa.mggschmitt.dorystarla.com
Address:  10.10.10.1

From pfbox cli

[2.3-RELEASE][admin@pfSense.localdomain]/root: grep 188server.com /var/unbound/pfb_dnsbl.conf
local-data: "188server.com 60 IN A 10.10.10.1"

grep 188server.com /var/unbound/pfb_dnsbl.conf
local-data: "188server.com 60 IN A 10.10.10.1"

grep 188server.com /var/db/pfblockerng/dnsblorig/*
/var/db/pfblockerng/dnsblorig/EasyListElements.orig:||188server.com^$third-party
/var/db/pfblockerng/dnsblorig/EasyListFeeds.orig:||188server.com^$third-party

grep 188server.com /var/db/pfblockerng/dnsbl/*
/var/db/pfblockerng/dnsbl/EasyListElements.txt:local-data: "188server.com 60 IN A 10.10.10.1"

[2.3-RELEASE][admin@pfSense.localdomain]/root: grep zypenetwork.com /var/unbound/pfb_dnsbl.conf
local-data: "zypenetwork.com 60 IN A 10.10.10.1"

grep zypenetwork.com /var/db/pfblockerng/dnsblorig/*
/var/db/pfblockerng/dnsblorig/EasyListElements.orig:||zypenetwork.com^$third-party
/var/db/pfblockerng/dnsblorig/EasyListFeeds.orig:||zypenetwork.com^$third-party

grep zypenetwork.com /var/db/pfblockerng/dnsbl/*
/var/db/pfblockerng/dnsbl/EasyListElements.txt:local-data: "zypenetwork.com 60 IN A 10.10.10.1"

[2.3-RELEASE][admin@pfSense.localdomain]/root: grep www188.nebraskacb /var/unbound/pfb_dnsbl.conf
local-data: "www188.nebraskacb.mcarder.chefpa.mggschmitt.dorystarla.com 60 IN A 10.10.10.1"

grep www188.nebraskacb /var/db/pfblockerng/dnsblorig/*
/var/db/pfblockerng/dnsblorig/hpHosts.orig:127.0.0.1    www188.nebraskacb.mcarder.chefpa.mggschmitt.dorystarla.com

grep www188.nebraskacb /var/db/pfblockerng/dnsbl/*
/var/db/pfblockerng/dnsbl/hpHosts.txt:local-data: "www188.nebraskacb.mcarder.chefpa.mggschmitt.dorystarla.com 60 IN A 10.10.10.1"

When I thought it was just EasyList I did a: LIST ACTION disabled -> force update -> LIST ACTION enable. All are showing unbound.

Opps: grabed the wrong one above (second Easylist should have been frm my MDS.txt list)

Name: zzz.hudconnecthome.org
Address: 95.46.98.60

tail -n 1 /var/db/pfblockerng/dnsbl/MDS.txt
local-data: "zzz.hudconnecthome.org 60 IN A 10.10.10.1"

grep zzz.hudconnecthome.org /var/db/pfblockerng/dnsblorig/*
/var/db/pfblockerng/dnsblorig/MDL.orig:127.0.0.1 zzz.hudconnecthome.org
/var/db/pfblockerng/dnsblorig/MDS.orig:zzz.hudconnecthome.org

p.s. BBcan177 I was the guy on twitter talking about it on Sunday April 17th

BBcan177

@rattis:

Like this plugin, first and only one I'm using so far but I'm having a problem.

Some of the feeds block properly, while some do not. At first I thought this was just Easylist, but I just found another.

p.s. BBcan177 I was the guy on twitter talking about it on Sunday April 17th

Hey… welcome!

If you ping those domains from the pfSense box do they all resolve to the DNSBL VIP address?

Either your desktop has other DNS servers defined or the browser is bypassing the DNS server... what browser are you using? Ensure that the desktops only have pfSense set as its DNS Server. Might also need to exit and reopen the browser...

Flush the Browser DNS cache, and also flush the OS cache... Another option might be to create a Reject rule in the LAN interface to block any outgoing port 53 other than from the pfSense Box itself...