Lack of internet connection for certain devices

Please follow the below template, it will help us to help you!

Expected Behaviour:

Device connects to network is assigned a IP via pi-hole and connects to the internet

Actual Behaviour:

Device connects, gets a IP and does not have internet access, my TV box, my alexa do not get access to the internet, but my phone and laptop and smart bulbs DO have access, all devies have been rebooted

Debug Token:

[✓] Your debug token is: https://tricorder.pi-hole.net/l3snrq7j2t

Looks like there is an issue with your network. The Pi-hole server is not able to contact the router.

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eno1 interface:
   192.168.0.9/24 matches the IP found in /etc/pihole/setupVars.conf

[✗] No IPv6 address(es) found on the eno1 interface.

[i] Default IPv4 gateway: 192.168.0.1
192.168.0.1
   * Pinging 192.168.0.1
192.168.0.1...
[✗] Gateway did not respond. (https://discourse.pi-hole.net/t/why-is-a-default-gateway-important-for-pi-hole/3546)

hey,

i have had a look and cant find out why

PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.395 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.478 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.456 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=0.544 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=0.441 ms
^C
--- 192.168.0.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4091ms
rtt min/avg/max/mdev = 0.395/0.462/0.544/0.055 ms

My laptop, the wifi bulbs, my mobile, all have internet access.
but my tv box and wifi speaker do not have access, any suggestions ?

Does the admin interface show any queries forwarded or queries blocked from those devices?

Unfortunately no.

Sounds like it may not be related to the Pi-hole DNS. Do the devices show up on the Network section of the admin interface?

They do indeed, PI-hole is used as my dhcp server so gives out the IP's the devices

The TV box also has access to the router via web interface and pi-hole

Is there any way to check on the TV box to see if it's using Pi-hole as the DNS or if it's hard coded to use another? Do you have any firewall rules on the router? Is the TV box seeing the router web interface via an IP address or via a domain name?

To my knowledge, there is no firewall on the router, the tv box must use pi-hole as its set in the router, it also does manage to get the correct IP thats set static inside of pi-hole (192.168.0.6)

Pinging 192.168.0.6 with 32 bytes of data:
Reply from 192.168.0.6: bytes=32 time=198ms TTL=64
Reply from 192.168.0.6: bytes=32 time=380ms TTL=64
Reply from 192.168.0.6: bytes=32 time=586ms TTL=64
Reply from 192.168.0.6: bytes=32 time=1611ms TTL=64
Ping statistics for 192.168.0.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 198ms, Maximum = 1611ms, Average = 693ms

i will try find in the settings what is its default gateway, but everything is done via dhcp

Are you able to get a terminal or a console on the TV box? Or does it have a browser that you can use? If it can browse, what is the result of going to http://1.1.1.1 which will test if the issue is with resolving or if it's another problem to research.

I can see the site, so resolving is the issue, for the two devices ....

So http://cloudflare.com does not work? Is there an error that is displayed?

Nope, the 1.1.1.1 works though, just not domains, what means something is stopping resolution

FYI its a android TV box, so i can get any app's etc needed (when i get the resolution working)

What error is returned?

If you can get some kind of terminal emulator or console that would be helpful as you should then be able to check the network stack and see if ping and dig respond or fail. And also check to see what resolver it's actually using.

so, by the look of it the tv box for some reason is taking 192.168.0.100 as a broadcast address, would somewhat explain it

turns out, for some unknown reason it was trying to connect to a network bridge, even thought it's setup to use eno1. thanks for your help

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.