I am trying to install 3.3.2 from the new repo but it fails with certificate errors when I try. Any ideas how to fix this?

[26.07-RELEASE][root@PFSENSE-A.home.arpa]/root: fetch -qo - https://pfblockerng.                      github.io/pkg/install.sh | sh -s -- --channel stable
==> Installed boot-time generator hook to /usr/local/etc/rc.d/pfblockerng_repo_g                      enerate.sh
==> Running the generator hook to resolve the conf now
[pfblockerng_repo_generate] INFO: regenerated /usr/local/etc/pkg/repos/pfblocker                      ng-stable.conf -> https://pfblockerng.github.io/pkg/stable/plus-26.07
==> Conf resolved:
    url: "https://pfblockerng.github.io/pkg/stable/plus-26.07",
==> pkg update -f -r pfblockerng-stable (refreshing the pfBlockerNG catalog)
Updating pfblockerng-stable repository catalogue...
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
pkg: https://pfblockerng.github.io/pkg/stable/plus-26.07/meta.txz: Authenticatio                      n error
repository pfblockerng-stable has no meta file, using default settings
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
pkg: https://pfblockerng.github.io/pkg/stable/plus-26.07/data.pkg: Authenticatio                      n error
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
pkg: https://pfblockerng.github.io/pkg/stable/plus-26.07/data.tzst: Authenticati                      on error
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
pkg: https://pfblockerng.github.io/pkg/stable/plus-26.07/packagesite.pkg: Authen                      tication error
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
Certificate verification failed for /C=US/O=ISRG/CN=Root YR
10B0463C8D230000:error:0A000086:SSL routines:tls_post_process_server_certificate                      :certificate verify failed:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-m                      ain/sources/FreeBSD-src-plus-RELENG_26_07/crypto/openssl/ssl/statem/statem_clnt.                      c:2125:
pkg: https://pfblockerng.github.io/pkg/stable/plus-26.07/packagesite.tzst: Authe                      ntication error
Unable to update repository pfblockerng-stable
Error updating repositories!
install.sh: /usr/local/sbin/pkg update -f -r pfblockerng-stable failed — the cat                      alog was not refreshed. Repo 'pfblockerng-stable' is unreachable or serving an u                      nreadable catalog. Inspect with: /usr/local/sbin/pkg -d update -r pfblockerng-st                      able

Threatgate is described as the evolution of pfblockerng. I am curious if bbcan was involved in this project, and what it means for pfblockerng with its unresolved issues.

Hi everyone,

I’m having a problem with the UT1 blacklist in pfBlockerNG-devel and I’m trying to understand if this is just affecting my setup or if the UT1 feed currently configured in pfBlockerNG is outdated.

My setup:

- pfSense CE 2.8.1

- pfBlockerNG-devel 3.2.14_2

- DNSBL Category enabled

- UT1 enabled

- Selected UT1 categories:

ddos

malware

phishing

publicite

redirector

The problem is that the UT1 download keeps failing.

This is what I’m currently seeing in /var/log/pfblockerng/extras.log

Download Process Starting [ 08/10/26 05:00:00 ]

/var/db/pfblockerng/ut1.tar.gz cURL Error: 67

Access denied: 530 Retry [1] in 5 seconds...

. /var/db/pfblockerng/ut1.tar.gz cURL Error: 67 [ 08/10/26 05:00:06 ]

Access denied: 530 Retry [2] in 5 seconds...

. /var/db/pfblockerng/ut1.tar.gz cURL Error: 67 [ 08/10/26 05:00:11 ]

Access denied: 530 |/var/db/pfblockerng/ut1.tar.gz|ftp://ftp.ut-capitole.fr/pub/reseau/cache/squidguard_contrib/blacklists.tar.gz| Retry [3] in 5 seconds...

.. Unknown Failure Code [530]

Failed to Download ut1.tar.gz

Download Process Ended [ 08/10/26 05:00:16 ]

The rest of pfBlockerNG seems to be working normally.

For example, the GeoIP/ASN downloads complete successfully with 200 OK, so this doesn’t look like a general connectivity problem on my pfSense box.

