Pi-hole dhcp tries to assign ip to Arlo base station but repeats constantl

Help
1

Expected Behaviour:

Pi-Hole/dnsmasq should assign ip to Netgear Arlo Base Station

Actual Behaviour:

I recently switched to using Pi-hole's DHCP server so I could get better stats from my clients. Everything is working well with one exception - my Netgear Arlo base station (VMS4330) won't take the address and stays offline.

In the logs, I see this:
Jun 2 01:46:47 dnsmasq-dhcp[5227]: DHCPDISCOVER(eth0) a0:04:60:30:13:23
Jun 2 01:46:47 dnsmasq-dhcp[5227]: DHCPOFFER(eth0) 192.168.86.29 a0:04:60:30:13:23
Jun 2 01:46:47 dnsmasq-dhcp[5227]: DHCPREQUEST(eth0) 192.168.86.29 a0:04:60:30:13:23
Jun 2 01:46:47 dnsmasq-dhcp[5227]: DHCPACK(eth0) 192.168.86.29 a0:04:60:30:13:23 Arlo-Base

Over and over, about every 10 seconds or so. The base station won't go online. I even tried factory resetting it to the same effect. It doesn't seem to take the ip. It did work fine with my previous DHCP server, this is something new with the Pi-hole.

Any ideas where to start? I've generated a debug log, token is below. Thanks!

Debug Token:

fg2l2wpwdo

2

are there any DHCP settings you can set n the base station itself? is there another device already at that IP on your network. it appears this device has an internal method of static IP

3

The Arlo is dhcp only. There isn't even a way to set an ip at all with it. You plug it in (the base station doesn't do wifi) and it grabs an address.

The address isn't used by anything else. I even tried giving it a static assignment using it's MAC, and while the Pi-hole will then assign said new address the same problem persists.

If I switch back to my router's DHCP it comes right back.

4

based on what i can find it is an issue with the IP not being assigned correctly but im not sure how our DHCP differs from your router

5

And you have turned off your other DHCP servers, such as the one on your router?

6

I'm thinking the problem must be related. I use Google WiFi, which doesn't allow you to A) Set a different DNS server to assign to clients (you can have it use the Pi-hole, but it will proxy that to the clients - it works, but makes everything appear to be coming from the Google WiFi base station) or B) Allow you to disable DHCP completely unless you also disable the mesh routing...which is the entire point of it.

So I did a trick I read on the Reddit forum - I limited Google WiFi's dhcp scope to just serve an ip to the Pi-hole, then enabled the Pi-hole dhcp. Which actually worked, for 39+ clients (IoT thermostats, game consoles, phones, all the other crap in my house) but the Arlo just wouldn't take the address.

Thinking it may be related but can't seem to dig in to why.

7

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