PfBlockerNG v2.1 w/TLD

DownloadDeviant

THANKS! Can't wait! Good stuff….great work...and thanks for helping us dumb dumbs :P here and over at Reddit!

PS - is there a quick n dirty way to test PFBNG to be sure you've generally set it up correctly? Like going to a website and not seeing ads, etc.?

mauroman33

Thank you so much for this fantastic work!!!

BBcan177

@DownloadDeviant:

THANKS! Can't wait! Good stuff….great work...and thanks for helping us dumb dumbs :P here and over at Reddit!

PS - is there a quick n dirty way to test PFBNG to be sure you've generally set it up correctly? Like going to a website and not seeing ads, etc.?

Thanks… Are you on the latest 2.1.1_1 version? Haven't heard much feedback yet, so not sure if many have installed it yet...

Not sure what sites are the worst for ADs... but yahoo is probably up there....

@mauroman33:

Thank you so much for this fantastic work!!!

Thanks!

DownloadDeviant

@BBcan177:

Thanks… Are you on the latest 2.1.1_1 version? Haven't heard much feedback yet, so not sure if many have installed it yet...

Not sure what sites are the worst for ADs... but yahoo is probably up there....

I'm still on 2.0.17. I've slowed down my updating a bit since I've had some snags and had to rebuild 3 times in the past 7 weeks. Two were my fault…lol I thought I had router plugged into the battery port on the UPS but didn't...storm hit...lost power...pf went corrupt. Sooooooooo, I'm a bit worn out on tampering right now. lol That said, I'll probably upgrade it this weekend.

Yahoo it is then. I'm very new to pfBNG so I need to learn it and get comfortable. I don't want to get too aggressive. I just want it to serve as a companion for my Firefox plugins and to help keep my girlfriend protected.

someuser123

pfBlockerNG-2.1.1_1 is working like charm, On 2.3.3-DEVELOPMENT (amd64) no issues.

TLD Blacklist is really handy, Thanks BBcan177

BBcan177

Here are the links for Malware Corpus Tracker which can be used w/ pfBlockerNG DNSBL:

Site:
http://track.h3x.eu/about/400

Available Feeds:
https://tracker.h3x.eu/api/sites_1month.php
https://tracker.h3x.eu/api/sites_1week.php
https://tracker.h3x.eu/api/sites_1day.php
https://tracker.h3x.eu/api/sites_1hour.php

DO NOT Select all of these Feeds. You should pick only one Feed. For example: the "1Month" will include the "1Week/1Day/1Hour".

[ Edit - change to https ]

Twitter:
https://twitter.com/h3x2b

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

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

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 ?

hulleyrob

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

[ 1week ]		 Downloading update [ 07/30/16 12:31:20 ] .. 200 OK
  Remote timestamp missing 
 No Domains Found

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

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

Me three, anyone post how exactly you get these list working?

BBcan177

Here is a patch to fix the H3X Feed… Sorry about that ...

@BBcan177:

Here are the links for Malware Corpus Tracker which can be used w/ pfBlockerNG DNSBL:

UPDATE:

Guess the internal QA testing didn't work too well when I tested this Feed.
Please follow these instructions below to patch the code to get the following feed to parse:

Edit /usr/local/pkg/pfblockerng/pfblockerng.inc

Goto Line 3368 which contains the following:
$h3x_feed = TRUE;
Reference:
https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L3368

and add the following line after line 3368:
$liteparser = TRUE;
Then follow that with a "Force Update"

BBcan177

@ntct:

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

Can you provide more detail about what you're trying to accomplish?

hulleyrob

Works for me.

For the lazy:

vi +3368 /usr/local/pkg/pfblockerng/pfblockerng.inc

to go straight to the line.

Thanks BBcan

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