Project

General

Profile

Actions

Bug #14132

closed

Aliases of the same name current as previously deleted will not be respected properly

Added by Steven Cedrone over 1 year ago. Updated over 1 year ago.

Status:
Not a Bug
Priority:
Low
Assignee:
-
Category:
Aliases / Tables
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
23.05
Affected Architecture:
All

Description

This problem is hard to describe so I'll give as much information as possible as best as I can.

-Alias was created and assigned in a traffic tagging scheme to push out a specific connection. (Worked fine)
-Deleted Alias and stopped tagging this specific traffic with this Alias.
-Time passed, we created the same Alias name but with different hosts associated with it.

Firewall would not tag and pass traffic properly.

We really spent a lot of time trying to figure this out, finally having tried everything else we re-created a new Alias with the same hosts/nets and used it instead in our traffic schemes and it worked flawlessly. As a test we then assigned it back to the other Alias with the exact same settings and it would not tag traffic properly.

So it appears in some instances that either Alias history or it in relation to using it traffic tagging schemes after having been changed causes the bug.

If I can be of any help I'm happy to be contacted.

Actions

Also available in: Atom PDF