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

    Issue with port forwarding

    Scheduled Pinned Locked Moved NAT
    5 Posts 3 Posters 504 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.
    • J
      jfre9193
      last edited by jfre9193

      I am attempting to port forward port 2456-2458 UDP to an internal host 10.5.10.3. I see the traffic getting to the host, but when leaving the WAN, it is using the internal IP as the source IP instead of the WAN NAT IP.

      Below is my NAT port forward and the screenshot of the pcap on the WAN interface. I am running pfsense 2.5.1.

      98a70a4a-fea2-4015-ae6c-5cf61b85962c-image.png

      f99d386e-a735-42a2-946b-da4c05e2cc6f-image.png

      KOMK 1 Reply Last reply Reply Quote 0
      • KOMK
        KOM @jfre9193
        last edited by

        @jfre9193 That's really strange. Your rule is fine other than that you should select UDP instead of TCP/UDP for protocol if you're only passing UDP. Just to check, I forwarded a web server in my lab and looked at the trace and it shows all responses from WAN address as expected.

        What do your outbound NAT rules look like? Anything "different" about your config as compared to most?

        J 1 Reply Last reply Reply Quote 0
        • J
          jfre9193 @KOM
          last edited by

          @kom My outbound NAT is as follows. The 10.5.10.3 host is in the Bridge Lab Networks alias.

          b3478180-255d-4454-a0fc-11855e0ac9b6-image.png

          KOMK DerelictD 2 Replies Last reply Reply Quote 0
          • KOMK
            KOM @jfre9193
            last edited by

            @jfre9193 That looks fine as well. I have no idea why it's doing that. I can't easily test your exact config because I have nothing to act as a client/server via UDP. Does it do the same thing if you create another forward to a test web server? It can't be doing that to all traffic from that subnet or nothing would work.

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

              @jfre9193 I believe that is related to this:

              https://redmine.pfsense.org/issues/11805

              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
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.