Solution Omada Gateway’s DHCP NOT Working After Upgrading to Firmware 1.1.1 - [Case Closed]
This Article Applies to:
ER605_v1 or ER7206_v1 managed by Omada SDN Controller v4
The Omada SDN Controller supports configuring Use Fixed IP Address (DHCP reservation) for the connected clients.
With Omada SDN Controller v4.2.11 and below version, there is no limitation on the Fixed IP Address (DHCP reservation) feature, it is possible to input the same fixed IP address for multiple clients, and this kind of improper configuration may cause the Omada Gateway’s DHCP service down.
To avoid such issue from happening, the limitation has been added on Omada SDN Controller v4.3.5 and above version, if you are configuring the same fixed IP address for another client, the following error message will be prompted:
However, the limitation only applies to the new configurations. The previous improper configurations won’t be removed themselves after you upgrade to the new firmware, which may still result in the DHCP service failure.
The gateway 1.0.1 firmware fixed the DHCP issue before, which may help for the case, but the problem may reappear after upgrading to new firmware 1.1.1. Related post can be found HERE.
The Omada Controller v5 will support showing the reserved IP addresses in a table, and the new gateway firmware compatible with Controller v5 will also ignore the duplicated DHCP reservation to avoid the DHCP service failure.
[Case Closed] Update:
Omada Controller v5 has been released to fix the issue, please check this post for an update. Besides, Omada gateway firmware 1.2.0 is fully adapted to the Controller v5, you may check this post for an update.
At present, to fix the DHCP issue thoroughly, please correct the DHCP reservation for the clients, ensure that all clients have a unique fixed IP address:
1) Go to Insights -> Known Clients -> each client’s Config to check the Fixed IP address, 2) Find out the duplicated DHCP reservation and correct it, then restart the gateway.
If this was helpful click the thumbs-up (Kudos) button below.
If this solved your issue, I'd encourage you to comment below, so others can benefit from that.
If the solution doesn't work for you, your case is probably different from what is described here.
In that case, please feel free to click Start a New Thread and elaborate on the problem so that we can try to help you further.
Thank you for your great cooperation and patience!