@user12345 said in pfBlockerNG won't complete cron update/reload of DNSBL feeds:

If you do an uninstall of non-devel version with keep settings checked and install the devel will it pull the settings and feeds over or trash those?

It's been a long time since I upgraded to the devel version so my memory is a bit foggy. But in general, if you're going to uninstall pfblocker and want to save the settings in the current configuration you need to check this setting in Pfblocker/General:

645d71a7-ecd6-44b6-9a8e-407637743220-image.png

Now, whether or not those saved settings load right back into the devel version I just can't remember for sure. But if you decide to try it, make sure that you do a complete backup of your whole system - Diagnostics/Backup & Restore. That way you could always roll back to where you where if the setting don't apply correctly.

@scop said in pfBlockerng-devel Certificate Error:

I would like to know if it is possible to redirect to another website like google (if the link is in HTTPS) or just show a message that he can't access to this web site instead of certificate error like in HTTP ?

There is not a way to do this. When a browser goes to an encrypted HTTPS site the first thing the browser is doing is verifying that the response is coming back from the server it intended to communicate with. It does this by verifying the security certificate of the server it communicates with. If the certificate matches the server it loads the page, if not, it will not load the page and will display the HTTPS (ERR_SSL_PROTOCOL_ERROR).

Because of that, if pfblocker attempts to serve up a an error page (classic MITM) the browser will not be able to verify the the page from pfblocker matches the security certificate of the intended server and the browser will block it.

@quasaur Cut it off

@gertjan Thanks for the feedback, good information and insights. I will see how I get on :)

By shut down automaticaly I meant, that it looked like this:

Bildschirmfoto_2021-12-26_18-15-06.png

But as I noticed now, that was, because I forgot to do a Reload after changing to Python Mode.

I now was able to get pfBlockerNG-devel runing as it should in the virtualbox, so everything is good so far.

@nogbadthebad

I made this text file on my ftp server
f4df1815-5ae8-445c-bfec-8c87254e489d-image.png

Then i made a entry like this:
595dc8d3-df02-4e00-9299-40e7b31c3d60-image.png

Finalize with:
e7991d88-fd37-46a2-855a-96d0639add15-image.png

Seems to work:
7cf3a590-f16b-4cc9-b67e-e14864fe469b-image.png

dnsbl.png

category filtering not working when I enter custom domain it works, could you please help me do block things category wise

@fireodo Thanks!

You've made my day 👍 😀

41ce1e68-1e71-41ca-b54d-ecfc5b3740a6-grafik.png

Fine sunday!

@Gertjan @fireodo Great community support!

That error message indicates the GUI code attempted to iterate an empty array variable without verifying the variable is actually defined as an array. My first guess, since the error is from the alerts log, is that the alerts log file is empty and the code is not properly initializing the array when an empty alerts file is encountered.

This is a problem that needs to be addressed by the pfBlockerNG-devel package maintainer. It should also get a bug report created at the Redmine Site here: https://redmine.pfsense.org/projects/pfsense.

@p_bear I don’t know who to blame but if a 3rd party browser works but Safari does not it seems that Netgate is not to blame. It would be nice to know why it does not work so we have something useful to complain to Apple about.

It used to work, I forget if it first broke when Yosemite was released?

@jegr

Read pfBlockerNG IP Reputation
It has a good ending.

The 'Reputation' tab is not available by default.
"Things" need to happen so it can be presented.

Thanks all. I am going to try it with what I have and then see how it goes.

@ghostshell said in Blocked Page:

https://www.reddit.com/r/pfBlockerNG/comments/lnczld/is_dnsbl_webserver_for_ssl_https_connections/

I don't understand what has been said there.
pfBlockerNG-devel logging isn't the issue here. The internal unbound (python, or not) or Lighttpd logs are not available to our browsers.
Our browser see what the web server @10.10.10.10:443 is replying after a page request.
It doesn't understand the answer.

What I think ** what is happening :
Our browser caches web server certificates, as HSTS has become wide spread.
So, our browsers knows what type of cert it should get back from web server. Because it caches certificates, for days, weeks, or even months (so naughty you, you've visited this site already ones without pfBlockerNG ;) - the cert was loaded and cached ).
Many encryption types exist, and the self generated (self signed) cert from the web server of pfBlockerNG cert does not have the right 'format'. If it had the right format, the host name would have been verified (and the date and many more aspects) and then a more understandable error would have been shown.

This issue can not be resolved. Our browsers could show more comprehensible message, true, but it all boils down to :
You wanted to visit a.tld but b.tld replied.
That's a MITM situation and that's a no-go

** Firefox is open source. So the source code will show the exact conditions of the error.

@pulsartiger

pfBlockerNG -devel???? ,on the current version? 3.1.0 should be no problem if you upgrade

if Keep settings is checked, also takes settings, lists, etc. with it when upgrading

BTW:

be careful, since you are switching to new FreeBSD version and the pfBlockerNG - devel has got a lot of new features in the near past...

I have to say you waited a long time for the update, 2.6 is almost here 😉

I think I have found a very easy way to bypass unbound.

In general setup/DNS Resolution Behavior I changed it to use remote DNS servers and ignore local DNS. And in DNS Server Settings I added my local BIND DNS ip addresses.

In client ip address assignment, I still give pfSense IP address for dns, however pfSense just ignores unbound and uses my local dns for resolutions. It’s still utilizing the DNSBL and IP blocklists as they are defined in the firewall floating rules by pfblockerng.

Resolutions now are much faster. Hope this keeps working as I just could not stand unbound resolution performance issues.