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

    No Internet access to LAN2

    Scheduled Pinned Locked Moved DHCP and DNS
    19 Posts 5 Posters 1.7k 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.
    • GertjanG
      Gertjan @parneetbatra
      last edited by Gertjan

      @parneetbatra

      Let's start with :

      No Internet access to LAN2

      You've proven that wrong with :

      61f448c4-a65f-45b7-867e-8b5323aafead-image.png

      😊

      I saw :

      d626d93f-e02a-4997-a5b8-a68c88ba726b-image.png

      8a3fb559-d4ca-4b16-a8b2-b62d74198ef2-image.png

      When you did a :

      c91df92e-f25e-4ae8-8c13-cc7e773cf4db-image.png

      it showed that ICMP packets reach the LAN1, and the reply gets back. Good sign.
      Make it one step further : a ping from LAN2 to a device present on LAN1: the DNS pi-hole.
      I saw your PC was using this IP as a DNS.
      Another step : can your PC ping some other device on LAN1 ?

      Even more info : Goto Diagnostics > Packet Capture :

      Select for Capture Options your LAN2 interface :

      a6410135-0066-42ea-b37e-2de0a64d5dbb-image.png

      and hit the start button.
      Now, do a ping to google.com (this implies a initial host name lookup == DNS == 192.168.1.5 is/should (!) be used) or use the official Microsoft nslookup tool called nslookup ^^

      nslookup google.com
      

      What did that show ?

      and then look at the packet trace result.

      This might explain the issue : DNS packets coming from LAN2 do arrive at the LAN1 interface, but the pi-hole has a setting that allows it to answer only to requests coming from its own LAN == LAN1 == 192.168.1.0/24 - and it (pi-hole) refuses to answer to requests coming from elsewhere, notability 192.168.100.0/24 == LAN2.
      So pi-hole behaves like a black-hole ^^
      This pi-hole behavior is a security : it should only answer to request from the local "LAN" (LAN1) and from no one else. Up to you to add also "LAN2" (192.168.100.0/24) to the allowed network list.

      Btw : I never used or saw a pi-hole.

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

      P 3 Replies Last reply Reply Quote 0
      • V
        viragomann @parneetbatra
        last edited by

        @parneetbatra
        What do you get if you do an

        nslookup google.com
        

        ?

        I suspect, that your DNS is not responding due to missing ACL the LAN2.

        P 1 Reply Last reply Reply Quote 1
        • P
          parneetbatra @Gertjan
          last edited by parneetbatra

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • P
            parneetbatra @viragomann
            last edited by

            @viragomann

            Diagnosis Result

            50bc2213-5d81-40dc-96c1-2c89634d637c-image.png

            3914c504-59ad-4a82-b029-8f14b250c34b-image.png

            P 1 Reply Last reply Reply Quote 0
            • P
              parneetbatra @parneetbatra
              last edited by

              @viragomann

              dbc63b71-b711-46cf-9f88-96917f5107bd-image.png

              1 Reply Last reply Reply Quote 0
              • P
                parneetbatra @Gertjan
                last edited by

                @Gertjan said in No Internet access to LAN2:

                Another step : can your PC ping some other device on LAN1 ?

                febc9e5b-9765-4a07-be6e-5459284a221c-image.png

                1 Reply Last reply Reply Quote 0
                • P
                  parneetbatra @Gertjan
                  last edited by

                  @Gertjan

                  PiHole Diagnosis

                  ddd27e59-b4ac-404f-b8a1-28dae215510b-image.png

                  298f0a37-37ee-4d00-885e-8ab2aba6d6e6-image.png

                  ac117e46-f751-4293-b4b7-6cb642c31b6f-image.png

                  P 1 Reply Last reply Reply Quote 0
                  • P
                    parneetbatra @parneetbatra
                    last edited by

                    @Gertjan
                    @viragomann

                    Good news, if I change DNS to 8.8.8.8 in LAN2, I can ping to google.com
                    I can access the internet.

                    It's a Pi-hole issue. is there any idea for Pi-hole, why not let us connect to Google in LAN2?

                    bmeeksB GertjanG 2 Replies Last reply Reply Quote 0
                    • bmeeksB
                      bmeeks @parneetbatra
                      last edited by bmeeks

                      @parneetbatra said in No Internet access to LAN2:

                      It's a Pi-hole issue. is there any idea for Pi-hole, why not let us connect to Google in LAN2?

                      You've identified your problem by drawing those two red rectangles around two Pi-hole log entries. Here is one of them:

                      ignoring query from non-local network 192.168.100.10
                      

                      As someone pointed out earlier in this thread, DNS servers such as unbound and Pi-hole have ACLs (access control lists) that limit what IP addresses can query for DNS names. By default those queries are limited to clients residing on the same local network (LAN) as the DNS server.

                      Scroll down this list of dnsmasque warnings in Pi-hole to find your specific error and its causes: https://docs.pi-hole.net/ftldns/dnsmasq_warn/.

                      The TLDR answer is you seem to have incorrect access permissions and thus DNS queries from your LAN2 are being ignored by Pi-hole.

                      1 Reply Last reply Reply Quote 1
                      • V
                        vitko-core.ru @parneetbatra
                        last edited by

                        @parneetbatra said in No Internet access to LAN2:

                        Any help?

                        c37efcc0-7059-4bf7-b2d8-2d5aa804bc30-image.png

                        1 Reply Last reply Reply Quote 0
                        • GertjanG
                          Gertjan @parneetbatra
                          last edited by Gertjan

                          @parneetbatra

                          As said earlier,
                          As said by @bmeeks
                          As said by the guy who made the red box here :

                          4155689b-487b-4282-bb84-a5141afac0db-image.png

                          and as said by your pi-hole :

                          "Ignoring query from non local network 192.168.100.1".

                          The local network is 192.168.1.0/24 - your pfSense LAN network.
                          So : request from 192.168.100.0/24 are ignored.
                          So, set up pi-hole that it should consider both 192.168.1.0/24 and 192.168.100.0/24 as 'local'

                          and from then on, DNS works on your LAN2 interface.

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

                          V 1 Reply Last reply Reply Quote 1
                          • V
                            vitko-core.ru @Gertjan
                            last edited by

                            @Gertjan said in No Internet access to LAN2:

                            So, set up pi-hole that it should consider both 192.168.1.0/24 and 192.168.100.0/24 as 'local'

                            +++need set local CIDR!
                            200df62e-13a8-406b-8177-beaf45964f69-image.png

                            192.168.0.0/16
                            
                            1 Reply Last reply Reply Quote 0
                            • S SteveITS referenced this topic on
                            • First post
                              Last post
                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.