What's new

How to get status of aimesh nodes from command line?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

You know you can run a script with crontab on the nodes just like the main router.
Maybe something like

#!/bin/bash
ping -c1 192.168.50.1 > /dev/null
if [ $? -eq 0 ]
then
echo ok
exit 0
else
reboot
That will not help, when they are offline, i can still ping them
 
That will not help, when they are offline, i can still ping them
A reboot doesnt help? only time I had issues with nodes going offline when the distance/obstructions were questionable. Even though signal showed great most the time.
 
is there an easy way to revert back to stock firmware on my nodes?
should i just update the stock firmware over the merlin firmware?
or do i need to hard reset it afterwards?
 
Flash the firmware you want via the main router's GUI.

Remove the AiMesh node after it has rebooted and connected via the main router's GUI. This will reset it to factory defaults. You may want to do an additional WPS Button reset appropriate for your router, to fully reset it.

[Wireless] ASUS router Hard Factory Reset | Official Support | ASUS Global

After doing the above, do not 'touch' the node except by the method below.

Re-associate the node with the main router, again, via the main router's GUI.
 
is there an easy way to revert back to stock firmware on my nodes?
should i just update the stock firmware over the merlin firmware?
or do i need to hard reset it afterwards?
FWIW - I use Merlin 386.4 alpha on Main and latest current Official on my nodes. Everything seems to work, with exception of the Guest1 on Mesh issue that Asus has with the Mesh2 codebase. See my sig.
 
@L&LD did give a pretty good explanation. After that you should not have any issue. If you are still having the same issue, I would advise going to stock fw on your main and try it. If the issue still persists, that is RMA territory.
 
just an update... since running stock firmware on the nodes, no drops anymore from the nodes... so it was a merlin firmware issue after all
main router is still running merlin firmware
 

Similar threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top