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

    Re - Compatibility between VRRP and CARP

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    22 Posts 2 Posters 3.1k Views
    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.
    • empbillyE
      empbilly @viragomann
      last edited by

      @viragomann

      Ok. My doubt is if I need to enable this option on pfbackup:

      System > high availability sync

      Syncronize states?

      https://eliasmoraispereira.wordpress.com/

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @empbilly
        last edited by

        @empbilly
        Yes, only the states sync.
        So the state are in sync, when failback to the primary and the connections persist.

        But don't enable XMLRPC sync on the secondary.
        Config changes must be made on the primary then.

        empbillyE 1 Reply Last reply Reply Quote 0
        • empbillyE
          empbilly @viragomann
          last edited by

          @viragomann

          pfsync Synchronize Peer IP needs a IP of pfmaster?

          https://eliasmoraispereira.wordpress.com/

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @empbilly
            last edited by

            @empbilly
            No, not on the backup!

            empbillyE 1 Reply Last reply Reply Quote 0
            • empbillyE
              empbilly @viragomann
              last edited by

              @viragomann

              Thanks!!! Sorry for so many questions!!! :)

              After setting the IP Peer failover in pfmaster's dhcp, in the dhcp lease option, the pool state needs to be normal, right?

              Both pfmaster and pfbackup status is recover.

              What causes this?

              https://eliasmoraispereira.wordpress.com/

              V 1 Reply Last reply Reply Quote 0
              • V
                viragomann @empbilly
                last edited by

                @empbilly
                Maybe missing the Failover peer IP in the DHCP settings?
                This must be stated on the primary only.

                empbillyE 2 Replies Last reply Reply Quote 0
                • empbillyE
                  empbilly @viragomann
                  last edited by

                  @viragomann

                  Actually, I did. Monday I will review the settings.

                  Thanks again!!!!

                  https://eliasmoraispereira.wordpress.com/

                  1 Reply Last reply Reply Quote 0
                  • empbillyE
                    empbilly @viragomann
                    last edited by

                    @viragomann

                    We have DNS Forwarder enabled. Do I need to select the VIPs in the DNS Forwarder?

                    https://eliasmoraispereira.wordpress.com/

                    V 1 Reply Last reply Reply Quote 0
                    • V
                      viragomann @empbilly
                      last edited by

                      @empbilly said in Re - Compatibility between VRRP and CARP:

                      We have DNS Forwarder enabled. Do I need to select the VIPs in the DNS Forwarder?

                      Not clear, what you mean. There are no IP to select in the Forwarder settings.

                      But if you are talking about the DHCP settings, then yes, it doesn't matter if you're running the Resolver or Forwarder or any other DNS server, you have to enter it's IP here. For these ones running on pfSense, this is the interface VIP.

                      empbillyE 1 Reply Last reply Reply Quote 0
                      • empbillyE
                        empbilly @viragomann
                        last edited by

                        @viragomann

                        I meant that.

                        eeabdb9a-21ff-4b1d-905e-e9fe52915b0e-image.png

                        But there is still something I am not getting, because I have enabled pfbackup on our network and the WAN is as MASTER in pfbackup and the dhcp leases are not as "normal".

                        Any hints on what to look for?

                        https://eliasmoraispereira.wordpress.com/

                        V 1 Reply Last reply Reply Quote 0
                        • V
                          viragomann @empbilly
                          last edited by

                          @empbilly
                          These are the IPs, the Resolver is listening on. Yes, you should select the respective VIPs there or even keep "all".

                          because I have enabled pfbackup on our network and the WAN is as MASTER in pfbackup and the dhcp leases are not as "normal".

                          Don't know, what you mean with the term "the dhcp leases are not as normal".
                          However, I just rarely use the DHCP server on an HA system, so I'm sadly not experienced with it.
                          If you have trouble with that you should better open a separate thread to get viable help, I think.

                          empbillyE 1 Reply Last reply Reply Quote 0
                          • empbillyE
                            empbilly @viragomann
                            last edited by

                            @viragomann

                            Status > DHCP Leases

                            Pool Status
                            7c9ddad5-07aa-4d91-ac82-fbaf5ca332b7-image.png

                            It is now as "recover state". Regardless if I put pfbackup on the network, with Failover peer IP configured, it is still in "recover state".

                            https://eliasmoraispereira.wordpress.com/

                            1 Reply Last reply Reply Quote 0
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.