Knowledge Base How to add an Omada Gateway to the network with Controller v4.4.3 or above
This Article Applies to:
ER7206 (TL-ER7206) or ER605 (TL-ER605) + Omada Controller V4.4.3 or above
Background:
This article previously introduces the recommended steps to add the gateway with Omada Controller v4.3.5 or below version, as you may see discussions and comments under this article, it's hard to add the Omada Gateway in a non-192.168.0.x network since the Omada Controller v4.3.5 or below doesn't allow editing of the LAN interface before adopting the gateway.
Solution:
To simplify the configuration process, Omada Controller v4.4.3 starts to allow modifying the LAN IP before adopting the Omada Gateway. About how to add the Omada Gateway in a non-192.168.0.x network with the Omada Controller v4.4.3 or above, please refer to the FAQ below.
How to add an Omada Gateway to the network with Controller 4.4.3 or above?
Kind Note:
The Omada Hardware Controller bundled with controller v4.4.3 will not be updated but directly to v4.4.4.
Once there is a new release on the Omada Controller, I'll update this post. Thank you for your attention!
Related Articles:
How to add an Omada Gateway to the network with Controller 4.3.5 or below?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Fae Well, these instructions to adopt a GW works for a while...
My GW have almost 27 days of uptime, today I noticed that Omada (SW-controller) is back to a loop trying to Adopt and Provision the GW..
- Copy Link
- Report Inappropriate Content
@Fae I spent quite some hours trying to figure out why I couldn't get adoption to work. I eventually figured out that my device account had a space in it. Removing the space fixed the problem. It seems that my OC200 is more permissive about user names than my TL-R605, which means is continuously fails without giving a useful error. If I recall correctly the OC200 originally prompted me for my name and it wasn't clear it meant username.
- Copy Link
- Report Inappropriate Content
@takahe The username for my account was "one word" without spaces. Adoption of the TL-R605 was from the start a problem simply because it has a fixed IP address of 192.168.0.1 and it could not talk to my subnet 172.16.x.x
Problem is still there: LAN cannot be edited as described in the previous posts despite the last firmware update to 4.2.11 (1.7.4 Build 20210118 Rel. 72627).
- Copy Link
- Report Inappropriate Content
@BFH Worked for me, thank you!
I was fighting this for a few days!
- Copy Link
- Report Inappropriate Content
Was super happy with my Omada network untill my ISP dropped and when it came back up my R605 Gateway is no longer connected. So I
have been unable to get it to adopt using any of the above methoud. I guess I will be force to reset to factory . This is a really stupid oversight from the firmware develpers.
DO we have a estimate on when the fix might be out from anyone at TP-Link?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 23383
Replies: 51
Voters 2
