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
Why can't TP-LINK allow editing of the LAN interface before adopting the gateway ???? Then the problem is solved.
- Copy Link
- Report Inappropriate Content
@shberge I concur. Why not change the router's IP to 192.168.68.x before connecting it with Omada controller?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @shberge,
Why can't TP-LINK allow editing of the LAN interface before adopting the gateway ???? Then the problem is solved.
Thank you for the valued suggestion. This is planned to be supported on Omada Controller V5, hoping it comes soon.
- Copy Link
- Report Inappropriate Content
The issue is the Gateway needs an edit on the LAN so it can adopt. You should roll out a quick patch to fix this issue on the Gateways urgently! Not wait for who knows how long for a the V5 version of the firmware on the controller and keep all customers in the dark!
- Copy Link
- Report Inappropriate Content
@Fae This process does not work if you're using a software controller that's on the original network, especially if it's in a docker container with a static IP. I've come up with a different workaround that does fix it despite being overly complicated.
But it's inexcusable that the gateway was released with such a major bug. I would wager that most of the networks of people buying prosumer gear are not on the 192.168.0.1/24 subnet. If the majority are, then it's likely a small majority.
When is V5 of the software controller coming out, and how involved will migration be?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Configure the gateway in stand-alone mode with the correct subnet.
- Back up gateway settings.
- Adopt the gateway...
- While it is configuring, quickly go to Settings > Wired Networks > LAN > LAN and you will now be able to edit the settings.
- Input the correct values.
- Save settings.
- Adoption will fail.
- Factory reset the gateway.
- Restore gateway settings from step 2.
- Adopt the gateway. It will be successful.
HACKING!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@pcsurgeon Once the gateway shows up as "configuring," it should be editable. You might be going too slow or fast.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 15464
Replies: 51
Voters 2
