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

    Usable WAN CARP IPs (if any) for NAT, routing etc. to computers behind pfsense

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    4 Posts 2 Posters 2.0k 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.
    • S
      scar
      last edited by

      so i am using 3 public IPs for the CARP setup… one shared IP and one for each WAN interface on the two pfsense boxes.  can any of those IPs also be used for NAT and other routing to my computers behind pfsense, or are they strickly already taken and i should start with my 4th public IP?  it seems i might be able to get away using the shared CARP VIP, but what do i know? (not much)  maybe i can use the other two also if i add them as CARP VIPs?  thanks

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by

        The IP addresses assigned to the physical interfaces cannot also be CARP IP addresses.  It is possible to use them for doing port forwards, although they would not have the same failover benefits as CARP VIPs.

        If you have additional IP addresses, those can also be used as CARP VIP addresses on this cluster.  Assuming your ISP gave you a /29, you could use the first two IPs as the real IPs for each WAN on your cluster, the third for your shared VIP and the other 3 as additional shared VIPs for additional web servers, mail servers or whatever you need.  This is obviously dependent on your actual setup.

        1 Reply Last reply Reply Quote 0
        • S
          scar
          last edited by

          thanks… so what purpose does the third IP serve?  why couldn't i also use it in the same way i might use the remaining three IPs mentioned in your example?

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            You can.  That shared IP becomes the source IP of any traffic egressing from your network and you're able to NAT traffic inbound on that interface.

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