0
VotesFeature Request: Trigger DHCP Release/Renew on WAN Online Detection Failure (Gateway Unreachable)
Feature Request: Trigger DHCP Release/Renew on WAN Online Detection Failure (Gateway Unreachable)
Tags:
#WAN
Model: All Omada Routers (ER605, ER7206, ER707-M2, etc.)
Description of the Problem
When an Omada router is configured as a cascaded (downstream) router behind an upstream ISP gateway or main router using a Dynamic IP (DHCP) WAN connection, it fails to adapt if the upstream network subnet or gateway IP changes without a physical link drop.
Currently, if the upstream router changes its network configuration:
- The physical Ethernet link status on the Omada WAN port remains "Connected" (UP).
- The Omada Online Detection tool correctly identifies that the internet is down and marks the WAN status as "Offline."
- The Issue: The Omada DHCP client daemon does not respond to this Online Detection failure. Because the lease timer hasn't expired and the physical link never dropped, the router stubbornly retains its old, invalid IP address and gateway configuration. It loops traffic to a non-existent upstream gateway indefinitely.
current workarounds
The only current workarounds are to manually click "Disconnect/Connect" in the controller, physically unplug the WAN cable, or set a dangerously low DHCP lease time on the upstream router—none of which are viable for autonomous, enterprise-grade deployments.
Proposed Feature Change / Solution
We need a tighter integration between the
Online Detection service and the
DHCP Client interface.
Please implement one of the following logic loops into a future Omada firmware update:
- Automated DHCP Renewal on Tracking Failure: If Online Detection fails continuously for a user-defined threshold (e.g., 3 consecutive tracking intervals), the router should automatically execute a
DHCP ReleaseandDHCP Renewon that WAN interface to discover any network changes. - Interface Reset: Alternatively, provide a toggle under WAN Advanced Settings: "Reinitialize WAN Interface / Restart DHCP Client if Online Detection Fails."
Final Comments
This behavior is standard on competing routing platforms (often called "Interface Policy Routing" or "Link Tracking Scripts") and is critical for multi-tiered networks where upstream changes occur dynamically.
PS: I wanted to add tags WAN and DHCP but was not able do so, I could only create one custom tag, so I chose WAN