7 ms·
It doesn't honor DHCP lease expiration I don't know what you're using as a DCHP server, but the servers I've used try hard not to hand out the same IP address
by PhantomGremlin 11y ago
It doesn't honor DHCP lease expiration
I don't know what you're using as a DCHP server, but the servers I've used try hard not to hand out the same IP address to a second device until after handing out all possible IP addresses. Which means my network would need something close to 256 different DHCP clients before having a problem.
I do have some flexibility at home because I run my own dhcpd on OpenBSD, rather than relying on something in a router. Which means extra flexibility. So I lock down the IP addresses anyway. E.g. I have entries like this in my dhcpd.conf file:
host foo {
hardware ethernet 00:1b:63:95:1c:4f;
fixed-address foo.example.com;
default-lease-time 3600;
}
That lets me define IP addresses in a single location (my zone file). I don't need to configure devices individually. The DHCP server recognizes the MAC address and knows what IP address to give to what device.
It's a little bit of hassle to set things up this way, but there are never problems even if devices are stupid about when they renew their leases.
That's not to take anything away from your comments, it's just a workaround that has worked for me. Your entire list seems like annoying problems for the Nest.
- insaneirish 11y agoFunny enough, I do this as well (OpenBSD but with dnsmasq for easier DHCP/DNS integration). At the time I was having the DHCP issue, I had my OpenBSD router behind my ISP's router in order to preserve some cable box functionality. I also kept "untrusted" devices like the Nest using that router. I've since ditched my cable boxes and thus the ISP router and now just have untrusted devices in a separate VLAN walled off from my other networks.