Actions
Bug #16416
closedIt's possible to add DNSBL Virtual IP with subnet mask if to use Restore Configuration option in Diagnostics -> Backup&Restore
Status:
Rejected
Priority:
Low
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:
Description
Tested on 25.07.1 (pfBlockerNG 3.2.7)
If to use incorrect DNSBL Virtual IP in config.xml file ('DNSBL VIP with subnet mask.png'), it's possible to restore this config on pfSense without getting any errors/alerts ('restored DNSBL VIP with mask.png').
DNSBL doesn't work with this wrong VIP and it's hard to troubleshoot why it's happening as there are no any informative logs.
I think one more check function should be added which wipes the subnet mask while booting or applying pfBlockerNG settings.
It's not urgent to fix but we already had one customer who restored such config with incorrect DNSBL VIP and it took lots of time to find the reason why DNSBL wasn't able to start.
Files
Actions