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

    Multiple Virtual IP's mapped to multiple servers

    Firewalling
    3
    7
    914
    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.
    • P
      petros
      last edited by

      Hi All
      I have been looking through the forum but have not seen this scenario as yet. Hope I didn't miss it.

      I have a public IP on the WAN interface of PFSense. I created two virtual IP's in PFSense that the ISP also assigned to us.  I want to now open ports 443 and 21 to two different backend servers through one virtual IP and port 443 to yet another server on the other virtual IP. Not sure how to do this since 1:1 NAT only seems to map to one internal IP. Any help would be appreciated.

      Thanks.

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Why do you need 1:1 NAT for one port in the first place?

        1 Reply Last reply Reply Quote 0
        • P
          petros
          last edited by

          Well I was looking through and since 1:1 nat maps to an internal IP I figured I could use it to map to one internal server to make its services available on the outside but I didn't see a way to map through that virtual IP to multiple servers on different ports.

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Use port forwards.  You bind to the VIP there.  So forward port 443 on the first VIP to the first server, port 21 on the first VIP to the second server, and port 443 on the second VIP to the third server.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • P
              petros
              last edited by

              Thanks for your reply but I'm still unclear on one thing. When I am doing a port forward in firewall -> Rules -> WAN, I don't see how to bind to the VIP in here.

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                The Destination of the incoming packet into WAN.

                ![Screen Shot 2015-02-03 at 12.20.27 AM.png](/public/imported_attachments/1/Screen Shot 2015-02-03 at 12.20.27 AM.png)
                ![Screen Shot 2015-02-03 at 12.20.27 AM.png_thumb](/public/imported_attachments/1/Screen Shot 2015-02-03 at 12.20.27 AM.png_thumb)

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • P
                  petros
                  last edited by

                  Ah I see. Thanks so much for that.

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