PfBlockerNG v2.0 w/DNSBL

BBcan177

@BBcan177:

Thanks, I am hoping to get this out shortly… Just trying to clean up a couple loose ends.... Stay tuned!

maybe as a cristmas gift @bbcan ? ::) ::)
really look forward to your release

Probably after the Holidays… Just been really crazy busy lately... :(

heliop100

Hi,

I have a custom IPV4 Denny List
On Custom Address(es) I have 9 IPs but only 7 off them are been loaded
5.9.110.236
54.207.50.1
187.17.111.97
169.45.117.93
96.6.123.19
104.16.84.55
104.16.83.55
162.243.102.114
187.61.117.226

These two are not loading, I try to change order, set "Update Custom List" on drop down, etc.
5.9.110.236
162.243.102.114

Any ideas?

Thanks

RonpfS

Did you ran a Force Update and a Force Reload IP ?
Look at the pfblockerng.log, error.log to see what is happening when that Table is loaded?
Does these IPs get whitelisted?

heliop100

Hi,

I found that on log:

[ Denny_list_custom ] Downloading update . completed ..
–----------------------------
Original Master Final
------------------------------
9 7 7 [ Pass ]

I realize that the IP 162.243.102.114 are included in another entry as member of AS14061

But not find any conflict on the IP 5.9.110.236

Thanks.

RonpfS

Maybe it's already in another Table

grep "5.9.110.236" /var/db/pfblockerng/deny/*

or using a different range

grep "5.9.110" /var/db/pfblockerng/deny/*
grep "5.9.11" /var/db/pfblockerng/deny/*
grep "5.9.1" /var/db/pfblockerng/deny/*
grep "5.9." /var/db/pfblockerng/deny/*

heliop100

Bingo

I find it on: /var/db/pfblockerng/deny/IBlock_Proxy.txt:5.9.110.236exi

But I have one server communicating on port 123 with that IP, believe are one NTP server.

Why are not blocking it?

Hugovsky

I'm having problems with iOS 11.3 BETA. It seems that safari can't go to 0.0.0.0 and pages can't load. Solution was to reinstall package and use the VIP address, as I was using the certificate hack and 0.0.0.0.

EDIT: Sorry, wrong version. I'm on 2.1.

xanaro

earlier this month 1.1.1.1 (DNS server) was announced.
I noticed I can use their backup server 1.0.0.1 but cannot use 1.1.1.1

I have read that it is because of pfblockerNG, I tried the suggested edit from shell

https://www.reddit.com/r/PFSENSE/comments/88wg6g/issue_with_pfblockerng_dnsbl_and_cloudflares_1111/

sed -i '' 's/1.1.1.1/1.1.1.2/g' /usr/local/pkg/pfblockerng/pfblockerng.sh

but it does not seem to have worked, any help is appreciated.

RonpfS

You have to do a Force Reload All when you change this IP.

Maxburn

Did charting make it into this release? I can't seem to find it.

https://forum.pfsense.org/index.php?topic=144733.msg787832#msg787832

Escorpiom

I've just set this up, and the blocker is indeed very effective!
At the moment I'm using the DNSBL part only but so far it's impressive.

The only thing missing at the moment is the DNS blocking for IPv6 content. For example on Youtube.
As I understand this would be a new future for the upcoming 3.0 release, if so then I'm eager to try it out.

Thanks for your work on pfBlockerNG and your support, it's a must have for PfSense.

Cheers.

Edit:
I should have posted this in the pfBlockerNG 2.1 topic, that's the actual version installed on my pfsense box.

labradorg13

Hi do you have any guide or tutorial for the new version of pfblockerng w/ dnsbl.
Kindly please share.

Thanks

pfSenseTest

@labradorg13 https://www.linuxincluded.com/block-ads-malvertising-on-pfsense-using-pfblockerng-dnsbl/

SashaZt

Fatal error: Call to undefined function pfb_alerts_default_page() in /usr/local/www/pfblockerng/pfblockerng_general.php on line 96 PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_general.php, Line: 96, Message: Call to undefined function pfb_alerts_default_page()
Help???

BBcan177

@sashazt said in PfBlockerNG v2.0 w/DNSBL:

Fatal error: Call to undefined function pfb_alerts_default_page() in /usr/local/www/pfblockerng/pfblockerng_general.php on line 96 PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_general.php, Line: 96, Message: Call to undefined function pfb_alerts_default_page()
Help???

Strange error... Looks like it didn't install properly... Do you have enough hard drive space? Try to remove/reinstall the package.

Overloader

It looks like a PHP Opcache issue. Simply reboot pfsense after upgrade. Then it works.

BBcan177

@sashazt said in PfBlockerNG v2.0 w/DNSBL:

Fatal error: Call to undefined function pfb_alerts_default_page() in /usr/local/www/pfblockerng/pfblockerng_general.php on line 96 PHP ERROR: Type: 1, File: /usr/local/www/pfblockerng/pfblockerng_general.php, Line: 96, Message: Call to undefined function pfb_alerts_default_page()

Can you confirm if you are on pfSense 2.4.3? or 2.4.4?

Also did this occur when you upgraded pfBlockerNG-devel? or was this a new installation of pfBlockerNG-devel?

Overloader

@bbcan177 I'm running pfsense 2.4.3-RELEASE-p1 and upgraded from pfBlockerNG 2.1.4_9 to 2.2.5_11 (dev). There are no installation errors but it looks like that the PHP files are cached due opcache.

$ php -v
PHP 5.6.34 (cli) (built: Mar 16 2018 16:55:46) 
Copyright (c) 1997-2016 The PHP Group
Zend Engine v2.6.0, Copyright (c) 1998-2016 Zend Technologies
    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2016, by Zend Technologies
    with Suhosin v0.9.38, Copyright (c) 2007-2015, by SektionEins GmbH

MarcoP

@overloader is your php using opcache.validate_timestamps=0?
If it doesn't opcache should be able to check the modified timestamp and regenerate the cache.

I found out a little issue with a feed blocking it's own IP, funny.

Info regarding the feed
PRI4 - CCT_IP - https[:]//cybercrime-tracker[.]net/fuckerz.php - 213.186.33.3

I'll drop an email and report it directly to the list owner, till here easy.

However the main gateway is still able to connect and download from that IP.

pfSense gateway - pfBlockerNG Reports
Sep 4 10:00:47 WIFI pfB_PRI4_v4 (1770006077) 192.168.20.103:44188 213.186.33.3:443 cluster015.ovh.net TCP:S

pfSense test box on WIFI vlan - 192.168.20.103 - pfBlockerNG error.log
[ pfB_PRI4_v4 - CCT_IP_v4 ] Download FAIL [ 09/04/18 10:00:53 ] Firewall and/or IDS (Legacy mode only) are not blocking download.

Inbound interface is WAN

Advanced inbound on OpenPorts alias
Advanced outbound any any - as default
Floating rules deny both directions

Outbound interfaces, all including WAN

Advance inbound/outbound as default
Floating rules denying both directions

Pinging the IP from WAN correctly fails so pfB rules are working, but why is it still able to download, or is pfBlockerNG able to circumvent it's own block lists.

I was only able to found out the feed blocking it's own IP only because I was synching to the client.

Cheers

gniting

I'm looking to get started with PfBlockerNG but am confused as to which version I should get started with, the "dev" version or the stable one? Any pointers on differences between the two will be immensely helpful.

Thanks.