Google Wifi w/pihole DHCP problems (narrowed down to pihole-FTL pegged at 99%)

It kind of worked, the problem was it was a race between google wifi's dnsmasq and pihole's dnsmasq(FTL) responding to the dhcp requests from clients. If the google wifi's dnsmasq sent a NACK before FTL sent an ACK the clients would get stuck in an infinite loop of DHCPREQUEST/DHCPOFFER. It was a toss up if clients would get IPs. I'd have to keep rebooting things and hoping they got an IP. After another technical discussion with the GoogleWifi team pleading with them to either let me disable their dnsmasq or add a delay to their config I had enough and ripped GoogleWifi out of my network. It was the straw that broke my back.

I've since built out a ubiquiti network and couldn't be happier.

With all the technical limitations with GoogleWifi I can honestly only recommend disabling pihole's DHCP server and configuring GoogleWifi DNS to your pihole and letting it proxy all DNS requests (making all your network clients show up as a single network client in pihole logs).

2 Likes