Adopt a gateway under same subnet

I have following configuration for my office.
Here, I have statically assigned address (192.168.0.0/16) for my clients below my cisco gateway. Controller gets 192.168.2.112, and ER605 gets 192.168.254.10 for WAN port.
I can't have ER605 assigned to Omada software controller, failing adoption. Not id/passwd problem. Is there any way to get work with?
Should I use ER605's LAN ports only, instead of WAN ports?
Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content

Hi @airplasma
Should I use ER605's LAN ports only, instead of WAN ports?
>>>Yes, to manage the router, the controller should be in the same subnet as the router's LAN network.
- Copy Link
- Report Inappropriate Content

Hi @airplasma
Should I use ER605's LAN ports only, instead of WAN ports?
>>>Yes, to manage the router, the controller should be in the same subnet as the router's LAN network.
- Copy Link
- Report Inappropriate Content
Hi Vincent, thanks for your kind reply.
I now configured my ER605 as Bridge mode, only using LAN ports (besides the first port, WAN), but I can't still have it adopted. (Now the ER605 is on same subnet)
First concern is, if I ping from linux server to ER605, gets reply fine. However, from ER605, using Diagnostics menu with interface "LAN" selected, pinging the server does not respond. I find server is ping-able by using other PC's command lines, so I don't think the firewalls are issue.
What could be the problem?
thx.
- Copy Link
- Report Inappropriate Content
Hi @airplasma
What's the error message when failed to adopt the ER605? Please share with a screenshot of the page.
Although the controller can be pinged by other devices, since the management port of the controller is different, I still recommend that you disable the firewall and exit all antivirus software to try again.
airplasma wrote
Hi Vincent, thanks for your kind reply.
I now configured my ER605 as Bridge mode, only using LAN ports (besides the first port, WAN), but I can't still have it adopted. (Now the ER605 is on same subnet)
First concern is, if I ping from linux server to ER605, gets reply fine. However, from ER605, using Diagnostics menu with interface "LAN" selected, pinging the server does not respond. I find server is ping-able by using other PC's command lines, so I don't think the firewalls are issue.
What could be the problem?
thx.
- Copy Link
- Report Inappropriate Content
Hi, @Vincent-TP
Error message is not shown in the browser, so I looked into the /opt/tplink for logs.
This is log.
07-03-2025 15:01:18.693 INFO [https-jsse-nio-8043-exec-1] [] c.t.s.o.c.u.s.b(): list local interface macs: [52-54-00-AA-C2-B5, 34-5A-60-63-F1-EA]
07-03-2025 15:01:28.614 WARN [https-jsse-nio-8043-exec-2] [] c.t.s.o.m.d.d.m.s.i(): OmadacId(f8633d98c5b4c29ff72052dde7decb4b) device host not enable
07-03-2025 15:01:28.614 WARN [https-jsse-nio-8043-exec-2] [] c.t.s.o.m.c.a.a.e(): omadac OmadacId(f8633d98c5b4c29ff72052dde7decb4b) not exist, can't get device host
07-03-2025 15:01:44.713 INFO [https-jsse-nio-8043-exec-10] [] c.t.s.o.m.l.p.c.f(): set category advanced cache for OmadacId(f8633d98c5b4c29ff72052dde7decb4b) SiteId(6863a2c46e185307ec8f4f90)
07-03-2025 15:02:15.963 INFO [scheduled-pool-9] [] c.t.s.o.m.s.c(): change omadacId : OmadacId(f8633d98c5b4c29ff72052dde7decb4b) siteId : [] to busy
07-03-2025 15:03:27.484 INFO [discovery-work-group-1] [] c.t.s.o.m.d.d.m.e.a(): OmadacId(f8633d98c5b4c29ff72052dde7decb4b) DeviceMac(WL7PWG6R5E3LtAMh42Tz4Tc1potZjpcEjz2X+QVUG8I=) receive discovery when adopting, times[3] reach limit, set adopt fail
thx.
- Copy Link
- Report Inappropriate Content
Hi @airplasma
What specific indications does the controller interface during the adoption? Are there any status changes or other relevant information displayed?
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 237
Replies: 5
Voters 0
No one has voted for it yet.