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

    LAN can't visit IPV4 WAN

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    10 Posts 3 Posters 2.3k 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.
    • Y
      yon
      last edited by

      now the LAN's  computer can not visit via IPv4 wan IP open LAN'S server. I have setup NAT for server.

      like:  192.168.101.100–-- via wan ip 61.150.5.x-- nat ---192.168.101.3 IIS server

      PF v2.2.x normal work.

      now i using version is :

      2.3-ALPHA (amd64)
      built on Sun Dec 20 01:04:26 CST 2015
      FreeBSD 10.2-STABLE

      and why firewall block these ip ?  I have config allow all ipv6 ip pass.

      1750_3.png
      1750_3.png_thumb

      If you are interested in free peering for clearnet and dn42,contact me !

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Fix your DNS instead of relying on the NAT reflection clusterfuck. Other than that, sounds like duplicate of https://forum.pfsense.org/index.php?topic=104236.0

        1 Reply Last reply Reply Quote 0
        • Y
          yon
          last edited by

          @doktornotor:

          Fix your DNS instead of relying on the NAT reflection clusterfuck. Other than that, sounds like duplicate of https://forum.pfsense.org/index.php?topic=104236.0

          I am sure it not so dns, becasue I use ip address still can't visit.  I have changed any. I find firewall log show blocked.

          If you are interested in free peering for clearnet and dn42,contact me !

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            You totally missed the point. You should use the LAN IP. Not the WAN IP. Doesn't matter whether directly or via DNS. Pointing to your WAN when the server is on your LAN is just wrong.

            1 Reply Last reply Reply Quote 0
            • Y
              yon
              last edited by

              @doktornotor:

              You totally missed the point. You should use the LAN IP. Not the WAN IP. Doesn't matter whether directly or via DNS. Pointing to your WAN when the server is on your LAN is just wrong.

              I am say that my LAN web server config NAT with pubilc IPv4 address.  such as:  web server LAN is 192.168.101.3 then its public ip address 61.150.4.238, then when I use the  public ip address 61.150.4.238 visit that web server from LAN other computer or internet.

              If you are interested in free peering for clearnet and dn42,contact me !

              1 Reply Last reply Reply Quote 0
              • Y
                yon
                last edited by

                this firewall blocked ipv6 address?  I have config allow all ip for pass. why it is still show blocked?

                2302_4.png
                2302_4.png_thumb

                If you are interested in free peering for clearnet and dn42,contact me !

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  @yon:

                  I am say that my LAN web server config NAT with pubilc IPv4 address.

                  Yes. I understand perfectly fine what you are saying. I already answered your question 2 times but you are just not reading! Uh.

                  https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

                  1 Reply Last reply Reply Quote 0
                  • Y
                    yon
                    last edited by

                    @doktornotor:

                    @yon:

                    I am say that my LAN web server config NAT with pubilc IPv4 address.

                    Yes. I understand perfectly fine what you are saying. I already answered your question 2 times but you are just not reading! Uh.

                    https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

                    kind man, thank you!  ;D

                    I try change the NAT+Proxy mode to Pure NAT  just can visit pulic wan ip.

                    And why firewall blocked some IP ?  I have setup allow all ip.

                    0037_5.png_thumb
                    0037_5.png
                    0038_6.png
                    0038_6.png_thumb
                    0050_7.png
                    0050_7.png_thumb
                    0050_8.png
                    0050_8.png_thumb

                    If you are interested in free peering for clearnet and dn42,contact me !

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

                      @doktornotor:

                      @yon:

                      I am say that my LAN web server config NAT with pubilc IPv4 address.

                      Yes. I understand perfectly fine what you are saying. I already answered your question 2 times but you are just not reading! Uh.

                      https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks

                      Split DNS isn't an option when you have multiple ports being forward to different devices. I am having this issue too and it worked until recently with the NAT+PROXY configuration.

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        @pyrodex:

                        Split DNS isn't an option when you have multiple ports being forward to different devices.

                        Sure it is… Just use different hostnames for different devices. Kinda normal design.

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