Bug #14335
closed
Associated firewall rule for NAT port forward does not inherit ``nosync`` property, gets synchronized
Added by Jim Pingle about 1 year ago.
Updated almost 1 year ago.
Plus Target Version:
23.05
Description
If a user creates a port forward and checks the box to disable XMLRPC sync, this property is not copied to an automatic associated firewall rule. As a consequence, the port forward does not synchronize (expected) but the associated firewall rule ends up on the secondary (unexpected).
It may not be possible to correct existing rules, but it can be fixed for new entries going forward.
- Status changed from New to In Progress
- Assignee set to Jim Pingle
- Plus Target Version changed from 23.09 to 23.05
This is a much smaller fix than I anticipated. Commit inbound.
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
In my testing before and after applying the patch, both the port forward and firewall-associated rule get copied to the secondary even though the No XMLRPC Sync option is checked.
Please check.
That is a separate issue: #14316 -- I found this one when testing and fixing that one.
To test this one properly, apply the fix for #14316 first.
- Follows Regression #14316: Filter/NAT rules configured with "No XMLRPC Sync" enabled are still synchronized added
- Status changed from Feedback to Resolved
Working as expected on current snapshots. Associated firewall rule inherits the nosync property, and neither the NAT rule nor the associated firewall rule appear on the secondary.
Also available in: Atom
PDF
Updated by 
Updated by