Business Community > Routers > Adding gateway to Omada - PROBLEM
< Routers

Adding gateway to Omada - PROBLEM

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

Adding gateway to Omada - PROBLEM

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Adding gateway to Omada - PROBLEM
Adding gateway to Omada - PROBLEM
2024-02-04 09:36:42 - last edited 2024-02-04 13:12:03
Model: ER605 (TL-R605) Ā 
Hardware Version: V2
Firmware Version: 2.1.1

Hi guys,

Before adding a gateway, my topology was like:

3rd party ROUTER - OMADA SWITCH - 3  APs & OC200

 

Now I've added a router and configured its subnet  from its www.

3rd party ROUTER (192.168.0.1) - ER605 ROUTER (192.168.1.1) - OMADA SWITCH - 3 APs & OC200

 

At first it was working but I could not Adopt it. Omada controller couldnt be reached too. After a while Omada controller started to be available and I could Adopt new ER605 as a gateway.

During the "configuring" step of adoption, I lost Access to everything. 

My all client devices "returned" to my ISP router subnet (192.168.0.x) with x=1 as a gateway. However the internet stopped to work. Er605 behave like if it was working in bypass mode. Have no Access to it 

 

I dont know what to do now. Please help!

Thx in advance!

 

UPDATE:

After configuring the gateway by OMADA controller it changed its IP to 192.168.0.1 which is in conflict with ISP router. 

I disconnected ISP router to be able to login to Omada gateway, but the password I set up is invalid.

Cant login to OC200 neither šŸ˜­

 

UPDATE2:

did everything again + I updated ER605 to the newest version.

 

It seems that adopting ER605 in Omada controller kills it. All clients see no gateway, nor have assigned IP. šŸ˜­

Ā  0 Ā  Ā  Ā 
Ā 
Ā  0 Ā  Ā  Ā 
Ā 
#1
Options
11 Reply
Re:Adding gateway to Omada - PROBLEM
2024-02-04 13:25:52

  @VasquezPL 

 

Hello again.

 

As you have noticed, it is bad when the same subnet appears on both sides of the gateway.

 

While you can change the Omada defaults, it is much more work usually than changing your ISP modem config.  Ideally you put your ISP device in bridge mode, ie L2 which means the TPlink device's WAN gets the IP the ISP router would have got.  This is best.

 

If you cannot get bridge working, you can configure your ISP LAN and DHCP on another subnet like 192.168 100.1/24.  Anything other than 192.168 0.1/24 will work.  Statically configure the TPlink WAN to 192.168 100.2/24.  Then tell your ISP modem to make its DMZ 192.168 100.2.  Proceed with Adoptions...

 

If you must change the Omada side, you must configure your controller's default subnet to a subnet other than what the ISP is using.  Let's say 192.168 10.1/24.  You should configure the WAN statically, in your case 192.168 0.2 and tell ISP router to use that same IP as the DMZ.  Factory Reset ER605, power up Er605 without the WAN port connected, adopt and provision.  Once in connected state, you can connect er605 WAN to your ISP router.

<< Paying it forward, one juicy problem at a time... >>
Ā  0 Ā 
Ā  0 Ā 
#2
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-04 14:01:35 - last edited 2024-02-04 16:22:59

ISP router reconfig cant be made. They wont give me a pass. But I did what you wrote

1. Logged to Er605.

2. Set its IP to 192.168.1.1 and to obtain its gateway dynamicaly from ISP router 

3. Set DHCP table to 192.168.1.100-255

4. Restarted SWITCH and OC200 to get IPs from new subnet (192.168.1.100-255)

5. Veryfying if clients get new IPs from correct subnet.

6. OC200 starts to be online. Internet works. Until this stage, all is fine. All clients get correct IPs from new subnet

7. I see @ OMADA that ER605 is uknowm. I Adopt it.

8. It gets adopted. Configuration statge starts.

9. After a while everything is down. Even wifi SSID is not visible. My PC IS NOT seeing aby gateway nor gets an IP.

 

UPDATE:

I did another adoption from www (not mobile app)

Same story. Everything goes down.

 

UPDATE2

I reset everything and set up till point no. 5 on the list above.

Everything works, all IPs are in correct subnet of the router.

I don't touch OC200/Omada controller because it will kill everything.

 

If you know the solution how to adopt safely ER605 - please let me know.

 

Ā  0 Ā 
Ā  0 Ā 
#3
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-04 17:04:01

  @VasquezPL 

 

You need to program all the revised IP info into your controller BEFORE you adopt anything.  Otherwise, controller will reprogram gateway back to 192.168.0.1 and it all melts down again.

 

 

<< Paying it forward, one juicy problem at a time... >>
Ā  0 Ā 
Ā  0 Ā 
#4
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-04 18:28:30 - last edited 2024-02-04 19:17:26

  @d0ugmac1 

I dont understand.

Router/gateway is set to use its own, new subnet, with an IP 192.168.1.1

Switch, all APs, OC controller use new subnet 192.168.1.x

