pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!

RonpfS

From the CHANGELOG :

FEEDS:
        Removed discontinued Heuristic Security DoH Feed

Remove this URL. Use the Feeds tab to update your Groups

vjizzle

Hi,

Do we have CNAME blocking now? Thanks and as always amazing job!

BBcan177

@vjizzle
Yes its there in the DNSBL Tab with the other Unbound Python mode features.

A Former User

@BBcan177 said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

Edit the file:
/usr/local/pkg/pfblockerng/pfblockerng.inc
At line #1097 there is a function that builds the Lighttpd configuration file:
function pfb_create_lighttpd() {
}

Editing this function works fine for me. There is no need to edit lines #1308 and #1322 - These are for the NAT Rules and should stay as they are.

Thank you!

mlines

This post is deleted!

SachaH

First of all, great job on this release!

I'm currently running 3.0.0_1 with 'Unbound python mode' enabled in DNSBL.
While viewing the Reports tab I saw that the If and Source columns show 'Unknown' within the DNSBL Python alert entry's.

Any suggestion how the fix this?

RonpfS

@SachaH said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

Reports tab I saw that the If and Source columns show 'Unknown' within the DNSBL Python alert entry's.

https://forum.netgate.com/topic/158597/interface-and-source-is-unknown-running-devel-3-0-1/5

SachaH

@RonpfS Thanks

RonpfS

also https://www.reddit.com/r/pfBlockerNG/comments/k1137y/reports_dnsbl_python_unknown/

RonpfS

This post is deleted!

RonpfS

and https://www.patreon.com/posts/nov-update-43770381

HuskerDu

Thanks BBcan177 for your great work,

For info, get yellow icon for DNSBL widget due to following error.

2020-11-27 21:33:25,736|ERROR| [pfBlockerNG]: Failed get_q_name_qinfo: in method '_get_qname', argument 1 of type 'struct query_info *'

BBcan177

@HuskerDu
Do you have any of these options enabled in the DNS Resolver?

DHCP Registration:

Static DHCP
OpenVPN Clients

If so, disable those options, clear the py_error log and Force Reload - DNSBL and see if the error returns.

HuskerDu

@BBcan177
The options were removed after I've read the doc, but first launch after the install must have triggered the error.

Thanks, clearing the log file solved the yellow icon "issue".

Regards,

A Former User

@BBcan177

with v3.0.0 load on my Firewall is significant reduced when running large Set of DNSBL Lists (~3 Million Domains).

I don't see the unbound-control process spinning up every couple of seconds anymore.

Well Done

fmroeira86

@BBcan177

Thank you for your effort!

Everytime I do a RELOAD the skew on the backup CARP gets its value set to 0.

This causes the backup machine holding as CARP master when the Master machine comes online again.

I'm running 3.0.0_2

BBcan177

@fmroeira86 said in pfBlockerNG-devel v3.0.0 - No longer bound by Unbound!:

Thank you for your effort!
Everytime I do a RELOAD the skew on the backup CARP gets its value set to 0.
This causes the backup machine holding as CARP master when the Master machine comes online again.
I'm running 3.0.0_2

Did you update the package on all Nodes?
Did you set the SKEW on all nodes correctly?

The package should not be syncing the SKEW to the other nodes.

See the relevant code here:
https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-pfBlockerNG-devel/files/usr/local/pkg/pfblockerng/pfblockerng.inc#L9349-L9352

provels

@bbcan177
I got an alert today that an update from 3.0.0_2 => 3.0.0_3 was available. I had already updated to 3.0.0_3.
But my package manager now shows 3.0.0_2 as current and wants me to revert.
Any problem here? Thanks for reading.

BBcan177

@provels
No Idea. That is outside of the pkg as its part of the pfSense package manager.

asmodeus

@bbcan177 After upgrading to 3.0.0_3 whitelisting domains from the list of blocked domains (e.g. /pfblockerng/pfblockerng_alerts.php?filterdnsbl=DNSBL_Malicious2) no longer worked - getting 504 Gateway Time-out errors after selecting the domain to whitelist and providing the options (wildcard or not etc.)

The entire UI is unresponsive after that and I can get it back up again via ssh with /etc/rc.php-fpm_restart. I have rolled back to 3.0.0_2 but I still have this issue.

Any ideas on what the issue might be?