I have added my route10 to my local controller but it’s constantly showing disconnected.
I have sshd onto the router and checked the domain.txt file deleted the rcapi.txt file and checked the siteid, but all to no avail still will not show as connected. Router is on 1.3k and local controller is on 1.0k
Is it connected/configured with a WAN port?
Yes, I’m using WAN1 pppoe. I have full internet connectivity and my AP’s are connected ok. Just the router will not show as connected
Where is the control connected ?
It’s running in a container on my server which is connected to Lan4 on the Router
Is it possible to test without the PPPoE briefly?
Hi Josh, I ended up having to manage the router via the web controller instead of my local controller. Not ideal as I want everything controlled by the local controller. I think my biggest problem is when I factory reset it it defaults to the 192.168.1.0 subnet, but the rest of my network is on 10.0.1.0 subnet including my controller, so in the setup process when it asks to add to the controller it won’t add to my controller as it’s on a different subnet
That’s an interesting note and we’ll take a look at your idea. In the meantime, what if you move the controller to an address within 192.168.1.0/24 and get adopted, then revert to 10.0.1.0/24?
Hi Josh, this might be a bit tricky as the server that runs all my docker containers is all set up on the 10.0.1.0/24 subnet. Ideally it would be great during the initial setup process if you could set the default settings for vlan1 before adoption. I think this would help a lot of people out
I don’t love this idea, but, just to work around this for your case, what if you actually did the bad thing and introduce a second router to handle that subnet long enough to get adopted and then add a 10.0.1.0/24 VLAN for your other network?
I am curious if you are still dealing with this issue. I have another idea or two to look at if that is the case but if you have solved the problem I’m interested to hear what you learned.
Do you have any devices with sticky IP addresses and possibly a space in the name?
I’ve also done what Josh recommended and plugged into another router to get it connected, then change things, then reconnect it to the original LAN.
Hi Josh, I reset the router, instead of selecting pppoe I used dhcp and connected it to my existing network router. It established an internet connection was able to ping and access the controller, but would still not connect, no matter what I tried. It showed up in my local controller but when I clicked set up, nothing happens.
Delete the Route10 from your site as well as power-on reset by holding the reset button before plugging in the power until the LED activity on the top logo begins to fully clear the old configuration.
Hi Josh, also tried what you suggested still will not connect to the local controller
When I click set up nothing happens, when I add it to the cloud controller it adds straight away
And you completed the setup wizard, if I understand your other notes correctly?
Yeah, reset by pulling the power holding in the reset button and adding back power until the activity lights start blinking. Then go to 192.168.1.1 set up wan as dhcp, it gets an ip from my current 10.0.1.0/24 router. I then can access my local controller which shows the router as in the previous screenshot but clicking set up does nothing at all
Can you then go back to the UI on route10 and specify the controller address? Like with the APS?
Yeah, I specifiy the address of my local controller, click add to controller and again nothing.
sorry one last question, are you specifying the local controller address using the mdns name that it creates, or the IP adddress? From what I have seen, you have to specify the local.xxx mdns address for it to work.
