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

    Why can't I access forwarded ports on my WAN IP from my LAN

    Scheduled Pinned Locked Moved NAT
    8 Posts 5 Posters 7.4k 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.
    • E
      Eddie55
      last edited by

      Hello all

      Before we begin i already read

      Port Forward Troubleshooting
      https://doc.pfsense.org/index.php/Port_Forward_Troubleshooting

      Why can't I access forwarded ports on my WAN IP from my LAN/OPTx networks
      https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

      I am running 2.3.2-RELEASE-p1 (amd64)
      DNS RESOLVER is being used NOT DNS FORWARDED

      I have a DVR with cameras i want to access inside and outside my LAN using my cell phone using only 1 FQDN from DDNS that works inside and outside my LAN. This worked flawlessly using a tomato firmware flashed onto my old ASUS RT-N16.

      I have a very simple network with all computers in a workgroup.
      No domains or anything fancy like that behind a pfsense box.
      pfSense is running a DUAL WAN with Forwarding Mode enabled.
      192.168.x.x/21

      I can ping BOTH my WAN IP address and DDNS from outside AND inside my network through my cell phone.

      When inside my LAN using wifi my device can not connect to the DVR (FQDN:PORT) even though i can ping it with FQDN… i have to turn wifi off to connect to my DVR which is crazy.

      I read the manual above and have turned on NAT Reflection but still no joy.

      I dont care if i use the WAN IP address or FQDN i just need it to work.

      Split DNS is not going to work because i have multiple DVR's and SERVERS inside the LAN that i need to access and from what i understand Split DNS only works if its 1 FQDN for 1 SERVER/DVR and since i have multiple SERVER/DVR i cant use SPLIT DNS.

      Here are my current relevant settings that may be useful
      http://imgur.com/a/W9F63

      Any help would be appreciated.
      Thanks in Advance

      1 Reply Last reply Reply Quote 0
      • P
        Powercat80
        last edited by

        I am having the same issue connecting to my Home Automation via the LAN.  Port forwarding is working properly, as I can access the system remotely while wifi is off.  Please advise.

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

          Split DNS is not going to work because i have multiple DVR's and SERVERS inside the LAN that i need to access and from what i understand Split DNS only works if its 1 FQDN for 1 SERVER/DVR and since i have multiple SERVER/DVR i cant use SPLIT DNS.

          How are you accessing these various servers and devices via WAN?  They all have to have either an exclusive IP address or port unless you're running some reverse proxy.

          1 Reply Last reply Reply Quote 0
          • J
            jlevesque
            last edited by

            you could install a reverse proxy package having 1 dns record for each server (squid)

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

              I'm not asking how you would do it theoretically, I'm asking how he is specifically doing it.  I'm guessing he has the one WAN IP and is using a variety of port forwards to forward WAN traffic to selected servers and ports.

              It might be possible to put all these devices on a separate network and then port-forward from LAN1 to LAN2 along with split DNS.

              1 Reply Last reply Reply Quote 0
              • P
                pki
                last edited by

                Hi.

                Maybe my problem is by the same issue.

                I have upgraded from 2.0.1 which worked for years. First the NAT reflection seems to work fine or maybe i don't notice it. For hosts which have rules with limiters the reflection does not work.

                1 Reply Last reply Reply Quote 0
                • P
                  pki
                  last edited by

                  Self reply, workaround for me was to use que instead of limiter for download (direction out). Hope it will be fixed in 2.4….
                  https://redmine.pfsense.org/issues/4326

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

                    Limiters + NAT is fixed in 2.4.

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