Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

firewall: Alias selection issues when same named Alias and Interface Group exist with underscore #8423

Open
2 tasks done
Monviech opened this issue Mar 10, 2025 · 0 comments
Assignees

Comments

@Monviech
Copy link
Member

Monviech commented Mar 10, 2025

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:

  1. Go to 'Firewall->Groups' and create a new Group with the name "TEST_GRP"
  2. Go to 'Firewall->Aliases' and create a new Alias, type "Host(s)", content "127.0.0.1", name "TEST_GRP"
  3. Go to 'Firewall->Rules->TEST_GRP' and create a new rule with the Alias "TEST_GRP" in Source or Destination
  4. 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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants