Bug #14132


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

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

Not a Bug
Aliases / Tables
Target version:
Start date:
Due date:
% Done:


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


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 #1

Updated by Jim Pingle about 1 year ago

  • Status changed from New to Not a Bug

There isn't nearly enough evidence here of a bug and not something else happening in the configuration or existing states. There isn't anything special retained about an alias after it's removed like that, unless some other bit still in your configuration was referencing it in a way that wasn't removed before removing the alias.

This site is not for support or diagnostic discussion.

For assistance in solving problems, please post on the Netgate Forum .

See Reporting Issues with pfSense Software for more information.

Actions #2

Updated by Steven Cedrone about 1 year ago

Thanks for the update. You sparked an idea about not everything being removed when an Alias is changed.

I'm going to look through the exported XML file of the master box we use for programming before we export the configuration and then use portions of this on other PfSense installs by importing sections (to save time), so it is possible our master box has left-overs from previous configurations that then get passed on so the problem can be reduplicated.

If that is the case I'll consult Netgate support to confirm before posting another bug report.


Also available in: Atom PDF