Unable to reconnect to the wifi network after disconnection about pi-hole-for-android HOT 30 CLOSED

If you recently flashed a new ROM, you may have better luck rolling back a version or two.

Try switching WiFi between 2.4 and 5 Ghz if you have that option.

Just guessing at this point and throwing out random ideas... seems like the Android running Pi-hole has bad WiFi.

I'll flash some other ROM tomorrow, and report back. Thank you a ton for your help till now.

from pi-hole-for-android.

Open the app, tap STOP -- It will take a moment to shut down the instance. Then tap START to restart the instance.

from pi-hole-for-android.

One other thing -- Make sure your install is updated as Pi-hole 5.19 (released about 3 weeks ago) had a bug that crashed FTL.

from pi-hole-for-android.

One other thing -- Make sure your install is updated as Pi-hole 5.19 (released about 3 weeks ago) had a bug that crashed FTL.

My Pi-Hole is up-to-date.

Open the app, tap STOP -- It will take a moment to shut down the instance. Then tap START to restart the instance.

Is there really no fix for this? Do I need to restart the instance every time I (re)connect a device to the wifi?

from pi-hole-for-android.

Can you confirm you have this entry in Local DNS?
connectivitycheck.gstatic.com | 142.250.80.3

from pi-hole-for-android.

Can you confirm you have this entry in Local DNS? connectivitycheck.gstatic.com | 142.250.80.3

Yes

from pi-hole-for-android.

Are you connecting to the same WiFi access point every time, or switching between different ones?

from pi-hole-for-android.

Are you connecting to the same WiFi access point every time, or switching between different ones?

I only have one wifi AP in my house. So all the devices connect to that.

from pi-hole-for-android.

Are you using Pi-hole on your Android device at home all the time, and is the device disconnecting from WiFi on its own?

from pi-hole-for-android.

Are you using Pi-hole on your Android device at home all the time

No, the Pi-Hole is shut down at night.

and is the device disconnecting from WiFi on its own?

The Pi-Hole is neither disconnecting from the WiFi, nor does it have any issues reconnecting to the WiFi.

