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 changing the sequence of rules with the "Move selected rule before this rule" button, both the selected and the moved rule will have the same sequence number afterwards.
This makes it look like from a GUI perspective as if the rule did not move to the correct spot, as the sort order for both rules will be the same.
To Reproduce
Steps to reproduce the behavior:
Go to 'Firewall: Automation: Filter'
Create three firewall rules in Floating with the following sequence:
Rule A. 300
Rule B. 350
Rule C. 352
Select the rule 352 and press "move selected rule before this rule" on rule 350.
The rules will now have this sequence:
Rule A. 300
Rule B. 350
Rule C. 350
A clear and concise description of what you expected to happen.
I would have expected this sequence unless there is no available gap:
Rule A. 300
Rule C. 325
Rule B. 350
A clear and concise description of any alternative solutions or workaround you considered.
Adjusting the sequence manually gives the expected result.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 25.1.5 (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 changing the sequence of rules with the "Move selected rule before this rule" button, both the selected and the moved rule will have the same sequence number afterwards.
This makes it look like from a GUI perspective as if the rule did not move to the correct spot, as the sort order for both rules will be the same.
To Reproduce
Steps to reproduce the behavior:
Rule A. 300
Rule B. 350
Rule C. 352
Rule A. 300
Rule B. 350
Rule C. 350
A clear and concise description of what you expected to happen.
I would have expected this sequence unless there is no available gap:
Rule A. 300
Rule C. 325
Rule B. 350
A clear and concise description of any alternative solutions or workaround you considered.
Adjusting the sequence manually gives the expected result.
Environment
Software version used and hardware type if relevant, e.g.:
OPNsense 25.1.5 (amd64)
The text was updated successfully, but these errors were encountered: