I upgraded to 24.11 RC from command line, and now all is working in GUI again.

Well getting at a loss now. I checked the logs and the only thing that comes up when I start the onedrive app is a whole lot of beacon hits which I am led to believe has to do with google and not on drive. No other blocks that I can see. I disabled dnsbl and tried again. Same result. I then disabled all my IP block lists and same thing. One drive just sits there saying signing in. As soon as I take of the enable for pfBlocker under the general tab and hit save and onedrive logs in. I can then re-enable pfBlocker and everything works fine after a reload for the DNSBL

@dmshel80 I have the same issue. I get data from all but the Map isn't working: [image: 1731776618136-c8586e92-df62-4a7f-b9fc-7ea22b7bf948-image-resized.png]

You can also click on the (i) for more info. [image: 1731512434685-screenshot-2024-11-13-at-15.38.53.png]

@cyrcocq I'm having the same issue I believe, wondering if you found a solution? For what its worth I think I found that if you check "Enable Domain/AS" it stops working with any ip addresses in the list.

@Phantom_Stage Either offline or no longer exist.

A lil bit later, but I was having this same problem, and I fix it doing this: My DNS was: Host -> Active Directory DNS -> pfSense I changed to: Host -> pfSense Now all hosts I put in Python Group Policy bypass DNSBL rules. If you have Active Directory, you need to add your local domain in DNS Resolver -> Domain Overrides to resolve internal hosts.

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

@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 !

Updated pfBlocker devel from 3.2.0_19 to 3.2.0_20 ..all good (on x86 qemu), GEOIP / ASN entrys etc. all working well, Thank you for the Update!

@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.