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

    Is "mass addition" of IP Aliases possible?

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    4 Posts 2 Posters 374 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.
    • M
      mnlipp
      last edited by

      In a HA setup, I have defined a 1:1-NAT for a VM behind the firewall(s). As required, I have additionally defined an IP Alias using as "interface" the CARP address defined for HA. Works.

      However, I actually want to 1:1-NAT several dozens of VMs. This is easy to do in the NAT definition by using a Network as Internal IP. But how can I do this when defining the IP Aliases as Virtual IPs? Do I really have to do this one-by-one (for dozens of addresses)?

      (I also considered using Proxy ARP as an alternative because you can define these for networks, but this cannot be "bound" to an "interface" that is specified as CARP-Address.)

      Any hints?

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @mnlipp
        last edited by

        @mnlipp https://docs.netgate.com/pfsense/en/latest/firewall/aliases.html#bulk-import-network-aliases but it’s more for one alias with a list.

        Add to config file and restore maybe, if that’s easier to script/generate.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        M 1 Reply Last reply Reply Quote 0
        • M
          mnlipp @SteveITS
          last edited by

          @SteveITS Thanks, but you cannot enter an "IP Alias" (Firewall/Aliases/IP) in the "Address(es)" field when you define an "IP Alias" (Firewall/Virtual IPs/IP Alias).

          1 Reply Last reply Reply Quote 0
          • M
            mnlipp
            last edited by

            So I edited config.xml (plus 63 IP Aliases) and held my breath...

            The web interface of the secondary firewall became unresponsive for several minutes (the command line was still available). During this time, the secondary sent dozens of messages about assuming CARP state whatsoever.

            Eventually, things settled down and I could access the web interface again. I found that both firewalls considered themselves master for the "interface" CARP IP and all Alias IPs associated with it.

            I temporarily disabled CARP on both firewalls and enabled it again. Now things look okay.

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