@jsawhite 

jsawhite wrote

  @Cepheus0815 I find that whenever I change IP addressing in DHCP reservations, frequently those changes don't take affect until I reboot the gateway (in my case an er8411, but I'd image the same across the lineup).  after the router reboot, the new IP address change takes affect as soon as the device renews it's IP address.  not really sure why that is, but it seems to be a glitch in the router's DHCP server.  inconvenient but not intolerable...

It's the same thing for any other router. Either you reconnect the cable or reboot the device. 

If the device does not trigger a new DHCP request, you gotta reboot the device or the router to start a new DHCP interaction. 

The problem is the DHCP protocol. It does not renew until the lease time is halfway or restarted. 

I think I wrote this stuff in the guide about the DHCP. 

  @Clive_A 

not quite...  I had to reboot the router to get the IP address to update, not the device.  that did nothing.  the router was hanging onto that DHCP reservation.  I tried several thing before resorting to the router reboot.  rebooting/power cycling the device.  unplugging (waiting 10 sec) and re-plugging the eth connection.  Switching which port the device was plugged into (on same vlan).  I even tried shutting the device down overnight then turning back on in the morning.  It _would not_ give the updated IP address, just the old one.  and my lease time is set to 120 minutes on my main networks.  I had to reboot the router itself to get it to change.  (thankfully the 8411 reboots fairly quickly!)

now a caveat on that.  this was only if I was updating the IP or MAC address of an existing reservation.  if there was a new device that did not have a reservation, and I created the static reservation (with a different IP than what it picked up) via the device config page, it would work.  But if it already had a static IP address and I wanted to update that, then I had to reboot the router.

This was not an issue when I was using pFsense or the commodity router I had before my Omada setup.

again, inconvenient but not  a show stopper.  I've learned that's the case and just plan accordingly when I decide to move stuff around on my network (for ACL grouping or just OCD in the client list... ;)  It's not a frequent occurrence, so it's tolerable.

  @jsawhite 

jsawhite wrote

  @Clive_A 

 

not quite...  I had to reboot the router to get the IP address to update, not the device.  that did nothing.  the router was hanging onto that DHCP reservation.  I tried several thing before resorting to the router reboot.  rebooting/power cycling the device.  unplugging (waiting 10 sec) and re-plugging the eth connection.  Switching which port the device was plugged into (on same vlan).  I even tried shutting the device down overnight then turning back on in the morning.  It _would not_ give the updated IP address, just the old one.  and my lease time is set to 120 minutes on my main networks.  I had to reboot the router itself to get it to change.  (thankfully the 8411 reboots fairly quickly!)

 

now a caveat on that.  this was only if I was updating the IP or MAC address of an existing reservation.  if there was a new device that did not have a reservation, and I created the static reservation (with a different IP than what it picked up) via the device config page, it would work.  But if it already had a static IP address and I wanted to update that, then I had to reboot the router.

 

This was not an issue when I was using pFsense or the commodity router I had before my Omada setup.

 

again, inconvenient but not  a show stopper.  I've learned that's the case and just plan accordingly when I decide to move stuff around on my network (for ACL grouping or just OCD in the client list... ;)  It's not a frequent occurrence, so it's tolerable.

I have not faced this issue with the PC I have tested. I have not tested wireless or other products like IoT as I am not responsible for any of the wireless products of us or others.

With the Windows system, I disconnect the cable and reconnect it, and it gets the IP properly. 

When you create the DHCP reservation, it creates the IP-MAC binding rules in another tab. I am not sure if you checked that. Or change the IP from there. 

  @Clive_A I've had it happen with both Windows and non-windows devices (IoT and Linux flavors).  doesn't seem to be dependent on the endpoint.

I guess that is true.  I do not use the IP-MAC binding.  I find it unnecessary in my home network (and creates extra steps to change an IP address).  Maybe if I did that binding as well as the static IP assignment it would take without reboot?  may test that in the future...  *shrug*