Omada Cloud Controller Disconects from devices when ER605 Public Address Changes
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada Cloud Controller Disconects from devices when ER605 Public Address Changes
Controller Version
5.13.22.10
When the Public Address of the ER605 changes, the Omada Cloud Controller looses connectivity to the ER605. The only way to recover from this is to Unbind and/or Forget the device and import again, which makes the Cloud Controller useless. Is there a way to avoid this?
This is the physical setup:
/----------\ /----------\ /----------\ ~~~~~~~~~~
~---~ | ISP | | TP-LINK | | ETHERNET | { }
{ ISP }-----| INTERNET |--------| ER605 |--------| SWITCH | -------{ CLIENTS }
~---~ | Modem | \----------/ \----------/ { }
\----------/ | ~~~~~~~~~~~
|
|
/----------\
| ETHERNET |
| SWITCH |
\----------/
