Bug #2362

Deleting last/only port forward doesn't remove from secondary

Added by Chris Buechler about 1 year ago. Updated 3 months ago.

Status:Resolved Start date:04/08/2012
Priority:Low Due date:
Assignee:Renato Botelho % Done:

100%
Category:Config sync
Target version:2.1
Affected version:All Affected Architecture:

Description

if you delete the last/only port forward from the primary, it doesn't get removed from the secondary on config sync.

Associated revisions

Revision a1fb7d61
Added by Renato Botelho 3 months ago

Fully sync filter and nat sections. Fixes #2362

History

#1 Updated by Jim P 3 months ago

Does this still happen on 2.1? I thought I fixed all of these not too long ago.

#2 Updated by Chris Buechler 3 months ago

  • Target version set to 2.1

Yeah it does as of Friday's snapshot at least.

#3 Updated by Renato Botelho 3 months ago

  • Assignee set to Renato Botelho

#4 Updated by Renato Botelho 3 months ago

Same happens for last/only filter rule. I'm working on a solution.

#5 Updated by Renato Botelho 3 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#6 Updated by Ermal Luçi 3 months ago

If those seciton need to be synched no matter what than its better to remove the options completely from the filter sync configuration page to not create the impression this is controllable.

#7 Updated by Renato Botelho 3 months ago

I don't believe option should be removed since it is still valid for rules from Master you don't want to sync.

- Rules set to nosync on Master won't be send to Slave.
- All rules on Slave will be overwritten.

#8 Updated by Chris Buechler 3 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF