PfBlockerNG v2.1 w/TLD

BBcan177

I have posted a PR #164 to fix the H3x parser issue noted above.
‎https://github.com/pfsense/FreeBSD-ports/pull/164‎

Once this is merged the pkg will be at version 2.1.1_2.

If you manually edited the file noted above, or not, you do not need to make any further changes with this version.

oddworld19

…...and I'm buying another 8 gigs RAM tonight (from 8G to 16G) now that unbound is VIRT 12.3G and I've swapped 6G.

Worth it though.

Andrew453

Hi BBcan177

Thanks for implementing this. Would you be able to explain a bit more what the role of the /usr/local/pkg/pfblockerng/dnsbl_tld file is please?

I was expecting it to contain a pure list of TLDs which pfblockerng can then use to work out whether any given domain is a second level domain or higher. But it seems itself to contain some second level domains?

That said, when I've looked that the /var/unbound/pfb_dnsbl.conf on my set up that pfblockerng has created, it does contain exactly what I would expect to see (i.e. full blocking of the entire domain for second level domains, but only specific blocking for higher level domains). So it does seem to be doing exactly what I'd like it to, but I'm not sure how the dnsbl_tld file is working to do that.

Thanks.

Qinn

Hi BBcan177,

Is there any good install/setup/configure instruction (video or guide) for the last version op pfblockerNG, that you could/would recommend?

Thanks for your advice, cheers Qinn

BBcan177

@Andrew453:

I was expecting it to contain a pure list of TLDs which pfblockerng can then use to work out whether any given domain is a second level domain or higher. But it seems itself to contain some second level domains?

Hi Andrew453,

If I only used the TLD, it would be a simple process of looking at any listed Domain and seeing if it had only a second-level Domain (SLD) then block the entire Domain. However, there are suffixes like "uk.com" which is what I would call the TLD that is used to determine if there is one more level. So all of the TLDs (suffixes) in that file are known TLDs which is used in the determination process. Most of the file was taken from the "Public Suffix Registry".

BBcan177

@Qinn:

Hi BBcan177,

Is there any good install/setup/configure instruction (video or guide) for the last version op pfblockerNG, that you could/would recommend?

Thanks for your advice, cheers Qinn

There is a pfSense Hangout that I did which can be used for an overview of the pkg functionality. However, apart from the three main pfBlockerNG threads in this forum, there isn't any other documentation.

Qinn

Thanks for the quick reply. Darn :( I found this one can you can agree to this one?

https://www.youtube.com/watch?v=YLhDOaH0q5U

Andrew453

@BBcan177:

@Andrew453:

I was expecting it to contain a pure list of TLDs which pfblockerng can then use to work out whether any given domain is a second level domain or higher. But it seems itself to contain some second level domains?

Hi Andrew453,

If I only used the TLD, it would be a simple process of looking at any listed Domain and seeing if it had only a second-level Domain (SLD) then block the entire Domain. However, there are suffixes like "uk.com" which is what I would call the TLD that is used to determine if there is one more level. So all of the TLDs (suffixes) in that file are known TLDs which is used in the determination process. Most of the file was taken from the "Public Suffix Registry".

Yes ok. That's exactly what I thought the file was for. (i.e. some eTLDs are longer than others, so you need a list e.g. .com vs .co.uk to work out what to treat as an eTLD)

The thing that was confusing me was there were some domains in the list that looked a bit odd, e.g.

myactivedirectory.com
mydrobo.com
mysecuritycamera.com
myshopblocks.com
myvnc.com

I think all you're saying is that pfblockerng will treat those as eTLDs even though, strictly speaking, they aren't … which is fine.

p.s. a big thank you for implementing this. It was on my wish-list as I recall - https://forum.pfsense.org/index.php?topic=106534

Guest

@RonpfS:

@ntct:
Hi BBcan177,

I can't update h3x feed from available feeds list in pfBlockerNG v2.1.

It show below.
[ h3x ]			 Downloading update .. 200 OK
 Remote timestamp missing 
 No Domains Found
Same here

@ntct:

And I can't let TLD Exclusion List working. Can you give a example or check it works?

Did you do a Force Reload after changing the list ?

I'm on 2.1.1_2, the h3x fix is included, but I get the same error as above.

I tried with Update, Cron , Reload.

[ malw_corpus ] Downloading update .. 200 OK
Remote timestamp missing
No Domains Found

MoonKnight

Hi,
Thank you for your hard work on this package :)

After updating to 2.1.1_2 i can't "clear DNSBL Packets" from the pfBlockerNG widge
The DNSBL_EasyList won't delete the packets

![Desktop 31-07-2016 17.00.06-358.png_thumb](/public/imported_attachments/1/Desktop 31-07-2016 17.00.06-358.png_thumb)
![Desktop 31-07-2016 17.00.06-358.png](/public/imported_attachments/1/Desktop 31-07-2016 17.00.06-358.png)
[Video 31-07-2016 16.54.57.zip](/public/imported_attachments/1/Video 31-07-2016 16.54.57.zip)

RonpfS

@Redyr:

