I scan the logs every once and a while when running a Force Reload All rather and look for feeds that come back regularly as having 0 in the final count column after de-duplication as the lists load, looking to remove feeds that are already part of others rather and ones that are down altogether. Even when feed lists get abandoned from updates over time doesn't mean they're no longer effective unless if until they become merged into other lists that you use. https://filterlists.com/ has many other lists that can be added as long as the right list format is selected but same case there as far as which lists are actively maintained

@alan_touring

Ok, that explains.
The function "pfb_collect_localhost()" checks all known interfaces for DHCP and other settings to collect local IP addresses used.
If an interface is declared, but empty (no settings what so ever), then the error you've shown is totally understandable.

Btw : this is not a pfBlockerNG bug : the <OPT3> shouldn't be there.

@BBcan177

after going to _20

isn't jason is a horror movie reference ?

as it appears in the _20 release code as
'application/x-ndjason',

The list fails
Spamhaus_Drop_v4 ] Downloading update .. 200 OK
[PFB_FILTER - 17] Failed or invalid Mime Type: [application/x-ndjson|0]

now s/b json the correct way.

'application/x-ndjson',

if it was working with ndjason (and it was for a while), seems they may have fixed a typo upstream
previously it was:
[ Spamhaus_Drop_v4 ] Downloading update .. 200 OK
[PFB_FILTER - 17] Failed or invalid Mime Type: [application/x-ndjason|0]

@tedquade No, they've basically blocked its use with the T&C page. That was an issue in the past though.

@TravisH

From the info block -- I don't think anything has changed here --- your best to use Alias types and make the rules yourself, then when you place them in a specific order you want, they will stay in that order. Any of the "auto generated rules" will always sort based on the Firewall 'Auto' Rule Order.

"Refer to the blue infoblock 'List Action' icon in the IPv4 tab for details on how to use 'Alias type' (ie: 'Alias Deny') instead of 'Auto generated rules', if required for your network design. Select the 'Order' of the Rules  Selecting 'original format', sets pfBlockerNG rules at the top of the Firewall TAB.  Selecting any other 'Order' will re-order all the rules to the format indicated! "

@BBcan177

Excellent, with fix 3.2.0_20 crash has been solved ! Thanks so much for all your support !

@jrey Thanks for reply.

I have not registered for, and am not inclined to register for an IPInfo token as I am not intentionally trying to do anything with ASN features.

Isn't enabling ASN Reporting going to create more notifications, not remove the one I'm trying to get rid of?

Thanks

lists are working fine now....

i just updated from pfBlocker devel v.3.2.0_17 to pfBlocker devel v.3.2.0_19

@rle well not understanding what problem your wanting to solve then.. Via dns your not going to be able to resolve trivy-server, the only way to resolve that is via it device talking to itself, ie its own name - or via a broadcast, or something like mdns which would be trivy-server.local and the device itself answering.

In what scenario would asking for trivy-server of dns work, since it is not a valid dns query - so how would you allow it or not allow it in pfblocker in the first place.

@Antibiotic

6d334907-5940-4713-8648-83a23ed2c3d7-image.png

was made for you ...

@smolka_J said in Custom Client Lists in pfBlockerNG:

I'm waiting for pfSense's move to the Linux kernel that's coming down the road ...

Im sorry, what ?

@mzeid said in Custom block list for specific subnet ?:

pfblockerng block different lists for specific subnet

While adding a new DNSBL feed here Firewal > lpfBlockerNG > DNSBL > DNSBL you can not select "use feeds only on interface LAN & LAN2" or "use feed only on interface LAN2 only", DNSBL feeds (filtering) apply to all interfaces.
That is, this is valid when the "Python mode" is used.
A feature request ?

Btw : the above is 'very AFAIK, of course.
For a school I would probably consider using a Pi-hole also

As the DNSB Python filtering script is (I guess) aware of the requester IP, thus the network, thus the interface, it could be capable of 'per interface' filtering.

In the past, before we were using pfBlockerng, and used handcrafted 'unbound' config rules, here :

d451e5e1-6886-42ee-b577-9ea9f9d427c8-image.png

we were able to set up DNSBL files 'per interface' (per network).
This meant that this one was our guide line.

@mzeid said in Custom block list for specific subnet ?:

bypassing one of the IP addresses

That's the policy group setting :

e41d7108-7cd8-424e-acd9-d3b82e996bd6-image.png

and from now on, this devices will bypass DNSBL filtering

Btw :

@mzeid said in Custom block list for specific subnet ?:

teacher's computer

I'm pretty sure the teacher doesn't mind he can't visit these sites neither ^^

@johnpoz I get back here tmrw ... it's late already in my timezone.
Thanks so far!

edit: currently sick since monday ... I'll get back here asap

Hi
I have a similar problem. I have had PfSense for many years with no issues with PfblockerNG, recently I upgraded to latest version of PfBlockerNG 3.2.10. I lost full internet access for my single LAN. Turn off the pfblocker and reboot the firewall through GUI or console, Internet connectivity is back on. After trying to troubleshoot for a while, finally gave up and did a fresh install, problem is still the same.
Another odd thing noticed in 3.2.10 version of pfblockerng is that the geoip to block and edit which countries to block, edit button was missing. Not sure if others have this issue or is this a bug in this release.

Any ideas on what is causing the pfblockerng to break internet connectivity. I have a simple design:

WAN interface, DHCP LAN interface, DHCP Class C addresses Pfsense current stable version 24.03 rel1 PfblockerNG 3.2.10 (currently not installed on a fresh install). Want to install and back with blocking ranges of IPs based on location/country

I have another test PC that I can install the pfblockerng and test out the internet connectivity, hoping you can provide a tip to solve this issue.

@tman222 Yes, disabling the "States Removal" for the particular list(s) is what I did as a workaround. I looked for the code responsible when I made the post and recall pfblockerng is behaving as described in my first post. That is, if an IP address in a list is found in states, and "States Removal" is enabled, regardless of the "List Action", the state is removed. I retired my investigation since.