mekki
Occasional Visitor
Current options for WAN DHCP query frequency are:
Suggested solution (and feature request): Additional option for DHCP query frequency of "backoff mode". Ideally, the backoff timings would be user configurable, along with number of attempts, but if a simple 4th option in the pull list is preferred, something like, "When router does not get a response from ISP, send another query after 120 seconds, and then make 3 (ideally with an option for unlimited) more attempts. Each query after the first query will be delayed by double the previous query time delay, i.e., 120 seconds, 240 seconds, 480 seconds, etc."
Reasoning for feature request: This problem is common to many ISPs and the solution is not ISP specific so won't lead to issues with having to maintain ISP specific code. Solves problems where disconnects, both intermittent short term, and medium term eventually lead to a situation where either the ISP's DHCP blocks the router from getting a WAN IP address indefinitely (leading to a need to disconnect the ISP modem for a lengthy period to reset); or, the situation where the router DHCP requests give up after 2-3 attempts and then stop trying to reconnect to WAN until user manual intervention (e.g. reboot) is done, which can be a frequent problem in the case of sufficiently common ~6-10 minute outages without it being clear that the router gave up trying to connect to the WAN DHCP and won't try again (nothing in the log files about this, so many users assumed it would keep trying indefinitely, myself included); or, solves both.
- Normal: When router does not get a response from ISP, send another query after 120 seconds and make 2 more attempts.
- Aggressive: When router does not get a response from ISP, send another query after 20 seconds and make 3 more attempts.
- Continuous: Not defined in tooltip. Presumably initiates new DHCP request as soon as previous request times out.
Suggested solution (and feature request): Additional option for DHCP query frequency of "backoff mode". Ideally, the backoff timings would be user configurable, along with number of attempts, but if a simple 4th option in the pull list is preferred, something like, "When router does not get a response from ISP, send another query after 120 seconds, and then make 3 (ideally with an option for unlimited) more attempts. Each query after the first query will be delayed by double the previous query time delay, i.e., 120 seconds, 240 seconds, 480 seconds, etc."
Reasoning for feature request: This problem is common to many ISPs and the solution is not ISP specific so won't lead to issues with having to maintain ISP specific code. Solves problems where disconnects, both intermittent short term, and medium term eventually lead to a situation where either the ISP's DHCP blocks the router from getting a WAN IP address indefinitely (leading to a need to disconnect the ISP modem for a lengthy period to reset); or, the situation where the router DHCP requests give up after 2-3 attempts and then stop trying to reconnect to WAN until user manual intervention (e.g. reboot) is done, which can be a frequent problem in the case of sufficiently common ~6-10 minute outages without it being clear that the router gave up trying to connect to the WAN DHCP and won't try again (nothing in the log files about this, so many users assumed it would keep trying indefinitely, myself included); or, solves both.
Last edited:
