Actions
Bug #15989
closedRenaming an alias in MIM does not update firewall and NAT rules with the new alias name
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Multi-Instance Management
Target version:
Start date:
Due date:
% Done:
100%
Estimated time:
Release Notes:
Default
Affected Plus Version:
24.11
Affected Architecture:
Description
Firewall and NAT rules reference the old alias name after the alias has been renamed. To reproduce:
- Enable MIM
- Create the alias
testalias1 - Create a rule with a source set to the alias
testalias1 - Rename
testalias1totestalias2
Updated by Marcos M about 1 year ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Fixed with 02a8538d86ff96c2da3321264dd9d506f3bb0370.
Updated by Georgiy Tyutyunnik about 1 year ago
latest dev fixes the issue
tested on:
25.07-DEVELOPMENT (amd64)
built on Thu Jan 16 6:00:00 UTC 2025
FreeBSD 15.0-CURRENT
Updated by Georgiy Tyutyunnik about 1 year ago
- Status changed from Feedback to Resolved
Updated by Mike Moore about 1 year ago
Trying to patch using the commitID above and I'm unable to fetch.
Updated by Marcos M about 1 year ago
Part of the fix requires a binary update which cannot be applied via the System Patches package.
Updated by Jim Pingle about 1 year ago
- Subject changed from Firewall and NAT rules reference the old alias name after the alias has been renamed to Renaming an alias in MIM does not update firewall and NAT rules with the new alias name
Actions