I recently added the ISC_Miner list and looks like it may be dead too.

@publictoiletbowl said in allow fb messenger but:

but no luck. because in pihole it works

No luck because it works ? 😊 Isn't it the other way around ?
It works with pi-hole, so ... can you discover why it works for pi-hole ?

Btw : what is 'facebook' ?
You means their web site ?
Whatsapp ?
Messenger ?
Other ?
And also :
From a web browser ?
From an app on a pad or phone ?

The nasty thing about facebook : (and Google, Apple, Microsoft, Amazon and this list is very long)
They use (own) thousands of IP addresses. These addresses change all the time.
A fact is that a browser access will use destination port 443 as it is https only.
Apps can use any port they want.

The good news is ; they own their own networks, or AS and pfBlockerng can block these, but that means nothing will work anymore, not even the web browser access.

So, I'm curious, who does pi-hole does it ?

Hummm.

@Gertjan said in pfBlocker still not working even in 24.11 version:

Copy past the Log that will show up (it's text, so copy text please).

I missed that.
In that log there can be info related to any issues. Issues you're looking for.

Also - probably not related :
b1d657a2-1801-4468-8747-b577b8cca361-image.png

so delete for the moment :

7819b6d2-a93d-464e-9ab8-4067b18b0cea-image.png

and then delete the error message with :

8b37e6df-6238-4480-a903-547af1730cdc-image.png

edit :

Did you conclude that you didn't loose any Internet access while reloading ?

@Gertjan
Looks like the issue is resolved. changing from "fall back to remote" to "ignore remote". I also made sure that there was NO other references for external DNS servers.

I've also been working on making sure that all of the downloads are working. I have found that some have changed policies or paths.

THANK YOU!

@reberhar SUCCESS

After the latest upgrade for pfBlocker I started to have the same problems all over again and none of my other methods fixed it.

I finally got onsite and have learned some useful things.

First I have 2 Netgear GS108PEs, and one worked properly in this situation and the other did not. After thinking about it I realized that the one that functioned had 802.1q VLAN enabled. So I enabled 802.1q VLAN on the one that was not functioning correctly and the problem disappeared. No I didn't make any VLANs on the second unit, although the first unit I mentioned does have them. I just enabled 802.1q VLAN.

I reasoned that perhaps multicast was somehow involved in this. (duh) So I worked through enabling multicast on my Ubiquiti 24 port smart switch that had failed with this challenge earlier. It actually involved the Cloud Key as well.

This I did just on the two ports I am using for HA, not the entire switch.

That worked too and is still working.

😊

Yes I know, multicast is mentioned in the HA diagnostics write up. I guess I was just not following through. Actually, I was just a little unsure how to proceed. I have other very smart switches that have been testy in this pfBlockerng / HA environment. I am excited to try this approach with them.

@Jabiru

Be aware that this exists : Update Frequency of GeoIP do you can't update their lists xx hours, you will be punished (== blocked). As most lists don't even change each week, a weekly update is more then enough.

Also, visit the https://www.maxmind.com/en/account/sign-in and check your account. Didn't they change something last year, so you had to 'redo' ( ? ) your registration (get new codes etc - can't recall )

edit : this :

@Jabiru said in pfBlocker configuration for MaxMind GeoIP:

401 Unauthorized

smells like a account problem.

@Gertjan This is Noted, and Thank you

@uniqueusername said in pfBlockerNG Crash Report version 3.2.0_16 pfSense version 24.11 DNSBL UT1 Adult Category added:

I just enabled the UT1 category Adult to block port ....

Not that one.
The fast reply : You can't buy a "3100" (a 1 Mega RAM arm device) and then use a functionality' that asks for way more processor power, and way (like 4 or 8 times) more memory.

c804433a-62c2-4025-9de9-cac0d59e166a-image.png

The thing is, this file is not just large, it's more like huge ... and even if you can download it it, the next step will bring the system down : it has (hundreds of) thousands of lines, and pfBlockerNG will read them in one by one in memory (...,) together with all the other DNSBL you've also selected, and then it will remove the doubles ... and then filters them for the known DNSBL host names to be whitelisted, and so one. This task will bring PHP to it's knees.
I know, because on my 4100 with 4 Mbytes most often it will fail also, with the same error.
Put a "post it" on it, with : "try me again when I have the memory" ;)

@elexir said in Error after package update:

pfBlockerNG-Dev

The latest version, or development version, is written with the latest version of pfSense in mind.
That not 24.03, but 24.11.
Next time : always start by checking what the latest pfSense version is and if needed, update pfSense first.
Then, start to think about upgrading packages.

@jrey Thank you for clarifying.

The asn is downloading (I did have to do the above shell command to force it first time), but the expectation was it would download immediately upon a first save or update that included asn.

Once primed, once per day more than enough. After all, how often do asn assignments actually get changed?

@JClayton
I'm having the same issue with pfsense 2.6 and the last pfblockerng package
did you find any solution?
thanks