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

    [Help] - Can't access external IP

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 3 Posters 2.6k 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.
    • G
      gimomars
      last edited by

      Hi experts, I need some help. We are trying to access our in-house web application outside the network. But it seems we cannot access it. Attached is our firewall Port forward, the highlighted is our WAN to access the web app from 192.168.0.31:81. In our DSL Router, it is also port forwarded. Our network setup now is "DSL Router(ISP) - (WAN) > pfSense > router(LAN) > Switch > client" But locally, we are able to access our web app.
      1.JPG
      1.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • G
        gimomars
        last edited by

        Anyone please?

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

          Good list of things to check here:

          https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

          You are going to have to show that the DSL device is actually forwarding the port (packet capture on WAN) before anyone will feel like helping you.

          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
          • C
            chris4916
            last edited by

            NAT deosn't work like this  ???

            Reading what you wrote as NAT rule, you are forwarding to internal address (192.168.0.32) everything reaching WAN interface with destination being "LAN address on port 81".

            I seriously doubt this will ever catch anything because such destination address should never reach you WAN interface  ;)

            Destination address should rather be either your public IP, depending on how your DSL device behaves or at least your pfSense external IP, IMHO  ;)

            Jah Olela Wembo: Les mots se muent en maux quand ils indisposent, agressent ou blessent.

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

              Yup.  I missed that.  I get confused because the firewall rules on WAN are the Real IP of the server, not the WAN address.

              Those port forwards are wrong, as has been pointed out ^^.  The destination address should be WAN address and the NAT address should be the real IP address of the 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
              • G
                gimomars
                last edited by

                Hi guys, thanks for the reply. Here's the output. But still can't access it outside. :(
                Here's my setup:

                The 124.xx.xx.xx is our public IP and the 192.xx.xx.xx is our web app server.

                Also, I've tried it vice versa.

                2.JPG
                2.JPG_thumb

                1 Reply Last reply Reply Quote 0
                • C
                  chris4916
                  last edited by

                  :D  this idea is not to try everything plus the opposite until it works  :P

                  It looks better to me now but still this requires to get the whole understanding.
                  This IP is your public IP. So far so good.
                  The very first step is to ensure that your DSL device will either act as a gateway or route requests reaching external interface to pfSense external interface.
                  Once this is done, you should be able to see, looking at pfSense log, such request reaching pfSense.

                  This is clearly the prerequisite. Don't waste time trying further is this doesn't work.

                  Jah Olela Wembo: Les mots se muent en maux quand ils indisposent, agressent ou blessent.

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

                    Again, we don't know if the ISP router is actually forwarding the port.

                    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
                    • G
                      gimomars
                      last edited by

                      Thanks to all specially to chris. Already working. ;)

                      1 Reply Last reply Reply Quote 0
                      • C
                        chris4916
                        last edited by

                        Some more detailed feedback for those potentially facing similar issue:

                        as suspected and highlighted by Derelict, problem was misalignment between DSL device and pfSense. In order to reach internal web service, if DSL device acts as a router, 2-steps NAT is required. One from internet to pfSense and one from pfSene to internal server.

                        This needs to be consistent all along the path however paying attention not to open everything in order to grant access  ;)

                        Jah Olela Wembo: Les mots se muent en maux quand ils indisposent, agressent ou blessent.

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