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

    virual ip From ip alias to CARP type

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    5 Posts 2 Posters 477 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.
    • T
      tosman06
      last edited by

      Hello
      i have setup pfsense using virtual ip's for internal network and external network. I want to setup second pfsense using CARP . Can i just change every ip from ip alias to CARP without having connection issues?

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

        @tosman06
        Change one of the virtual IPs on each interface to a CARP. For the others, edit them and change only the interface to the CARP VIP.

        Remember to also change to outbound NAT on WAN to the CARP VIP and also on your local devices the gateway IP.

        T 1 Reply Last reply Reply Quote 2
        • T
          tosman06 @viragomann
          last edited by

          @viragomann thank you. i don't know if i said well. I don't want to change the ip address. Just the type from ip alias to CARP. Can i just do that before i connect to second pfsense using CARP technology? I mean i want to change in my main pfsense that i am using now. And after that i connect the other pfsense and setup the carp connection! Is that right?

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

            @tosman06
            Best to connect the second pfSense before you start the CARP setup.

            You know, each box needs an interface IP in each subnet. So you need to keep an IP on the primary in each subnet, which you cannot be used on the other in case of failover.
            Configure the interface IPs on the secondary, then connect it to your network. Configure a sync-interface on both.
            Remember to set up the same admin credentials on both nodes.

            Then on the primary configure System > High Availability. Consider to use add sync user with limited privileges.
            Check if the sync to the secondary works.

            Then start with the changes of the virtual IPs.
            Since the secondary goes into backup state as soon as you enable CARP on the primary, the setup should go seamlessly.

            T 1 Reply Last reply Reply Quote 1
            • T
              tosman06 @viragomann
              last edited by

              @viragomann thank you!

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