Navigation

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

    Static Port Oubound NAT not working [it's working]

    NAT
    3
    4
    2374
    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
      miafya last edited by

      Not sure what I'm missing here…

      I've turned on manual outbound NAT because I want static port mapping on one of our subnets. NAT is working great but it's still randomizing the ports.

      See attached screen shot (second rule for the 10.11.0.0 network).

      When I show states it's still showing entries like this:
      10.11.0.154:64033 -> public.wan.address:64033 -> 64.12.25.191:443

      So I assume it's still randomizing ports.

      What am I missing?

      1 Reply Last reply Reply Quote 0
      • GruensFroeschli
        GruensFroeschli last edited by

        When I show states it's still showing entries like this:
        10.11.0.154:64033 -> public.wan.address:64033 -> 64.12.25.191:443

        Where do you see randomization?
        Your client initiates a connection from 10.11.0.154:64033.
        The pfSense uses the same port on the outside public.wan.address:64033. (<– The same as on the client)
        The connection goes to it's destination 64.12.25.191:443.

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • D
          danswartz last edited by

          Seconded.  It looks like it's doing exactly what it is supposed to be doing!

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

            Looks like you're right. Sorry about the confusion!

            I had assumed it wasn't working because the desired behavior (allowing some gaming consoles behind the pfsense box to nat properly) wasn't working. It turned out to be a problem with allowing multicast traffic on the subnet for UPnP.

            Thanks for your help.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post