Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    Changes on Primary sync incorrect changes on secondary

    HA/CARP/VIPs
    2
    2
    855
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rickpo12 last edited by

      I have two pfsense firewalls that are running in a VMware 5.5 environment.  I have the following setup on each:

      em0 = WAN
      em1 = LAN
      em2 = PFSync
      CARP setup such that the primary syncs to the secondary FW

      I do not yet have these firewalls (FW) running live yet.  Here is what I am seeing in my testing so far.

      1.  I create a rule on the primary and the rule gets sync'd to the secondary fine
      2.  If I create a new "Interface" on the primary is does not get sync'd to the secondary so I have to also create it there.  NOTE:  I create on Interface for each VLAN that I setup on my network within VMware.
      3.  I create a VIP (CARP) on the primary and it gets sync'd to the secondary fine.

      Problem:
      4. At one point I created a new rule on the primary and when it was sync'd with the secondary it messed everything up on the secondary.  Meaning, the rule information on the secondary was inconsistent with the primary.  For example, if I had only three rules defined on the primary, like

      Rule1: Proto=IPV4 * : Source=* : Port=* : Dest=VLAN2000 : Port=* : GW=* : Queue=none; Description= rule1
      Rule2: Proto=IPV4 * : Source=* : Port=* : Dest=VLAN2001 : Port=* : GW=* : Queue=none; Description= rule2
      Rule3: Proto=IPV4 * : Source=* : Port=* : Dest=VLAN2002 : Port=* : GW=* : Queue=none; Description= rule3

      The above rules sync'd ok over to the secondary FW.  I was playing around with some other things and later I created a new rule called Rule4 like:

      Rule4: Proto=IPV4 * : Source=* : Port=* : Dest=VLAN2003 : Port=* : GW=* : Queue=none; Description= rule4

      When this rule was sync'd to the secondary it messed the rest of the rules up and ended up with:

      Rule1: Proto=IPV4 * : Source=* : Port=* : Dest=VLAN2000 : Port=* : GW=* : Queue=none; Description= rule1
      Rule2: Proto=IPV4 * : Source=* : Port=* : Dest=VLAN2001 : Port=* : GW=* : Queue=none; Description= rule2
      Rule3: Proto=IPV4 * : Source=* : Port=* : Dest=VLAN2003 : Port=* : GW=* : Queue=none; Description= rule4
      Rule4: Proto=IPV4 * : Source=* : Port=* : Dest=* : Port=* : GW=* : Queue=none; Description= <blank>After comparing the setups of the primary to the secondary the only thing that I noticed is the I had created an additional internet called VLAN2100 on the primary and I did not also create this on the secondary.  So I created it on the secondary.

      Here is my concern, I have been running pfsense as a FW for a number of year and it has been rock solid, but this FW was not setup in and HA config and using CARP.  Now that I am playing with CARP, things do not seem as rock solid, or I just need to better understand how CARP works and what I have to do to work around these issues.

      Has anyone had much experience running CARP in a large production environment?  Has anyone had issues like what I ahve described?  What is the cause of these issues.

      Thank you

      Rick</blank>

      1 Reply Last reply Reply Quote 0
      • jimp
        jimp Rebel Alliance Developer Netgate last edited by

        Interfaces > (assign)
        Make sure all interfaces exist on both units and have been assigned in the correct order.

        That behavior can be seen when you have interfaces out of order on one system.

        Also make sure their internal names line up, e.g. OPT3 on primary is the same as OPT3 on the secondary.

        You might have to edit config.xml on the backup to fix the order properly in some cases

        1 Reply Last reply Reply Quote 0
        • First post
          Last post

        Products

        • Platform Overview
        • TNSR
        • pfSense
        • Appliances

        Services

        • Training
        • Professional Services

        Support

        • Subscription Plans
        • Contact Support
        • Product Lifecycle
        • Documentation

        News

        • Media Coverage
        • Press
        • Events

        Resources

        • Blog
        • FAQ
        • Find a Partner
        • Resource Library
        • Security Information

        Company

        • About Us
        • Careers
        • Partners
        • Contact Us
        • Legal
        Our Mission

        We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

        Subscribe to our Newsletter

        Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

        © 2021 Rubicon Communications, LLC | Privacy Policy