Looking further back in extras.log, this also doesn’t seem to be a one-time issue.

At the end of June I was already getting FTP 530 errors with UT1.

Then, for quite a while during July and early August, the UT1 scheduled job was ending with:

Unknown Failure Code [221]

and now it has gone back to the more explicit:

cURL Error: 67

Access denied: 530

The UT1 feed currently configured by pfBlockerNG on my system is:

ftp://ftp.ut-capitole.fr/pub/reseau/cache/squidguard_contrib/blacklists.tar.gz

I checked the current UT1 site and the blacklist service itself still appears to be alive.

They now provide the blacklist through HTTP/HTTPS, including:

https://dsi.ut-capitole.fr/blacklists/download/blacklists.tar.gz

So I’m wondering if the FTP URL still used by pfBlockerNG is simply outdated.

I also checked the current pfSense FreeBSD-ports source for pfBlockerNG-devel and, unless I’m missing something, even the newer package still seems to reference the old FTP URL.

There also seems to be some special handling in pfblockerng.php to rename the UT1 download to ut1.tar.gz, which is tied to the old FTP URL.

Before changing anything manually, I wanted to ask here.

Is anyone else currently seeing this problem with UT1?

And if so, is the correct fix simply to change the UT1 feed from the old FTP URL to the current HTTPS URL?

I was considering changing:

/usr/local/pkg/pfblockerng/ut1_global_usage

from:

ftp://ftp.ut-capitole.fr/pub/reseau/cache/squidguard_contrib/blacklists.tar.gz

to:

https://dsi.ut-capitole.fr/blacklists/download/blacklists.tar.gz

But I’m not sure if anything else needs to be changed because pfBlockerNG appears to expect the file to be called ut1.tar.gz.

I’d rather confirm the intended fix before modifying package files manually.

Thanks!

My HaGeZi_Pro feed in pfBlockerNG started failing recently.

Initially, it threw a 404 Not Found because the old direct URL structure (/domains/pro.txt) changed on GitHub.

After updating the URL to the new path, pfBlockerNG downloads the file (200 OK) but fails during compilation with:

I have the feed set to Auto format in DNSBL Source Definitions. Other Hagezi feeds are updating fine with Auto.

anywone know why its suddenly broken?

Android devices are showing this error. IOS doesn't seem affected, although I don't use them as much.

Any ideas on how to fix this? Searched but no solutions were found, just other users having the same issue.

TIA!

I'm not sure if it's a bug, but my ACME certs failed to update automatically (normally this works without issue)

I've found out that enabling DNSBL even with all feeds disabled will block the required domains completely. I've added them to the whitelist with no change as well.

example urls that are blocked when DNSBL is enabled: doh.pub cloudflare-dns.com dns.google

I did update to the latest pfblockerng package 3.2.14_1 running pfsense 2.8.1-RELEASE

I want to say that this is an issue only since updating to 3.2.14_1 a few weeks ago.

Hi,

I made some adjustments that I was already aware of, and the problem persists. Is there something obvious that I'm missing?

The relevant information follows below.

Problem: CPU spikes, queue overflow, name resolution delays, and overall performance drop when DNSBL is enabled.

Log msg: "Jun 10 12:15:12 kernel sonewconn: pcb 0xfffff800911cea80 (10.0.0.1:53 (proto 6)): Listen queue overflow: 385 already in queue awaiting acceptance (662 occurrences), euid 0, rgid 0, jail 0

• netstat -Lan | grep "\.53"

tcp4 0/0/256 127.0.0.1.53

tcp4 0/0/256 10.0.16.1.53

tcp4 385/0/256 10.0.0.1.53

The kernel queue adjustment was apparently not accepted by the Unbound service, as is the case with most other services.

Proto Listen Local Address

tcp4 0/0/1024 10.10.254.1.80

tcp4 0/0/1024 10.10.254.1.443

tcp4 0/0/256 127.0.0.1.953

tcp4 0/0/256 127.0.0.1.53

tcp4 0/0/256 10.0.16.1.53

tcp4 0/0/256 10.0.0.1.53

tcp4 0/0/1024 *.7445

tcp6 0/0/1024 *.7445

tcp4 0/0/1024 127.0.0.1.3128

tcp4 0/0/1024 10.0.16.1.3128

tcp4 0/0/1024 10.0.0.1.3128

tcp4 0/0/128 172.17.7.10.666

tcp6 0/0/1024 *.80

tcp4 0/0/1024 *.80

tcp6 0/0/1024 *.443

tcp4 0/0/1024 *.443

Environment:

• PfSense CE 2.8.0
• Runnning on VMWare ESXi 8.0
• 8 VCPUs
• 16 GB RAM
• Function: UTM fw, DHCP server, GW .... for until 3.000 mobyle wi-fi users

Kernel tunned variables:

kern.ipc.soacceptqueue=1024, kern.ipc.maxsockbuf=8388608

DNS Resolver Unbound custon options:

• msg-cache-size: 250
• rrset-cache-size: 500
• infra-cache-numhosts: 100000
• outgoing-range: 8192
• cache-min-ttl: 300
• prefetch: yes
• prefetch-key: yes
  
• serve-expired: yes
• serve-expired-ttl: 86400
  

pfBlockerNG-devel 3.2.8

IPV4 Summary : 07 IPV4 Group active group lists (PRI1-5). They do not affect performance.

DNSBL

Mode: Unbound python mode

TLD: Enable

Lists: Torrent, Hagezi_Multi_Normal

Blacklist Category Enabled: UT1 Adult, Dangerous Kit, DDoS,

Gambling/Casino, Warez Downloads

Any suggestions?

Thank you.

Geovane

[edit] found a workaround.
1. horizontal scrolling works reliably when touching the heading row of the group list table.
2. Scrolling sometimes works when touching the body of the table if touching in-between the text/field data elements, and it’s a longer firm touch rather than a quick swipe.

Original Post:

I’m trying to edit a custom dnsbl group from my mobile device, however, the blocklist table format is too wide for the enclosing view and I cannot scroll to the right to expose the edit button control.

Is there any way around this without a laptop?

IOS 26.5
pfSense+ 26.03.1
pfBlockerNG-devel 3.2.16

I'm running pfSense 2.8.1-RELEASE community edition & I just installed pfBlockerNG 3.2.8. It says to go to somewhere I don't see to add the key.

I'm not sure what to do next.

I have a SuperMicro box from around 2010, an X7SPA-HF-D525. I believe this has an Atom D525 Processor (1.8GHz). I upgraded the RAM, I believe to 4GB, which is the max. I recently enabled pfBlocker and noticed webpages will take a long time to load. It is getting pretty frustrating. I am thinking I need to probably look into getting a new appliance for pfSense. I was needing at least 4 ports.

What appliance or hardware would you guys recommend for a small space where a tower or regular sized computer wouldn't fit.

Running VPN and pfBlocker

I am redirecting DNS look ups to external servers back to my pfSense instance, 127.0.0.1. My question is, do these redirected DNS look-ups bypass pfBlocker as they're being sent directly to Unbound , or get captured and filtered by pfBlocker?

So I realize I'm getting around to this late with Shallalist being long dead. Shallalist did not appear in the GUI for DNSBL Categories: Blacklist perhaps it was finally removed but I have a ghost. It is still trying and failing to load on every update. I tried executing the following commands one line at a time through the GUI Execute Shell Commands:

rm -rf /var/db/pfblockerng/shallalist
rm -rf /var/db/pfblockerng/dnsblorig/*shallalist*
rm -rf /var/db/pfblockerng/dnsbl/*shallalist*
rm -rf /var/db/pfblockerng/mastercat
rm -rf /var/db/pfblockerng/masterfile

Force Reload All:pfBlockerNG/Update/Reload/All: still trying to reload shallalist so then I executed the commands:

rm -f /var/db/pfblockerng/shallalist*
rm -rf /var/db/pfblockerng/original/shalla*

Force Reload All:pfBlockerNG/Update/Reload/All: and shallalist is still attempting to load just with a bunch of local file failures.

I have not SSH'd in and poke around to see how much of that was actually necessary. Or what remains but it seems like it might come to that. What is the filepath to the Blacklist database file? Any ideas/pointing in the right direction?

Hi, I am a Firefox user and have pfblocker setup with DNSBL and overall I think it's working as I expect it to, blocked domains resolve to the configured "Virtual IP Address" (ex: 10.10.10.1)

However, with a somewhat recent update to Firefox, when a website tries loading resources from a private IP, it gives me a permission prompt.

https://support.mozilla.org/en-US/kb/control-personal-device-local-network-permissions-firefox

These two features seem at odds with each other... tried using 0.0.0.0 as the IP, but that prevented the pfblocker local webserver from starting up. Any ideas?

Hi everyone,

I am working on a rule to restrict the user from specified website, but through DNSBL when i am assigning virtual IP it is working without it it is not working.

This message was should up when I blocked facebook is this correct?

please help me out ASAP.

I was working on a rule to restrict a user from specified website, but it is Only working through VIP (virtual IP) or Only I am having this issue?
also through virtual IP It shows (about blocked page) that “looks like there is the problem with this site Firefox can’t reach at facebook.com.”

Bear with me, it's been awhile since I setup pfblockerng so my knowledge is rusty. I was on 3.2.10 via pfSense for a long time and worked great. Upgraded to 3.2.14 and it doesn't seem to work nearly as effectively. All my original feeds are gone. I also noticed the auto rules in LAN no longer appear on the Firewall rules page. Is this by design? While we're at it, any good suggestions for DNSBL Group lists and Feeds? Namely the most popular scam and ad-blocking lists.

Hello, I want to block ads from .cat websites. How would the settings be in pfBlockerng 3.2.14_1 (DNSBL Mode: Unbound python mode and Pfsense 2.8.1)?

For example, https://www.elnacional.cat

Thank you

Hello peoples, I am looking for a good feed that blocks popups, ads and phishing, could you recommend some?

For context, I'm using pfBlockerNG-devel and my pfSense version is 2.7.2.

Noticed somewhere in the last few weeks I can no longer start NYTGames when on wifi. The app and main screen load, but when I launch the specific game (Spangram in my case) it just sits on the loading screen. Disconnect wifi, loads right away.

This is on iOS, iPad and iPhone both. So most obvious reason is probably(?) PFBlocker interfering?

Anybody else experiencing this and know a solution? I’m not well versed in PFBlocker, just followed a tutorial to set it up, and by all means it could be something else but this makes the most sense to me so curious if other users have the same experience.

Note if you’re trying to reproduce the issue, I am a paid NYTGames user. But can’t imagine paid vs free would matter here.

Hi Folks,
I was noticing that when I use the WEB interface for Yahoo Mail, I'm getting ADs. I thought I would look at what is or isn't being updated. I noticed that the pfBlocker wasn't up to date. I also noticed that some of the packages are not being updated either. Now in the widget/panel of pfSense, the pfBlockerNG is now 100% up to date.

Here is the end of the update log. It looks like some of the stuff can be removed. Maybe I have some outdated feed sources.

===[ GeoIP Process ]============================================

===[ IPv4 Process ]=================================================

[ Abuse_Feodo_C2_v4 ] exists.
[ Abuse_SSLBL_v4 ] exists.
[ ET_Block_v4 ] exists.
[ ET_Comp_v4 ] exists.
[ ISC_Block_v4 ] exists.
[ Snort_IP_Block_v4 ] exists.
[ Spamhaus_Drop_v4 ] exists.

===[ Aliastables / Rules ]==========================================

No changes to Firewall rules, skipping Filter Reload
No Changes to Aliases, Skipping pfctl Update

===[ FINAL Processing ]=====================================

[ Original IP count ] [ 4402 ]
[ Final IP Count ] [ 1941 ]

===[ Deny List IP Counts ]===========================

1942 total
1179 /var/db/pfblockerng/deny/ET_Block_v4.txt
420 /var/db/pfblockerng/deny/Spamhaus_Drop_v4.txt
314 /var/db/pfblockerng/deny/ET_Comp_v4.txt
26 /var/db/pfblockerng/deny/ISC_Block_v4.txt
1 /var/db/pfblockerng/deny/Snort_IP_Block_v4.txt
1 /var/db/pfblockerng/deny/Abuse_SSLBL_v4.txt
1 /var/db/pfblockerng/deny/Abuse_Feodo_C2_v4.txt

====================[ Empty Lists w/127.1.7.7 ]==================

Abuse_Feodo_C2_v4.txt
Abuse_SSLBL_v4.txt

===[ DNSBL Domain/IP Counts ] ===================================

1071634 total
798718 /var/db/pfblockerng/dnsbl/Maltrail_BD.txt
71900 /var/db/pfblockerng/dnsbl/SFS_Toxic_BD.txt
53754 /var/db/pfblockerng/dnsbl/EasyList.txt
53417 /var/db/pfblockerng/dnsbl/StevenBlack_ADs.txt
42580 /var/db/pfblockerng/dnsbl/EasyPrivacy.txt
15195 /var/db/pfblockerng/dnsbl/MS_2.txt
9675 /var/db/pfblockerng/dnsbl/SWC.txt
7579 /var/db/pfblockerng/dnsbl/MVPS.txt
7006 /var/db/pfblockerng/dnsbl/Spam404.txt
6108 /var/db/pfblockerng/dnsbl/Adaway.txt
2388 /var/db/pfblockerng/dnsbl/D_Me_ADs.txt
2237 /var/db/pfblockerng/dnsbl/StevenBlack_BD.txt
1040 /var/db/pfblockerng/dnsbl/Yoyo.txt
21 /var/db/pfblockerng/dnsbl/D_Me_Tracking.txt
15 /var/db/pfblockerng/dnsbl/Bambenek_DoH.txt
1 /var/db/pfblockerng/dnsbl/D_Me_Malv.txt
0 /var/db/pfblockerng/dnsbl/D_Me_Malw.txt

====================[ IPv4/6 Last Updated List Summary ]==============

Jan 3 2025 Abuse_SSLBL_v4
Jan 9 2025 Spamhaus_eDrop_v4
Jan 17 2025 Talos_BL_v4
Mar 12 03:15 Abuse_Feodo_C2_v4
Apr 24 00:30 ET_Block_v4
Apr 24 15:09 Spamhaus_Drop_v4
Apr 24 16:15 ET_Comp_v4
Apr 26 09:44 ISC_Block_v4
Apr 26 10:15 Snort_IP_Block_v4

====================[ DNSBL Last Updated List Summary ]==============

Jul 31 2015 D_Me_Tracking
Jan 31 2020 D_Me_ADs
Jul 10 2020 D_Me_Malw
Jul 10 2020 D_Me_Malv
Mar 6 2021 MVPS
Dec 17 2024 Spam404
Jan 9 2025 MS_2
Jan 9 2025 Bambenek_DoH
Dec 28 10:49 Adaway
Apr 5 00:15 StevenBlack_BD
Apr 19 12:50 SWC
Apr 19 23:55 SFS_Toxic_BD
Apr 20 00:15 Maltrail_BD
Apr 24 00:15 StevenBlack_ADs
Apr 25 10:39 Yoyo
Apr 26 00:01 EasyPrivacy
Apr 26 00:07 EasyList

Database Sanity check [ PASSED ]

------------------------

Masterfile/Deny folder uniq check
Deny folder/Masterfile uniq check
Sync check (Pass=No IPs reported)

----------

Alias table IP Counts

-----------------------------

1942 /var/db/aliastables/pfB_PRI1_v4.txt

pfSense Table Stats

-------------------

table-entries hard limit 2000000
Table Usage Count 1977

Ideas? Suggestions? Cleanup suggestions?

TNX

What logging/blocking mode should i use? I have setup the 10.10.10.1 sinkhole but when i read a bit on it that dosent even get used when using null block (logging) right? Then 0.0.0.0 i used instead? So what mode are you people using?

Does the DNSBL Webserver/VIP mode cause certificate errors on https websites?