Cannot connect to wifi "No route to host" on clients (my Mac and other devices)

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

Expected Behaviour:

After turning off DHCP Server on my Arris BGW210-700 and turning on DHCP Server on the pihole and turning off my wifi network off and back on to connect to the new server I expected to be able to still be on the network. I'm running it on a raspberry pi with Ubuntu server.

Actual Behaviour:

after resetting my wifi network on my mac, it works for a bit until the lease from the pihole takes over and then when entering any address other than my router and pihole it says "cannot connect to server" and when I try to ping anything on my terminal like google it says "No route to host." I have tried reinstalling, and using different DNS servers upstream but it seems to produce the same results.

on my Pi I can ping the gateway and ping itself, on my Mac I can do the same.

entering ip route on my Pi
default via 192.168.1.254 dev eth0 src 192.168.1.231 metric 202
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.231 metric 202
192.168.1.254 dev eth0 proto dhcp scope link src 192.168.1.231 metric 100

Debug Token:

https://tricorder.pi-hole.net/nz0zlqd2b6

Welcome to the Pi-hole community, bennergarrett.

Your ip route output would imply that 192.168.1.254 is your gateway's address.
However, it seems you are distributing 192.168.1.1 to your clients as router/gateway.

Verify that your router is residing at 192.168.1.254.
Then enter that address in Pi-hole's Settings | DHCP. Save and force your clients to dis- and reconnect in order to renew their DHCP leases.

ah thank you! I believe it is fixed now, I saw other users using the 'ip route' but to be honest I didn't quite follow what it was actually showing. It seems obvious now because the pi had full connection to the wifi but none of my devices would connect. I just figured it would automatically put the Gateway in there since it showed me during initialization. Thanks again! that seems to have solved it

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