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

    Android Limited Connectivity

    Scheduled Pinned Locked Moved DHCP and DNS
    14 Posts 6 Posters 1.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.
    • AndyRHA
      AndyRH
      last edited by AndyRH

      There are instructions in the pfSense docs to NAT DNS so the device does not know it it not talking to the DNS server of it's choice. I have done it with PiHole, the method to do it for pfSense DNS is a little different.

      Or don't worry about it since it is working fine.

      o||||o
      7100-1u

      4 1 Reply Last reply Reply Quote 0
      • 4
        4o4rh @AndyRH
        last edited by

        @AndyRH I have

        Rules

        • rule to allow DNS to pfsense interface
        • rule to block all other DNS not to pfsense interface

        Port Forwards

        • DNS not to pfsense interface, redirect to pfsense interface

        but what i don't understand is, i have 3 WIFI IDs 2 give the error and 1 does not. The have exactly the same DNS settings

        GertjanG 1 Reply Last reply Reply Quote 0
        • Y
          yattengate @4o4rh
          last edited by

          @gwaitsi, from what I know they use a host to check if "Internet" is available.
          There's no good way to differentiate network vs Internet, so all mobiles do this.
          Androids HTTP/S to connectivitycheck.gstatic.com or clients3.google.com or www.google.com
          iPhones HTTP/S to captive.apple.com
          Missing response they assume there's no Internet reachable from current connectivity.

          1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @4o4rh
            last edited by

            @gwaitsi said in Android Limited Connectivity:

            I have my DNS setup to forward all requests to pfsense.
            And use the DNS Resolving to forward to cloudsense all requests not handled by resolver.

            Are you using DHCPv6 on your LAN? Android devices won't work with it, thanks to some genius at Google. You normally use SLAAC and select Provide DNS configuration via radvd.

            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...

            4 1 Reply Last reply Reply Quote 0
            • 4
              4o4rh @JKnott
              last edited by

              @JKnott no, just IP4. but it is weird and seems to be something to do with the client/s.

              some phones connect to WIFI1, WIFI2, WIFI3 without issue
              my phone connects to WIFI3 without issue, but WIFI1 and WIFI2 with limited connectivity

              I tried to forget the connect and re-establish, but i get the some results.

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

                @gwaitsi said in Android Limited Connectivity:

                rule to allow DNS to pfsense interface

                Android phone ? DNS, problems ? .... I hope this one is done now.

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

                4 1 Reply Last reply Reply Quote 0
                • 4
                  4o4rh @Gertjan
                  last edited by

                  @Gertjan all android phones.
                  WIFI1, WIFI2 and WIFI3 are all on the same devices and forward dns queries to the pfsense interface for the vlan.

                  But different devices, get different results

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

                    @gwaitsi said in Android Limited Connectivity:

                    forward dns queries to the pfsense interface

                    And just to be sure : using '53' TCP and or 53 UDP, like the good old days. Not 'only 853 or nothing'.
                    I owned/used never saw an Android device ... so dono how these devices behave.

                    @gwaitsi said in Android Limited Connectivity:

                    But different devices, get different results

                    Like : a pc works, but a byod doesn't ?

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

                    4 1 Reply Last reply Reply Quote 0
                    • 4
                      4o4rh @Gertjan
                      last edited by

                      @Gertjan i mean different android devices get different results.
                      no windows or linux machines are effected

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

                        @gwaitsi

                        AS shown in the other thread I've mentioned above : packet capture on the interface used, and add the IP of the device.
                        Start the capturing.
                        Now, connect the device.

                        Tell us what you saw ....

                        @gwaitsi said in Android Limited Connectivity:

                        no windows or linux machines are effected

                        Neither apple devices, they work fine also, right ?

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

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