I'm on 2.1.1_2, the h3x fix is included, but I get the same error as above.

I tried with Update, Cron , Reload.

[ malw_corpus ] Downloading update .. 200 OK
Remote timestamp missing
No Domains Found

Each URL contains sites that were active in the last period (month, week, day or hour).

If you look at the 1hour or the 1day csv file, they only have one comment. The 1week and 1month have entries.

You should only choose one of the feeds according to your need. I guess most will pick the 1month URL.

pftdm007

Not sure if this is related to pfblockerNG (2.1 w/ TLD) but I went to the package manager to install a package, and saw that my copy of pfblockerNG was outdated, so I clicked the yellow round arrow to update the package. It went well, but immediately after I returned to the package manager I was greeted with a red ribbon saying "Unable to retrieve package information". This happens for the "Installed Packages as well as "Available Packages" tabs!

On the main page, I see "Obtaining update status ", then it turns to "Unable to check for updates".

Tried disabling both pfblockerNG and DNSBL to no avail. Snort is disabled and the blocked hosts list is empty.

Now I cannot update, install or uninstall packages…. How do I remedy to this?

Andrew453

I've had that trouble before too. It happened when I was trying to change from the development thread for updates to the stable thread. I couldn't update anything. I eventually found some instructions to reinstall the main pfsense components from the command line. I ended up still on the development thread and didn't venture to try to change it back after that.

pftdm007

@Andrew453:

I've had that trouble before too. It happened when I was trying to change from the development thread for updates to the stable thread. I couldn't update anything. I eventually found some instructions to reinstall the main pfsense components from the command line. I ended up still on the development thread and didn't venture to try to change it back after that.

Not sure I understand that. I am not playing with development stuff, nor that I am configured to retrieve packages from development repos.. Just a vanilla pfsense install with pfblockerNG, snort and thats it. Not normal all of a sudden I lose connection to repos..

Also after a reboot I see these warnings in the main page:

There were error(s) loading the rules: /tmp/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 14:55:00
There were error(s) loading the rules: /tmp/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 14:55:11
There were error(s) loading the rules: /tmp/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 14:55:20

BBcan177

@lpallard:

There were error(s) loading the rules: /tmp/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 14:55:00
There were error(s) loading the rules: /tmp/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 14:55:11
There were error(s) loading the rules: /tap/rules.debug:37: cannot define table pfB_Europe_v6: Cannot allocate memory - The line in question reads [37]: table <pfB_Europe_v6> persist file "/var/db/aliastables/pfB_Europe_v6.txt" @ 2016-07-31 14:55:20

These all seem to be related to the MaxMind IPv6 database. Looks like you will need to bump the pfSense max aliastable entries limit from 2M to 4M. If you enable aggregation in the general tab, it should condense the CIDRs and reduce the overall IP count. This changed due to using the new MaxMind Geolite2 database which seems to have smaller subsets of the data listed causing more IP entries to be added.

BBcan177

@CiscoX:

After updating to 2.1.1_2 i can't "clear DNSBL Packets" from the pfBlockerNG widge
The DNSBL_EasyList won't delete the packets

I am away for a few weeks but will check that out. Seems like some regression somewhere. Thanks for reporting.

java007md

@lpallard:

Not sure if this is related to pfblockerNG (2.1 w/ TLD) but I went to the package manager to install a package, and saw that my copy of pfblockerNG was outdated, so I clicked the yellow round arrow to update the package. It went well, but immediately after I returned to the package manager I was greeted with a red ribbon saying "Unable to retrieve package information". This happens for the "Installed Packages as well as "Available Packages" tabs!

On the main page, I see "Obtaining update status ", then it turns to "Unable to check for updates".

Tried disabling both pfblockerNG and DNSBL to no avail. Snort is disabled and the blocked hosts list is empty.

Now I cannot update, install or uninstall packages…. How do I remedy to this?

From the following thread:

https://forum.pfsense.org/index.php?topic=116019.0

I followed the ssh command line execution steps:

pkg update -f
pkg upgrade -f

and the same problem was resolved.

MoonKnight

@BBcan177:

@CiscoX:

After updating to 2.1.1_2 i can't "clear DNSBL Packets" from the pfBlockerNG widge
The DNSBL_EasyList won't delete the packets

I am away for a few weeks but will check that out. Seems like some regression somewhere. Thanks for reporting.

Hi, No problem. Have a nice Holiday :)

Qinn

Hi there I followed this guide, http://fredmerc.com/2016/07/15/pfsense-adblock-using-pfblockerng-guide/ a rather short setup, there is only DNSBL and no IP4 is that new or is this guide missing it? Thanks for any help.

RonpfS

@Qinn:

Hi there I followed this guide, http://fredmerc.com/2016/07/15/pfsense-adblock-using-pfblockerng-guide/ a rather short setup, there is only DNSBL and no IP4 is that new or is this guide missing it? Thanks for any help.

Here are the original pfBlockerNG thread https://forum.pfsense.org/index.php?topic=86212.0
and the pfBlockerNG v2.0 w/DNSBL thread https://forum.pfsense.org/index.php?topic=102470