Project

General

Profile

Actions
Copy link

Bug #10941

closed

pfBlockerNG-devel Bug in ipv6 lists when updating

Added by Rick Coats over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
pfBlockerNG
Target version:
-
Start date:
09/30/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.4.5-p1
Affected Plus Version:
Affected Architecture:

Description

I posted initially in the forum with screenshots in case it is something I am doing but during update the pfblocker ipv6 alias's get clobbered in the rules. This has happened before, so it is not a new issue with today's update.

During update the ipv6 Alias's get a _v4 added to the end of the alias name, and it was changed to protocol IPv4. Of course, then the firewall throws all kinds of errors since it doesn't see it as a legit alias. My rules are in an interface group if that makes a difference, but I have seen it happen when I had rules in the WAN interface also in the past.

https://forum.netgate.com/topic/157274/bug-in-ipv6-lists-when-updating

Is there a reason why a separate _v4 and _v6 alias needs to be generated? Seems like a single Alias with both types would work just as well.

I am on:
pfBlockerNG-devel 2.2.5_35 but it has been in the prior versions also.

2.4.5-RELEASE-p1 (amd64)
built on Tue Jun 02 17:51:17 EDT 2020
FreeBSD 11.3-STABLE

Files

pfsense_status_output.tgz (383 KB) pfsense_status_output.tgz Rick Coats, 10/02/2020 12:27 PM
Actions
Copy link

Also available in: Atom PDF