ER7206 - Option 138 doesn't work?
Redoing my setup and now have my devices on a mgmt lan separate from rest of servers and misc devices. Router doesn't want to connect to controller even with option 138 configured correctly. My Switch and 5 AP's all work properly (now that it's setup correctly), but the router refuses to conenct across subnets. if i move the controller container to the mgmt subnet, it connects perfectly.
is there a bug in the router firnware?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
To make the router visible in the controller, enter the controller’s IP address in the router’s config at:
System Tools>Controller Settings>Controller Inform URL>Inform URL/IP Address:
I got my router adopted after that, but it wasn’t a success after all since the router’s IP address wasn’t properly ported into the controller. After I corrected it manually, the router got disconnected from the controller and I had to back out. You may have better luck. My switch is not TP-Link and the whole configuration isn’t quite the same as yours.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Here's the data on my router and controller.
Hardware Version: ER7206 v1.0
Firmware Version: 1.2.3 Build 20221104 Rel.41500
Omada Controller: Software type
Version: 5.7.4
Controller Host: UBUNTU
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 640
Replies: 5
Voters 0
No one has voted for it yet.