There has not been a change to the DHCP code or settings since the initial release of this device so the recent firmware wouldn't have caused a change. I will check with support to see why a the gateway as replaced (even if it were a firmware issue the firmware could be downgraded). My guess is that the device itself was resetting every 60 seconds or so which would be indicative of a hardware issue. In this case, it would request a new DHCP every 60 seconds as it does it automatically upon reset/power-up.
We still use DHCP as a default and a static IP is not required (although we do recommend it).
The old gateway (already returned and received by TED) was completely inaccessible. Could not hard reset, couldn’t access FP, nothing whatsoever. I found it defaulted to factory set ip 192.168.7.2 which I could ping but not browse. (I provided the screenshots to support).
Anyway, in the above post I was referring to the brand new gateway which came with the old firmware (think it was R406). Before I loaded the R452/R240 firmware, it was working as expected with the dhcp settings. After I loaded the R452/R240 firmware, I found that I couldn’t access the gateway via browser.
When I checked the router's dhcp clients list, I found that this one keeps requesting a new IP every 60 secs when all the other devices have 24 hrs lease time. Nothing has been changed on the router between using the old and new firmware on the gateway.
I don’t think the device was resetting every 60 secs, because I did check this graph for an hour there were no indications of resetting every minute other the two while configuring.
Once I configured the static IP on the gateway itself, everything is back to normal.
