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

    Cannot access WAN IP from LAN

    Scheduled Pinned Locked Moved General pfSense Questions
    13 Posts 3 Posters 1.2k Views 3 Watching
    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.
    • JKnottJ Offline
      JKnott @tittu
      last edited by

      @tittu

      With those addresses so close, my first question would be what subnet masks are you using?

      PfSense running on Qotom mini PC
      i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
      UniFi AC-Lite access point

      I haven't lost my mind. It's around here...somewhere...

      T 1 Reply Last reply Reply Quote 0
      • T Offline
        tittu @JKnott
        last edited by

        @jknott thanks for your reply. the subnet mask for both the 192.168.0.x and 192.168.1.x are 255.255.255.0 /24 bit.

        Please tell me I'm doing something silly?

        JKnottJ 1 Reply Last reply Reply Quote 0
        • JKnottJ Offline
          JKnott @tittu
          last edited by JKnott

          @tittu

          Your WAN is in the RFC1918 range. There are some rules that block those on the WAN side. For example, the first 2 rules in my firewall block private addresses and "bogon" networks. You could try turning off the private networks one.

          PfSense running on Qotom mini PC
          i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
          UniFi AC-Lite access point

          I haven't lost my mind. It's around here...somewhere...

          GertjanG 1 Reply Last reply Reply Quote 1
          • GertjanG Online
            Gertjan @JKnott
            last edited by

            You mean these :

            b9ca2025-583a-4c64-bfd9-ca4e03ac3bb9-image.png

            This is my WAN :

            584aebe1-a7ea-47b8-b9ec-3615db1a9ea7-image.png

            pfSense has 192.168.10.3 and my ISP router's LAN IP is 192.168.10.1

            Still, when I type 192.168.10.1 in a browser situated on LAN, I can access my ISP router's GUI just fine.

            I didn't set any firewall or NAT rules for this to work.

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            JKnottJ 1 Reply Last reply Reply Quote 1
            • JKnottJ Offline
              JKnott @Gertjan
              last edited by

              @gertjan

              Notice that first rule, that blocks RFC 1918? You shouldn't have that if your WAN is 192.168.anything. The purpose of that rule is to keep anything within the RFC 1918 addresses from entering. Try disabling it and see what happens.

              PfSense running on Qotom mini PC
              i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
              UniFi AC-Lite access point

              I haven't lost my mind. It's around here...somewhere...

              GertjanG 1 Reply Last reply Reply Quote 1
              • GertjanG Online
                Gertjan @JKnott
                last edited by Gertjan

                @jknott : I do agree with you - that rule - this rule :

                375b9ebd-42a3-46c1-b1ca-1eb7f73e2aac-image.png

                should not be checked in my case.
                As my upstream router has 192.168.10.1/24 == very RFC198.

                I unchecked it, as per your words, and the description.

                Still, nothing happens. No smoke, no sound.
                I can still access my upstream ISP router (192.168.10.1) just fine :

                be5d4d7d-e479-40e6-b9a3-d860f20d67b2-image.png

                This "Block private networks and loopback addresses" checkbox was like a no-op for me.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                JKnottJ 2 Replies Last reply Reply Quote 1
                • JKnottJ Offline
                  JKnott @Gertjan
                  last edited by

                  @gertjan

                  Next step is to try some packet capture to see what's actually happening.

                  PfSense running on Qotom mini PC
                  i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                  UniFi AC-Lite access point

                  I haven't lost my mind. It's around here...somewhere...

                  1 Reply Last reply Reply Quote 1
                  • JKnottJ Offline
                    JKnott @Gertjan
                    last edited by

                    @gertjan

                    BTW, is your modem in bridge or gateway mode? You should have it in bridge mode for pfsense.

                    PfSense running on Qotom mini PC
                    i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                    UniFi AC-Lite access point

                    I haven't lost my mind. It's around here...somewhere...

                    GertjanG 1 Reply Last reply Reply Quote 1
                    • GertjanG Online
                      Gertjan @JKnott
                      last edited by

                      @jknott
                      "bridge" is something of the past for me. I've been using it in the past.
                      These soHO 'livebox"boxes is also an access point, has two telephone lines, can accommodate the national TV channels and has even now a 4G+sim card backup card.
                      The VDSL lines - and the underlying protocol - that Orange used in France do not permit 'bridge (PPPOE) mode.
                      I"ve a typical router-after-router setup.

                      The Wifi, TV and phone functionality has been shut down.
                      As a hotel we already have way more TV channels and TV sets (39) - 4 phone lines and a fax line (have to keep it for one more year, and then the fax will get shut down - telex died in 2010). The Wifi is based on my own AP's - 6 around the building.

                      Not really a problem for me. I just have to implement double NAT, so my OpenVPN is reachable.
                      ( and a rsync access - port 22 - to my LAN based Syno for backup reasons )

                      No "help me" PM's please. Use the forum, the community will thank you.
                      Edit : and where are the logs ??

                      JKnottJ 1 Reply Last reply Reply Quote 1
                      • JKnottJ Offline
                        JKnott @Gertjan
                        last edited by

                        @gertjan said in Cannot access WAN IP from LAN:

                        Not really a problem for me. I just have to implement double NAT, so my OpenVPN is reachable.

                        Why would anyone want to do that? My modem also supports phone & TV but having it in bridge mode doesn't cause any problems. The only thing I lose is the built in WiFi. However, I have a separate AP that provides much better coverage. Also, gateway mode prevents pfsense from handling IPv6.

                        PfSense running on Qotom mini PC
                        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                        UniFi AC-Lite access point

                        I haven't lost my mind. It's around here...somewhere...

                        1 Reply Last reply Reply Quote 1
                        • T Offline
                          tittu
                          last edited by

                          Thank you everyone. I removed the block traffic on ip addresses that are reserved for private networks per RFC and unique local addresses on the LAN and my VPN interface and it’s working! Yay, I’m so happy. Thanks to you all, this problem is resolved.

                          Best wishes and thanks again!

                          JKnottJ 1 Reply Last reply Reply Quote 0
                          • JKnottJ Offline
                            JKnott @tittu
                            last edited by

                            @tittu

                            What you may want to do is create a rule to allow only the desired address(s) through followed by the block RFC1918 rule.

                            PfSense running on Qotom mini PC
                            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                            UniFi AC-Lite access point

                            I haven't lost my mind. It's around here...somewhere...

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