The issues described in this issue are faced from other devices (my laptop, my mother's phone etc) when reconnecting to the WiFi, after they've been disconnected (disconnected normally when taken out of the house).

from pi-hole-for-android.

Ok got it, thanks for the extra info.

When a device rejoins your network and is unable to resolve DNS, can you run ipconfig /all (or equivalent) to verify it's using the correct DNS server? (that should be the IP of the Pi-hole)

If some devices continue to resolve DNS using Pi-hole, while others do not after (re)joining your WiFi, there has to be a configuration issue somewhere. Are you using Pi-hole's DHCP server or your router's?

from pi-hole-for-android.

When a device rejoins your network and is unable to resolve DNS, can you run ipconfig /all (or equivalent) to verify it's using the correct DNS server? (that should be the IP of the Pi-hole)

The DNS server address is of my pi-hole (I checked on my mother's android phone).

If some devices continue to resolve DNS using Pi-hole, while others do not after (re)joining your WiFi, there has to be a configuration issue somewhere.

I noticed that if I keep refreshing the page after it says "DNS address could not be found", after sometime (20 secs), the device is able to connect to the internet normally, but the wifi indicator icon in the status bar still says "Connected but no internet".

This is the case with my laptop too, though the wifi indicator's functioning properly there.

Are you using Pi-hole's DHCP server or your router's?

Router's

from pi-hole-for-android.

I noticed that if I keep refreshing the page after it says "DNS address could not be found", after sometime (20 secs), the device is able to connect to the internet normally, but the wifi indicator icon in the status bar still says "Connected but no internet".

This behavior isn't possible to reproduce using my father's phone, as his phone keeps reconnecting to the network if it detects there's no internet connection (which resets the connection).

from pi-hole-for-android.

Can you try assigning one of the problematic devices a static IP and set DNS1 and DNS2 servers to point at Pi-hole's IP?

from pi-hole-for-android.

I tried setting the wifi settings to that on my laptop. I still faced connectivity issues for about 30 secs, then websites began to connect successfully.

Also experienced packet loss when pinging google.

~ took 20s
❯ ping google.com
PING google.com (142.250.183.206) 56(84) bytes of data.
64 bytes from bom07s33-in-f14.1e100.net (142.250.183.206): icmp_seq=2 ttl=119 time=287 ms
64 bytes from bom07s33-in-f14.1e100.net (142.250.183.206): icmp_seq=3 ttl=119 time=238 ms
64 bytes from bom07s33-in-f14.1e100.net (142.250.183.206): icmp_seq=4 ttl=119 time=141 ms
64 bytes from bom07s33-in-f14.1e100.net (142.250.183.206): icmp_seq=6 ttl=119 time=71.0 ms
^C
--- google.com ping statistics ---
6 packets transmitted, 4 received, 33.3333% packet loss, time 5041ms
rtt min/avg/max/mdev = 70.989/184.171/286.872/83.852 ms

from pi-hole-for-android.

The ping shown above, what device is this from?
Take DNS out of the picture all together, try pinging 1.1.1.1 or 8.8.8.8 and see if you still have packet loss.

It could be an IP conflict. Assign the Android device running Pi-hole a IP static address outside your DHCP range, making sure the new IP is not already in use by another device.

from pi-hole-for-android.

The ping shown above, what device is this from?

My laptop.

Before assigning static IP to my laptop

~
❯ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=49 time=73.3 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=49 time=73.6 ms
^C
--- 1.1.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1005ms
rtt min/avg/max/mdev = 73.264/73.424/73.585/0.160 ms
~
❯ ping google.com
PING google.com (142.250.183.174) 56(84) bytes of data.
64 bytes from bom07s32-in-f14.1e100.net (142.250.183.174): icmp_seq=1 ttl=119 time=60.5 ms
64 bytes from bom07s32-in-f14.1e100.net (142.250.183.174): icmp_seq=2 ttl=119 time=60.3 ms
64 bytes from bom07s32-in-f14.1e100.net (142.250.183.174): icmp_seq=3 ttl=119 time=59.6 ms
64 bytes from bom07s32-in-f14.1e100.net (142.250.183.174): icmp_seq=4 ttl=119 time=60.6 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 59.608/60.260/60.644/0.394 ms

After assigning static IP, and reconnecting

~
❯ ping google.com
ping: google.com: Temporary failure in name resolution
~ took 17s
❯ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=49 time=103 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=49 time=99.0 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=49 time=273 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=49 time=345 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=49 time=293 ms
^C
--- 1.1.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 99.026/222.748/345.413/102.056 ms

No packet loss occurred now. Weird. But the DNS issue is still present.

from pi-hole-for-android.

Android device running Pi-hole a IP static address outside your DHCP range

After assigning static IP, and reconnecting

It's not clear from your message if you changed the IP of the Android device running Pi-hole as I advised.

EDIT - Additionally, from your laptop, what is the output from nslookup google.com

from pi-hole-for-android.

It's not clear from your message if you changed the IP of the Android device running Pi-hole as I advised.

Yeah, I've changed it to static IP, here's the configuration

~
❯ nslookup google.com
Server:		127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	google.com
Address: 142.250.67.142
Name:	google.com
Address: 2404:6800:4009:827::200e

~
❯ nslookup gitlab.com
;; connection timed out; no servers could be reached


~ took 15s
❯ nslookup github.com
;; connection timed out; no servers could be reached

from pi-hole-for-android.

What is your DHCP range? You are still using 192.168.101.4 try changing it to something farther away like 192.168.101.168
What is your setting for DNS 2? Leaving it blank defaults to 8.8.4.4. Needs to be explicitly set the same as DNS 1. (EDIT - The bit about DNS2 only applies to Android devices)

from pi-hole-for-android.

Your Linux box has systemd-resolved and returns the DNS server as 127.0.0.x so that gets in the way of our troubleshooting.
Please try this instead:
nslookup github.com 192.168.101.168 (Or whatever IP you settle with)

from pi-hole-for-android.

I changed the router's DHCP range to 192.168.101.2 to 192.168.101.253, I then assigned the IP i92.168.101.254 to my pihole, and changed both the DNS to that IP.

Here's the nslookup result from my laptop:

~
❯ nslookup duckduckgo.com 192.168.101.254
;; connection timed out; no servers could be reached

After 30 secs, the wifi magically works as I've described before, and here's the nslookup output after that

~ took 15s
❯ nslookup duckduckgo.com 192.168.101.254
Server:		192.168.101.254
Address:	192.168.101.254#53

Non-authoritative answer:
Name:	duckduckgo.com
Address: 40.81.94.43

from pi-hole-for-android.

~ took 15s

Are you still having this issue or is it operating as it should?

Can you send a few pings to your Pi-hole from your Laptop and some other device?
If ping times are still 200-300ms you have a problem somewhere with WiFi.

from pi-hole-for-android.

Are you still having this issue or is it operating as it should?

Yes, I'm still having DNS issues. I'm unable to resolve any DNS for about 30 secs after re-connnection. After which, it works (don't ask me how).

Can you send a few pings to your Pi-hole from your Laptop and some other device?
If ping times are still 200-300ms you have a problem somewhere with WiFi.

~
❯ ping 192.168.101.254
PING 192.168.101.254 (192.168.101.254) 56(84) bytes of data.
64 bytes from 192.168.101.254: icmp_seq=1 ttl=64 time=86.9 ms
64 bytes from 192.168.101.254: icmp_seq=2 ttl=64 time=25.3 ms
64 bytes from 192.168.101.254: icmp_seq=4 ttl=64 time=124 ms
64 bytes from 192.168.101.254: icmp_seq=5 ttl=64 time=144 ms
64 bytes from 192.168.101.254: icmp_seq=6 ttl=64 time=161 ms
64 bytes from 192.168.101.254: icmp_seq=7 ttl=64 time=78.0 ms
64 bytes from 192.168.101.254: icmp_seq=9 ttl=64 time=117 ms
^C
--- 192.168.101.254 ping statistics ---
9 packets transmitted, 7 received, 22.2222% packet loss, time 8043ms
rtt min/avg/max/mdev = 25.332/105.180/161.212/42.390 ms

Packet loss is back.

from pi-hole-for-android.

Something is wrong... 20% packet loss on home WiFi is Not Ok.
Is the Android device's screen on and showing the Pi Deploy UI? Just want to see if it's power-management related.

from pi-hole-for-android.

Is the Android device's screen on and showing the Pi Deploy UI? Just want to see if it's power-management related.

Yes

from pi-hole-for-android.

You'll need to have the packet loss issue sorted before I can suggest anything else.
Probably want to verify the issue persists with another device (besides your laptop)

from pi-hole-for-android.

~ $ ping 192.168.101.254
PING 192.168.101.254 (192.168.101.254) 56(84) bytes of data.
64 bytes from 192.168.101.254: icmp_seq=2 ttl=64 time=217 ms
64 bytes from 192.168.101.254: icmp_seq=3 ttl=64 time=135 ms
64 bytes from 192.168.101.254: icmp_seq=4 ttl=64 time=342 ms
64 bytes from 192.168.101.254: icmp_seq=5 ttl=64 time=182 ms
64 bytes from 192.168.101.254: icmp_seq=6 ttl=64 time=306 ms
64 bytes from 192.168.101.254: icmp_seq=7 ttl=64 time=227 ms
64 bytes from 192.168.101.254: icmp_seq=8 ttl=64 time=352 ms
64 bytes from 192.168.101.254: icmp_seq=9 ttl=64 time=456 ms
64 bytes from 192.168.101.254: icmp_seq=11 ttl=64 time=511 ms
64 bytes from 192.168.101.254: icmp_seq=12 ttl=64 time=228 ms
64 bytes from 192.168.101.254: icmp_seq=13 ttl=64 time=353 ms
64 bytes from 192.168.101.254: icmp_seq=14 ttl=64 time=273 ms
64 bytes from 192.168.101.254: icmp_seq=15 ttl=64 time=294 ms
64 bytes from 192.168.101.254: icmp_seq=16 ttl=64 time=111 ms
^C
--- 192.168.101.254 ping statistics ---
17 packets transmitted, 14 received, 17% packet loss, time 16043ms
rtt min/avg/max/mdev = 111.852/285.340/511.787/109.502 ms

Here's the ping from my mother's phone (termux)

from pi-hole-for-android.

If you recently flashed a new ROM, you may have better luck rolling back a version or two.

Try switching WiFi between 2.4 and 5 Ghz if you have that option.

Just guessing at this point and throwing out random ideas... seems like the Android running Pi-hole has bad WiFi.

Edit: One-third of a second ping response on that device and 18% packet loss is also, Not OK.

from pi-hole-for-android.

Well, the phone's battery gave up. I'll buy a RPi in the future and use it as a pi-hole. Thank you nevertheless for this project!

from pi-hole-for-android.