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

    Outbound NAT to VIP not working :o(

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 2 Posters 1.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 Offline
      Supermule Banned
      last edited by

      Having real issues with 2.1.4 and outbound NAT to Virtual IP.

      Anybody that can comfirm this working?

      1 Reply Last reply Reply Quote 0
      • S Offline
        Supermule Banned
        last edited by

        Something really wrong….

        Whenever I change this to the parent interface address defined under WAN, then it works on all boxes.

        When I change them to Virtual IP's then they cant connect to the internet. Inbound routing works fine on VIP.

        Outbound doesnt.

        1 Reply Last reply Reply Quote 0
        • S Offline
          Supermule Banned
          last edited by

          Here are the screendumps…

          firewall_rules.jpg
          firewall_rules.jpg_thumb
          outboundNAT.jpg
          outboundNAT.jpg_thumb

          1 Reply Last reply Reply Quote 0
          • S Offline
            Supermule Banned
            last edited by

            This is the test setup AMD64 vers. 2.1.4.

            pfsense_system.jpg
            pfsense_system.jpg_thumb

            1 Reply Last reply Reply Quote 0
            • S Offline
              Supermule Banned
              last edited by

              I have created a case on Redmine concerning this.

              1 Reply Last reply Reply Quote 0
              • V Offline
                vindenesen
                last edited by

                I just tested this using 2.1.4. Created an IP alias on a OPT-interface, and created a outbound NAT rule that translated the source address to the IP alias. Tested it against an Apache http server, and the client address displayed in the log was the IP alias I created. So at my setup it works, but it could be that it's related to the WAN-interface, which I'm not able to test with.

                Support the project by buying a Gold Subscription at https://portal.pfsense.org
                Running pfSense on SuperMicro A1SRI-2758F with ESXi 5.5

                1 Reply Last reply Reply Quote 0
                • S Offline
                  Supermule Banned
                  last edited by

                  I use alias' as well on the opt1 interface that I renamed DMZ.

                  So the routing is from one alias to VIP on WAN interface.

                  But even routing from the OPT1/DMZ interface using any instead of alias but keeping the VIP on the WAN, still render it useless regarding traffic redirection to VIP.

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