Project

General

Profile

Actions

Bug #7421

closed

Unresolvable port alias is omitted from rule rather than generating an error

Added by Jim Pingle over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Rules / NAT
Target version:
Start date:
03/23/2017
Due date:
% Done:

100%

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

Description

GUI validation prevents this from happening, but if a port alias is missing from the firewall configuration, a rule using that alias is still included in the ruleset, but without the port. No errors are generated by the firewall.

The only way this can happen is if the user, against all advice, hand edits the configuration and accidentally omits or deletes the port alias.

That said, we toss out rules that have missing source/destination address aliases, so we should be consistent and toss out missing port alias rules the same way.

To me, I have a patch.

Actions

Also available in: Atom PDF