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
@Fae This is frustrating me to no end. I stuck my oc300 with ip 192.168.0.100 on a tp-link sdn 24 port stitch reset to factory, plugged the 7206 in set to factory, went to 0.100, tried to adopt it, it failed, unplugged it waited 10 seconds plugged it back in, failed again. Factory reset on it, went to it's web interface gave it a username and password, tried to adopt, it failed, said bad password, put in the correct password, it still failed, but can no longer log in with the the username/password I set. The access points adopt so easily and run so stably, it seems crazy this is so hard to get to work.
- Copy Link
- Report Inappropriate Content
Dear @GeneMor,
GeneMor wrote
I am installing the TL-ER7206 for the load balance of two internet services: AT&T and Blue Stream. However, there is an ip conflict between the WAN: DHCP client setting IP and the Gateway of one modem. It seems both use the same IP. Any recommendation?
So the DHCP IP address of the ER7206 is the same as the WAN IP address received from one modem, right?
To resolve the IP conflict issue, you may change the IP address of either the DHCP IP setting or the gateway of the modem.
- Copy Link
- Report Inappropriate Content
Dear @sWampyOne,
sWampyOne wrote
This is frustrating me to no end. I stuck my oc300 with ip 192.168.0.100 on a tp-link sdn 24 port stitch reset to factory, plugged the 7206 in set to factory, went to 0.100, tried to adopt it, it failed, unplugged it waited 10 seconds plugged it back in, failed again. Factory reset on it, went to it's web interface gave it a username and password, tried to adopt, it failed, said bad password, put in the correct password, it still failed, but can no longer log in with the the username/password I set. The access points adopt so easily and run so stably, it seems crazy this is so hard to get to work.
Sorry to hear that you have some trouble with the adoption.
From your description, it seems that you are trying to adopt the ER7206 in the default 192.168.0.1/24 subnet. In that case, the adoption should not be difficult. Please follow the steps below and see if it helps:
- Please reset the ER7206 by pressing the reset hole for about 8 seconds until the SYS LED flashes quickly.
- Wait until the ER7206 is restarted, connect the ER7206 -> the 24 port switch -> OC300 & PC, log into OC300 on the PC.
3. On the Devices page, ensure the 24 port switch obtains an IP address (192.168.0.x), and the ER7206 shows IP 192.168.0.1.
4. Try to adopt the ER7206, if it says adoption failed, please reboot the ER7206 by unplugging the power cord and verify if it helps.
- Copy Link
- Report Inappropriate Content
@Fae When I do all that I still end up with a router that isn't adoopted, that I can't log into manually any more. I may try it with just router, oc300, and laptop, and see what happens.
Originally I was trying to get it all going on 10.190.x.x, and no matter what I did the router kept iping itself to 192.168.0.1
- Copy Link
- Report Inappropriate Content
Dear @sWampyOne,
sWampyOne wrote
Originally I was trying to get it all going on 10.190.x.x, and no matter what I did the router kept iping itself to 192.168.0.1
The Controller will issue the default 192.168.0.1/24 LAN setting to the Omada gateway after it's adopted.
The next firmware update on the hardware controller will allow editing the LAN before the gateway is adopted, which may make the adoption easier. At present, we need to go to Settings > Wired Networks > LAN > LAN to edit the LAN after the adoption.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @sWampyOne,
sWampyOne wrote
I must be confused, somewhere, it's all on 192.168.0.xxx and still fails, if I try to edit network to the same thing in the controller after adoption it won't save because nothing changed, and I can't log back into the router/gateway, because it seems the username and password does get changed, but not to ANY on the controller/cloud.
Would a reboot of the gateway by unplugging the power cord resolve the adoption failure issue?
May I know the current firmware version of your controller and gateway?
- Copy Link
- Report Inappropriate Content
Unplugging didn't help.
There is something strange going on, I told firefox to save the password for the gateway, and everytime I log in, using the saved password it says it's wrong, I type it in manually or paste it in manually, it lets me in, and asks me if I want to update the password, if I say yes it stores some 256 char string of random looking stuff. I'm beginning to wonder if there is some strangeness that is causing the controller to set the wrong password in the gateway when adopting, so it can't fully adopt.
Controller Version:
4.3.5
Model:
OC300 1.0
Firmware Version:
1.1.0 Build 20210406 Rel.58776
Gateway 1.0.1 Build 20210113 Rel.35468
- Copy Link
- Report Inappropriate Content
Dear @sWampyOne,
sWampyOne wrote
Unplugging didn't help.
There is something strange going on, I told firefox to save the password for the gateway, and everytime I log in, using the saved password it says it's wrong, I type it in manually or paste it in manually, it lets me in, and asks me if I want to update the password, if I say yes it stores some 256 char string of random looking stuff. I'm beginning to wonder if there is some strangeness that is causing the controller to set the wrong password in the gateway when adopting, so it can't fully adopt.
It's suggested to open the firefox in private mode.
Generally speaking, adopting the gateway in the same 192.168.0.x/24 IP subnet won't get into any trouble.
Have you tried to simplify the network topology and configuration to verify if the OC300 can successfully adopt the gateway?
I'd recommend you factory reset all Omada devices, simply connect the gateway to the switch then to the OC300 & one PC, so nothing else connected, gateway as the only DHCP server, verify if you can adopt the devices with the controller.
BTW, the username and password under Settings -> Site -> Device Account will be issued to the devices after they are adopted by the controller. The password is randomly generated by the controller and you can customize it from there.
- Copy Link
- Report Inappropriate Content
There is a new Omada controller version out, 4.4.3. This is mentioned in the release notes;
"Allow to modify the LAN IP before adopting the Omada Gateway, simplifying configuration process."
Will give it a try over the weekend.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 23427
Replies: 51
Voters 2
