ER605 no Omada possible

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

ER605 no Omada possible

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

U3mi

2023-05-19 06:30:56

Posts: 1

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2023-05-18

ER605 no Omada possible

2023-05-19 06:30:56

Model: ER605 (TL-R605)

Hardware Version:

Firmware Version:

Hi,

i have a network with subnet 192.168.179.0/24 and all my TP-Link devices in here. Since a couple of days I have also an ER605 which i cannot adopt into Omada C200 Controller.

In the dashboard of my Omada instance I see that the device is recognized with IP 192.168.0.1/24 which is the default VLAN 1 for this device. Trying to adopt this device always fails.

Do you have an Idea how to adopt this Router?

BR Tim

3 Reply

d0ugmac1

LV5

2023-05-19 18:08:54

Posts: 2104

Helpful: 767

Solutions: 190

Stories: 0

Registered: 2022-03-05

Re:ER605 no Omada possible

2023-05-19 18:08:54

@U3mi

Easiest way would be to login in Standalone mode (admin/admin I think). Change the default LAN IP subnet from 192.168.0.0/24 to 192.168.179.0/24 (so assign your ER605's LAN (VLAN 1) an IP on 192.168.179.x AND you should probably disable the DHCP server temporarily for this LAN. Once it's managed, the Controller will reset everything up again properly. I believe this is a cleaner approach for an already working controller setup.

In general, it can be a bit of fight to use a different subnet other than 192.168.0.0, but it is doable as long as your Controller is in DHCP mode and can get an IP from the router as you change it's IP/subnet.

<< Paying it forward, one juicy problem at a time... >>

Libik

LV3

2023-05-19 18:30:28

Posts: 137

Helpful: 37

Solutions: 8

Stories: 0

Registered: 2021-02-18

Re:ER605 no Omada possible

2023-05-19 18:30:28

You could temporarily change Controller network to 192.168.0.0/24, adopt ER605 and change it back. This is/was known problem. I have to do the same procedure. Other way which suggests d0ugmac1 does not work for me (but it was with 1.0.x FW or something similar).