Remotely rebooting or accessing aimesh node?

[ah1750]

Hey all, wondering if anyone has some interesting ideas for this issue.

I've got an RT-AX86U paired with an aimesh node RT-AX57. The system is remote and I don't have physical access right now. The 57 lost connection to the 86 and I can't get it to re-pair. The 86 is running 3004.388.7 and I can use the site survey to see that the 57 is still showing a 2.4 3(ax) channel, however I have no way to connect to it that I can find. I have Tailscale setup on the 86, so it's pretty easy for me to access it via the main webpage or SSH.

Wondering if there's anyway to SSH to the 86 to connect it to the 57 to reboot it somehow? Or any other hacks to sort the aimesh via the command line?

In the future I'll setup a linux box on the 86, but as of now I'm kinda trying to figure out if there's anyway to get around this.

Thanks.

 

[DJones]

Hey all, wondering if anyone has some interesting ideas for this issue.

I've got an RT-AX86U paired with an aimesh node RT-AX57. The system is remote and I don't have physical access right now. The 57 lost connection to the 86 and I can't get it to re-pair. The 86 is running 3004.388.7 and I can use the site survey to see that the 57 is still showing a 2.4 3(ax) channel, however I have no way to connect to it that I can find. I have Tailscale setup on the 86, so it's pretty easy for me to access it via the main webpage or SSH.

Wondering if there's anyway to SSH to the 86 to connect it to the 57 to reboot it somehow? Or any other hacks to sort the aimesh via the command line?

In the future I'll setup a linux box on the 86, but as of now I'm kinda trying to figure out if there's anyway to get around this.

Thanks.

If you have access to the RT-AX86U perhaps try rebooting the router within the gui interface or using SSH in amtm or by using the command reboot.

This might allow it to reconnect. However if you don’t have a wired connection to the RT-AX57 as fallback unless it reconnects itself you won’t have much luck unless you have scheduled reboot enabled on both and that causes reconnection when the times up for a restart.

My suggestion for the future if you can’t easily get a wired connection just invest in a cheap powerline adapter kit so it can communicate through your houses power outlet. Even if your primary uplink is through WIFI for the AIMesh node if the router disconnects to your main AIMesh router it should regain a wifi connection or at minimum you can reboot the AIMesh router because you have that fallback.

 

[ah1750]

I've done re-boots of the 86 from the GUI and the iOS app, I may try an all-radio-off reboot and see if there's some sort of magic there.

For whatever reason the 57 loses the 5ghz connection and doesn't broadcast 5ghz either when the failure happens. The fun part is that its 2.4ghz stays active and a lot of my IOT devices stay connected to that, so I lose all of those. As failures go, it's a pretty good one. I tried shutting off 5ghz on the 86 and seeing if aimesh would connect using just that (since the 57's 2.4 is still showing), but that didn't work. Not that I'd expect it to, but you never know.

The scheduled reboot is a great idea, although I'm a bit concerned with it losing connection after a reboot, but agreed, that would have sorted this problem most likely.

Good idea about the power line, I've never used those before, that will be on the upgrade list.

Appreciate the reply.