Actions
Bug #12678
closed
Applying firewall rule changes does not clear dirty flag for aliases subsystem
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
22.05
Release Notes:
Default
Affected Version:
2.5.2
Affected Architecture:
Description
How to reproduce:
1) Change Aliases
2) You'll see a message on top of the page:
The alias list has been changed. The changes must be applied for them to take effect.
3) Change any firewall rules, and press apply (
filter_configure() execution)4) Aliases changes are applied, but the "The changes must be applied for them to take effect." note still there
Updated by Viktor Gurov almost 3 years ago
same issue with the NAT and Shaper pages
fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/553
Updated by Jim Pingle almost 3 years ago
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
- Target version set to CE-Next
- Plus Target Version set to 22.01
Updated by Jim Pingle almost 3 years ago
- Plus Target Version changed from 22.01 to 22.05
Updated by Viktor Gurov almost 3 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset c04144d193bbd6583a5000e409ec4692729bc89e.
Updated by Christopher Cope almost 3 years ago
- Status changed from Feedback to Resolved
Tested and working correctly on
22.05-DEVELOPMENT (amd64) built on Mon Feb 21 06:18:46 UTC 2022 FreeBSD 12.3-STABLE
Updated by Jim Pingle almost 3 years ago
- Target version changed from CE-Next to 2.7.0
Updated by Jim Pingle over 2 years ago
- Subject changed from Applying firewall rules changes does not clear Aliases subsystem dirty flag to Applying firewall rule changes does not clear dirty flag for aliases subsystem
Updating subject for release notes.
Actions