everything seem to be set correctly.

 

could you please elaborate? 

 

OMADA:

screen

 

ER605:

Ā  0 Ā 
Ā  0 Ā 
#5
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-05 01:49:04

Hi @VasquezPL 

Thanks for posting in our business forum.

You probably should call tech support instead of waiting for a reply on the forum. We cannot avoid the reply lag so something might change. It is not a good idea to troubleshoot here.

 

So, if you are changing the subnet, after the adoption, it is normal to see the devices cannot be adopted. Reboot the switch if your controller is connected to the switch.

After the config is synced to the router, the router will be placed in the new subnet. Then after the router stabilizes and you reboot the switch. This will make the switch get the new IP from the router. Same for the controller.

Then hit the adopt and it should work.

 

Above this thread, the Pending looks good to me. Just hit the adopt. Set up the LAN to 192.168.1.1/24 before you hit the adopt. So, after the config syncs, you should get everything under 192.168.1.1/24

 

 

Key is to know that the same subnet, the adoption can happen.

Second, you should know that the DHCP would only renew if a reboot is done.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ā˜›Download Beta Hereā˜š ā˜› ā˜… Configuration Guide ā˜… ā˜š ā˜› ā˜… Knowledge Base ā˜… ā˜š ā˜› ā˜… Troubleshooting Manual ā˜… ā˜š ā— Be kind and nice. ā— Stay on the topic. ā— Post details. ā— Search first. Don't be a lazy asker. ā— Please don't take it for granted. ā— No email confidentiality should be violated. ā— S/N, MAC, and your true public IP should be mosaiced.
Ā  0 Ā 
Ā  0 Ā 
#6
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-05 08:08:21 - last edited 2024-02-05 08:10:30

  @Clive_A Thanks for your reply.

I tried to adopt router twice, with the same results.

it goes from ADOPTING to CONFIGURING stage, and then everything stops working.

Clients stop getting IP etc, no gateway visible in client configs.

 

I suspect that adoption resets router subnet back to 192.168.0.1 and it is in confilct with ISP router.

 

I tried to make small experiment yesterday.

1) plug off ISP router (192.168.0.1) to avoid the conflict

2) log into ER605 router, change its adress to 192.168.0.1 + DHCP reservations to 192.168.0.100-199

3) unplug the switch with OC200 controller, to make OC200 get IP from the subnet mentioned in point 2

4) make an adoption by logging @ OC200

5) change subnet @ ER605 router back to 192.168.1.1 + DHCP reservations to 192.168.1.100-199

6) plug back ISP router.

 

the plan was about to be implemented but I forgot that I had not set the local admin account for OC200 :) ) :) of course cloud account did not work 

I will try to do it today.

 

 

Ā  0 Ā 
Ā  0 Ā 
#7
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-05 15:35:58

  @VasquezPL 

 

Also, please connect your OC200 direct to a LAN port on the ER605 and connect your switch to a second LAN port on the ER605. 

Do NOT loop all traffic through the 2 ports of the OC200!  The OC200 is a stub device and its ports are only 100Mbps.

 

Please show us screen grabs of the Controller where you have configured the WAN interface, and also your LAN subnets.

 

I would expect to see something like this for your WAN port (Site->Settings->Wired Connections->Internet)

 

 

 

 

 

and for the default LAN

 

 

 

<< Paying it forward, one juicy problem at a time... >>
Ā  0 Ā 
Ā  0 Ā 
#8
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-05 18:38:08 - last edited 2024-02-05 18:38:33

  @d0ugmac1 

The only difference is that my WAN is set as dynamic. It gets an IP from ISP router where I have no access.

 

I tried to unplug ISP router and adopt ER605 on 192.168.0.1 subnet (where the ISP router was). and you know what? it does not work.

ADOPTING->PROVISIONING->CONFIGURING->DISCONNECTED.

and it stays in DISCONNECTED state for good.

When I reset it, I can readpot it - but the result is the same - ER605 remains disconnected. Cannot be pinged.

 

I am really really tired of that piece of junk :(

 

Ā  0 Ā 
Ā  0 Ā 
#9
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-05 20:15:51

  @VasquezPL 

 

Sending you a PM

<< Paying it forward, one juicy problem at a time... >>
Ā  1 Ā 
Ā  1 Ā 
#10
Options
Re:Adding gateway to Omada - PROBLEM
2024-02-05 20:43:46

  Current config - switch to static@WAN:

 

 

 

 

 

 

 

 

 

Ā  0 Ā 
Ā  0 Ā 
#11
Options
12

Information

Helpful: 0

Views: 1297

Replies: 11

Related Articles
Adding router/gateway to Omada Controller
546 0
Omada SDN gateway as OpenVPN Client
24669 1
Adding a new Router to an existing TP-Link Omada Controlled network
1145 0
problem in adding a device
425 0
adopting existing Omada gateway in new controller OC200
1856 0
ADDING PAYMENT GATEWAY
260 2
About Us
Press
Copyright Ā© TP-Link Systems Inc. All rights reserved.