Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
After updating to version 26.1, a display error was noticed in the new rules. This only affects translated versions, in my case, German.
The legacy rules were transferred to the new rules using the wizard. The existing automatic rules were apparently not exported or imported, but rather loaded in the code via MVC. This is where the display error occurred. The Allow/Deny symbol is always set to Allow, which is obviously incorrect for rules that are set to Default Deny. See screenshot.
To Reproduce
Steps to reproduce the behavior:
- Use a version prior to 26.1
- Set the language to German
- Update to 26.1
- Export the existing rules using the Migration Assistant
- Import the exported rules using the Migration Assistant
- Open "New" under Firewall Rules
- Inspect the automatic rules.
- You will see, for example, that the "Default deny / state violation rule" is marked with the "Allow" symbol.
Expected behavior
The symbol should be the Deny symbol.
Describe alternatives you considered
When querying api/firewall/filter/search_rule/, there appears to be an unintended translation of the action field. With legacy rules, the field is translated into German, which I believe is a bug. With MVC rules, no translation is performed; instead, the %action field is added as a translated version.
Perhaps this is a possible solution? Not tested!
hartmann-daniel@d94fabb
Screenshots
English Version (no Problem):

German Version (Problem in First Line)

Relevant log files
No
Additional context
No
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 26.1.7_1-amd64
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Describe the bug
After updating to version 26.1, a display error was noticed in the new rules. This only affects translated versions, in my case, German.
The legacy rules were transferred to the new rules using the wizard. The existing automatic rules were apparently not exported or imported, but rather loaded in the code via MVC. This is where the display error occurred. The Allow/Deny symbol is always set to Allow, which is obviously incorrect for rules that are set to Default Deny. See screenshot.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The symbol should be the Deny symbol.
Describe alternatives you considered
When querying
api/firewall/filter/search_rule/, there appears to be an unintended translation of theactionfield. With legacy rules, the field is translated into German, which I believe is a bug. With MVC rules, no translation is performed; instead, the%actionfield is added as a translated version.Perhaps this is a possible solution? Not tested!
hartmann-daniel@d94fabb
Screenshots
English Version (no Problem):

German Version (Problem in First Line)

Relevant log files
No
Additional context
No
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 26.1.7_1-amd64