Todo #14073
openShalla block list is offline but still available in pfBlocker
0%
Description
The Shalla Services blocklist went offline permanently in January 2022. It's still available as a list option in the pfSense GUI (Firewall > PfBlockerNG > DNSBL > DNSBL Category) but of course pfBlocker can't download it.
https://forum.netgate.com/topic/169241/shalla-list-off
https://www.shallalist.de/
UPDATE PROCESS START [ v3.2.0_3 ] [ 03/4/23 19:17:01 ] ===[ DNSBL Process ]================================================ Loading DNSBL Statistics... completed Loading DNSBL SafeSearch... disabled Loading DNSBL Whitelist... completed Downloading Blacklist Database(s) [ shallalist (~10MB) ] ... Please wait ... Failed Shallalist ... Failed [ StevenBlack_ADs ] exists. [ 03/4/23 19:17:03 ]
Updated by Kris Phillips over 1 year ago
- Status changed from New to Confirmed
Confirmed in 23.01 and 2.7:
UPDATE PROCESS START [ v3.2.0_4 ] [ 04/9/23 01:34:56 ]
===[ DNSBL Process ]================================================
Loading DNSBL Statistics... completed
Loading DNSBL SafeSearch... disabled
Loading DNSBL Whitelist... completed
Downloading Blacklist Database(s) [ shallalist (~10MB) ] ... Please wait ...
Failed Shallalist ... Failed
Updated by Mike Moore about 1 year ago
Can we get this package cleaned up at least with the removal of the list.
Its causing confusion from users.
Updated by Kris Phillips about 1 year ago
This is an issue on the pfSense Plus 23.09.X branch still.
Updated by OpIT GmbH about 1 year ago
Mike Moore wrote in #note-3:
Can we get this package cleaned up at least with the removal of the list.
Its causing confusion from users.
Yes thats true
Updated by Kris Phillips 9 months ago
This still affects 23.09.1 and 24.03's builds of pfBlockerNG as of today. This source should be removed as soon as possible from the available sources list. It continues to cause user confusion.
Updated by Mike Moore 9 months ago
Kris we know what the issue is but how does it get cleaned up?
Seems like something someone internal can push the maintainer for instead of updating the notes every few months that the problem is present.