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

Simple NAT question

Scheduled Pinned Locked Moved NAT
7 Posts 3 Posters 1.5k 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.
  • V
    victor1211
    last edited by Jul 26, 2016, 6:28 PM

    Dear all,

    What I am doing here wrong as this NAT Rule used to work and still working for the past NAT rules  but I think during the past few pfsense releases updates it stopped working for new NAT rules.

    for NAT and rules please see attached picture, for the working NATs I dont see anything under rules which is surprising but could have changed in some releases of pfsense.

    am i missing anything as I said it used to work great but not sure what changed in the new releases.
    NAT.PNG
    NAT.PNG_thumb
    firewall.PNG
    firewall.PNG_thumb

    1 Reply Last reply Reply Quote 0
    • C
      cmb
      last edited by Jul 26, 2016, 6:34 PM

      That's correct. Nothing changed in new releases. Go through the troubleshooting steps.
      https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

      Likely one of 2-5 under common problems.

      1 Reply Last reply Reply Quote 0
      • V
        victor1211
        last edited by Jul 26, 2016, 7:28 PM

        thanks for the quick response CMB but I verified 2 - 5 but nothing applies to this situation as I know NAT working for other devices and ports but not for the newer one and nothing blocked on the client machine. Logs are not very helpful to see what might block it but in reality nothing is being blocked by the ISP or client machine which is outside of that network.

        1 Reply Last reply Reply Quote 0
        • V
          viragomann
          last edited by Jul 26, 2016, 8:19 PM

          Do a packet capture from Diagnostic menu on the WAN interface, while trying the access from outside, to ensure the packets arrive at pfSense.
          If you see the packets, do a packet capture on the interface the destination host is connected to, to see if here is everything okay.

          1 Reply Last reply Reply Quote 0
          • V
            victor1211
            last edited by Jul 26, 2016, 10:23 PM

            thanks viragomann I do see packets on the WAN interface showing my remote IP I am trying to access from but it shows a different port which I guess may be normal but I am not sure what I am looking at on the LAN packet capture for the destination device. I dont see its IP being requested.

            1 Reply Last reply Reply Quote 0
            • V
              viragomann
              last edited by Jul 27, 2016, 7:52 AM

              On WAN you have to see packet with destination <wan address="">:61009 and responses from this address:port
              on LAN packets to 192.168.200.14:80 and responses from it.

              If your not sure post the output here.</wan>

              1 Reply Last reply Reply Quote 0
              • V
                victor1211
                last edited by Jul 29, 2016, 4:43 PM

                I figured its some corruption in the firmware - I used another machine and it worked great. Thanks for your help. I will close this case now

                1 Reply Last reply Reply Quote 0
                2 out of 7
                • First post
                  2/7
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                  This community forum collects and processes your personal information.
                  consent.not_received