Project

General

Profile

Actions
Copy link

Bug #8996

closed

pfBlockerNG not like CloudFlare DNS

Added by DRago_Angel [InV@DER] about 7 years ago. Updated about 7 years ago.

Status:
Bogus
Priority:
Very High
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
10/03/2018
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
All
Affected Plus Version:
Affected Architecture:
All

Description

Hi all, pfBlockerNG use IP 1.1.1.1 is list of IPs is NULL, so any time list is null CloudFlare DNS can be banned, filtered or even allowed (if filter elsewhere used as native) to illegal info. Could this fixed by creating logic about that NULL list must be not created? Or if not - could it point to one of test supnets described in RFC 5737: 192.0.2.0/24 198.51.100.0/24 203.0.113.0/24 and for IPv6 list to 2001:db8::/32 as RFC 3849 "Addresses used in documentation and example source code". Thank you.

Actions
Copy link

Also available in: Atom PDF