Project

General

Profile

Bug #26

"No XMLRPC Sync" still sends data to CARP Slaves, and CARP slave rules marques NO Sync are erased

Added by Rudolph Sand about 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Rules / NAT
Target version:
Start date:
07/04/2009
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

Simple setup using two 1.2.3-rc1 (one full, one embeded), everything runs fine...
My goal simply is to redirect ports 123 and 53 from a LAN CARP IP to each pfsense's LAN IP, thus the need for the "no XMLRPC Sync", but

In NAT:
Create a rule on master, click "no XMLRPC Sync", click, or not, create a fw rule
Check the slave(s), a line with blank fields was added in NAT
If you delete it, it will get re-created on next sync

In the same fashion, if i create a new rule on slaves and check "no XMLRPC Sync", the rule is erased

Associated revisions

Revision 89a55272 (diff)
Added by Chris Buechler about 11 years ago

MFC fix from Ermal

Fixes #26

History

#1 Updated by Ermal Lu├ži about 11 years ago

  • Status changed from New to Resolved

For 2.0 i fixed it.
For 1.2.3 the same fix as here applies
https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/bb46d659ddfb624044dd5b076dc67a404efe6f29

just that the code is under filter.inc on 1.2.3

#3 Updated by Wouter de Jong almost 11 years ago

Somehow, this still does not work in the (current) latest snapshot of 1.2.3 of 2009-07-18 19:20.

See [[http://cvstrac.pfsense.com/tktview?tn=1939]]

Code does seem to have been updated with the commit of Chris Buechler, so something else must go wrong ?

#4 Updated by Chris Buechler almost 11 years ago

  • Status changed from Resolved to New
  • Priority changed from High to Normal
  • Affected Version set to All

#5 Updated by Scott Ullrich almost 11 years ago

  • Status changed from New to Resolved

This code exists in 1.2.3. Also fixed a bug with nosync. This should be resolved.

Also available in: Atom PDF