You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating an Interface Group, and an Alias, which both have the exact same name with underscore (e.g. TEST_GRP), the Alias will resolve incorrectly in a Firewall rule when selecting the Alias (to TEST_GRP net).
When a group or Alias does not contain an underscore (e.g. both named TEST), this does not seem to happen, though it might also be wrong.
To Reproduce
Steps to reproduce the behavior:
Go to 'Firewall->Groups' and create a new Group with the name "TEST_GRP"
Go to 'Firewall->Aliases' and create a new Alias, type "Host(s)", content "127.0.0.1", name "TEST_GRP"
Go to 'Firewall->Rules->TEST_GRP' and create a new rule with the Alias "TEST_GRP" in Source or Destination
It will resolve to "TEST_GRP net" after saving
Expected behavior
Only the created Alias should be selected.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 25.1.2 (amd64).
The text was updated successfully, but these errors were encountered:
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
When creating an Interface Group, and an Alias, which both have the exact same name with underscore (e.g. TEST_GRP), the Alias will resolve incorrectly in a Firewall rule when selecting the Alias (to TEST_GRP net).
When a group or Alias does not contain an underscore (e.g. both named TEST), this does not seem to happen, though it might also be wrong.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Only the created Alias should be selected.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 25.1.2 (amd64).
The text was updated successfully, but these errors were encountered: