TL-R605 new model - Omaha adoption problems (workaround found!)
TL-R605 new model - Omaha adoption problems (workaround found!)
I want to use Omada to manage my network which is built on a 192.168.1.x range. I installed the router but need to change the default LAN address for port 5 from the default 192.168.0.1 but the adoption fails every time - it gets almost to the end of the process and then reboots and the LAN port returns to its default. It seems this happens no matter what approach is taken to adopt it other than to move the controller to the 192.168.1.x range...
I've spoken to tech support and we've tried simplifying the network config by directly wiring the controller to port five and setting the controller up to a 192.168.0.x ip so I can adopt it then change the lan port up before changing the IP of the controller back to it's normal setting (yep it's complicated!)That allows adoption but as soon as I move the controller back to 192.168.1.x address Omada drops the router again and it sets itself back to the default ip.
looks like a software bug to me can TP link replicate the problem?
----------------------- update found a workaround to enable adoption -------------------------
So after a day or so of failed adoptions and trying different things I've managed to at last get the router adopted by Omada and on the subnet I want it to be on not the default. Hope this helps someone else:
1. Reset the router to factory, login and set password and user name, go into the router and set the controller settings to the URL of the controller I also enabled cloud control (not sure if that's needed though)
2. On the Host of the Omada controller - I disabled any services running high bandwidth services e.g. blue iris for CCTV, I also temporarily disabled the firewall,
3. on the host of the Omada controller change the IP address to something on the 192.168.0.1 address range and point the gateway to 192.168.0.1
4. Bring up the Omada and once the router is available click adopt and enter password and username... at this point you'll know if its going to work as it starts provisioning quite quickly.
5. Once provisioned and connected go into the Omada controller and select the router - on the right hand side navigate to the config menu/common settings.. settings/wired networks/LAN - edit the LAN address and change it to the address you want on your controllers original IP range (Mine is 192.168.1.x)
6. On the Host of the Omada software - reverse the IP address change you made on step 3
7. The Omada controller should now adopt all of your devices again including the router...
Hope this helps others
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thank you for your help. After setting subnet same as default it works but it is really annoying bug. Please fix this. For some people even impossible.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Shedbuilder Just had the same issue last night.
Anyone else notice that it appears to be hard to get OC200? Supply low and prices going up.
I had deployed an er605 first and was adding the OC200 after (waiting on parts) and had to do a complete router reset to get it to adopt.
- Copy Link
- Report Inappropriate Content
@Shedbuilder - Thank you for your answer
I think what you are saying is to move the router and your controller machine to 192.168.0.x range
Adopt the switch
Then move everything back ?
Did you try it without a hardware reset before ?
I have DHCP fixed addresses
Broadband login
VLAN setup
.........
not sure what will happen when I change the switch IP but I can hope
I don't really want to do them all again :-)
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 7332
Replies: 14