Aimesh drops Router node once a day

[Scansbar]

Hey guys,
Was wondering if any pro's out there can give me some tips or troubleshooting on this one. In my wireless logs I see my router node drop once a day (I"m not connecting them with an Ethernet back haul). I ran a continuous ping from my pc and noticed that it drops between 30-45 seconds. Is this a normal behavior? The only thing I can think of is interference but it happens between 2am and 4am. Would it be better to use the repeater function instead to use different channels or to see the log of the repeater? I don't know, what do you guys think?
Thank you in advance.

 

[OzarkEdge]

Should one say the router node is dropping, or... ALL remote nodes are dropping?

OE

 

[Scansbar]

Hi OE,
I have a main router and a node router both are ac68u's. The node router is dropping it's connection with the main router via a wifi back haul. I have about 5 wireless devices on the main router which didn't loose it's connection, only the node router looses the connection and all the wireless devices attached to it the node router.
Thank you.

 

[OzarkEdge]

Got it... the router (root node) is up; the node (remote node) goes down. ASUS calls them router and node(s) once they are in an AiMesh.

The wireless backhaul could be too distant for certain ambient conditions... how far is it... what does the Wireless Log RSSI and Tx/Rx rates look like for the 2.4 and 5.0 GHz backhaul MACs?

OE

 

[Scansbar]

Its about-54 for both macs checked it a few times through out the day so I'd assume it was that around the time is disconnects.

 

[OzarkEdge]

-54 should be fine. I wish I had more diagnostic advice. Absent that, I can only suggest to reset/initialize both units, reconfigure the router from scratch, and add the node from the router GUI. If you did not reset to factory defaults after the most recent firmware upgrade, then definitely do this.

The 2-4 AM drop is curious. Dropping from interference seems too catastrophic. Power disturbance?... putting the node on a UPS would stop and answer this.

OE

 

[Scansbar]

Hi, I currently have it on ups but your point of "If you did not reset to factory defaults after the most recent firmware upgrade, then definitely do this". I did not do that as the node router was store bought but I did upgrade both firmware. The factory defaults is that the initialization button. Would I have to reassign all the dhcp reserved IP address all over or can I upload the config file you think? Thanks again for your insight, great forum ,great people.

 

[OzarkEdge]

We may be getting somewhere...

This FAQ explains the factory default reset. This is something you should do religiously while AiMesh is still a work in progress. There is too much change being introduced to trust otherwise. Once the dust settles, you can skip it for minor firmware updates... someone here who understands firmware can comment on this more fully regarding version number changes. But for now, I would reset all units after each upgrade. Yeah, it's a hassle.

You can reset from the GUI or by holding the button until the power LED slowly flashes. You can also initialize from the GUI (do this this time around!). Initialize resets to factory defaults AND purges logged data and whatever else... it's more thorough.

Then rebuild your AiMesh from scratch. Do not restore a saved configuration since it may reintroduce whatever is messed up. During this period of AiMesh evolution, you can save time by keeping your configuration as simple as possible. When you add the node, it should be in default condition. With two 68Us, you can also rotate their roles... rebuild the node as the router... at least you can copy the former router's settings; then add the former router as the node.

My notes (such as they are for now) may add to this.

OE

 

[Grisu]

You can reset from the GUI or by holding the button until the power LED slowly flashes. You can also initialize from the GUI (do this this time around!). Initialize resets to factory defaults AND purges logged data and whatever else... it's more thorough.

By holding WPS button!

 

[Scansbar]

That's great info, I read your notes and the faq. Just a little confused on one part since I rarely get free time to troubleshoot so I want to make sure I got this right since in my setting lsd i have two buttons factory default and factory initialize do I use these or holding down the rest button or the wps and you commented. Couldn't find the wps mentioned in either links. I read it a few times but would appreciate if you would help clarify. Currently I have bother routers up and running on the latest firmware.
Do you have experience with using the router as a repeater mode or recommend it since it's been around much longer than aimesh?
Truly appreciate your time,
Warm regards

 

[OzarkEdge]

That's great info, I read your notes and the faq. Just a little confused on one part since I rarely get free time to troubleshoot so I want to make sure I got this right since in my setting lsd i have two buttons factory default and factory initialize do I use these or holding down the rest button or the wps and you commented. Couldn't find the wps mentioned in either links. I read it a few times but would appreciate if you would help clarify. Currently I have bother routers up and running on the latest firmware.
Do you have experience with using the router as a repeater mode or recommend it since it's been around much longer than aimesh?
Truly appreciate your time,
Warm regards

The WPS button reset method is mentioned in the FAQ as a last resort for when the router will not boot. Read it again!

The GUI Initialize reset method was mentioned (by the FAQ author) in replies to the FAQ but those have been removed recently, probably to purge misinformation posted by others. Regardless, Initialize is still a valid reset option in the GUI.

Just use the reset button or the GUI Reset or the GUI Initialize as I already noted above. For your node, use the reset button to access the GUI and then use the GUI Initialize to reset again to be sure. And cycle power once while you're at it.

I've used repeater mode once so I'm not fluent enough to discuss it other than to suggest a working AiMesh is a better solution. So, be patient and be persistent and finish installing your AiMesh correctly as instructed in the AiMesh Install FAQ. Otherwise, you are just flailing around halfway.

(If your 68U firmware does not yet have the Smart Connect feature under Wireless, then use separate WiFi SSIDs such as Scansbar-24 and Scansbar-50. Otherwise, use a single SSID such as Scansbar, unless you want to use separate SSIDs and/or manage the wireless mode, channel bandwidth, control channel, and extension channel settings on your own.)

OE

 

[OzarkEdge]

By holding WPS button!

Since you replied to me, and since your reply is insufficient instruction for the OP to make use of... it's not even a complete sentence, I will conclude that you are only trying to remind me of the WPS reset method. Thanks, but the WPS reset method is explained in the previously mentioned FAQ I referenced.

OE

 

[Grisu]

Since you replied to me, and since your reply is insufficient instruction for the OP to make use of... it's not even a complete sentence, I will conclude that you are only trying to remind me of the WPS reset method. Thanks, but the WPS reset method is explained in the previously mentioned FAQ I referenced.

OE

Only wanted to make clear to press WPS and not maybe reset button, obviouly he just struggled exactly with this!
It was NOTHING against you to be pissed off, only meant as addition to your text as I missed it and maybe some others will read it too without reading the full FAQ.
I replied to exactly this one sentence, and used exactly your words with WPS inserted instead of "the". Never meant to be a full sentence.
Probabely I should have written: ... by holding WPS button ...

 

[Scansbar]

OE you have been great help, I may of missed it but your clarification and instructions are very well put. I'll give it a try and hopefully aimesh will be much better than it is for me today. I remotely checked on it and lost node today for a few seconds and my signal was at - 64. Well worst case ill try repeater mode but I'll do what you suggested first and give it another try and see where it leads, thanks again.

 

[OzarkEdge]

Only wanted to make clear to press WPS and not maybe reset button, obviouly he just struggled exactly with this!
It was NOTHING against you to be pissed off, only meant as addition to your text as I missed it and maybe some others will read it too without reading the full FAQ.
I replied to exactly this one sentence, and used exactly your words with WPS inserted instead of "the". Never meant to be a full sentence.
Probabely I should have written: ... by holding WPS button ...

No, the OP is not struggling... he is discovering and learning. It would be helpful to give him information he can use.

WPS reset requires a procedure you did not explain... here is the relevant extract from the FAQ that does explain it:

*****
How do I do a factory default reset?
Multiple ways to do so, which will depend on your particular situation.

If your router fails to boot due to corrupted/invalid nvram settings, then you will have to turn off the router, press the WPS button (on Asus routers), then turn on the router. Wait about 10 seconds, then release the WPS button.

If the router is booting correctly, then you can use any of the following:

• While router is running, press the reset button for about 5 secs, then release it. Router will then reboot.
• From the webui, on the same page where you can save/restore saved settings, there is a button to restore factory default values
• Over SSH, you can run the "nvram erase" command.
• Over SSH you can manually erase the nvram partition (do not use this method unless you know what you are doing! Erasing the wrong partition can permanently brick your router!) Run "mtd-erase nvram", followed by PHYSICALLY turning off then on the router. Do not use the reboot command.

*****

Since the OP's router is booting fine, he doesn't need to consider using the more involved WPS reset method for his current issue... and every time he upgrades AiMesh firmware... the later would be a waste of his time and energy.

If using the WPS reset method will make a difference for the OP's issue, explain why so people understand what your point is. Your implication is that the OP must use the WPS reset method over the other methods previously suggested... he doesn't. You're only confusing the matter with your unnecessary (it's in the FAQ) and incomplete (you did not mention cycling power) and unexplained recommendation (why?... his router boots up fine).

OE

 

[LimJK]

No, the OP is not struggling... he is discovering and learning. It would be helpful to give him information he can use.

WPS reset requires a procedure you did not explain... here is the relevant extract from the FAQ that does explain it:

*****
How do I do a factory default reset?
Multiple ways to do so, which will depend on your particular situation.

If your router fails to boot due to corrupted/invalid nvram settings, then you will have to turn off the router, press the WPS button (on Asus routers), then turn on the router. Wait about 10 seconds, then release the WPS button.

If the router is booting correctly, then you can use any of the following:

• While router is running, press the reset button for about 5 secs, then release it. Router will then reboot.
• From the webui, on the same page where you can save/restore saved settings, there is a button to restore factory default values
• Over SSH, you can run the "nvram erase" command.
• Over SSH you can manually erase the nvram partition (do not use this method unless you know what you are doing! Erasing the wrong partition can permanently brick your router!) Run "mtd-erase nvram", followed by PHYSICALLY turning off then on the router. Do not use the reboot command.

*****

Since the OP's router is booting fine, he doesn't need to consider using the more involved WPS reset method for his current issue... and every time he upgrades AiMesh firmware... the later would be a waste of his time and energy.

If using the WPS reset method will make a difference for the OP's issue, explain why so people understand what your point is. Your implication is that the OP must use the WPS reset method over the other methods previously suggested... he doesn't. You're only confusing the matter with your unnecessary (it's in the FAQ) and incomplete (you did not mention cycling power) and unexplained recommendation (why?... his router boots up fine).

OE

Excellent

Just to add ... the newer firmware has added "Initialize" option to the "Restore" under factory default. I normally do "Initialize" from GUI. Here for more information:
https://www.snbforums.com/threads/rt-ac86u-administration-restore-vs-initialize.41944/

 

[OzarkEdge]

Excellent

Just to add ... the newer firmware has added "Initialize" option to the "Restore" under factory default. I normally do "Initialize" from GUI. Here for more information:
https://www.snbforums.com/threads/rt-ac86u-administration-restore-vs-initialize.41944/

Me, too... it's there and easy and thorough according to RMerlin:

"This option is new with 382_18219. Initialize will also remove the existing content of the /jffs/.sys/ folder which contains various data such as the (forecoming) Notification Center, Web History, etc... Restore will only erase the nvram configuration."

I recently read a thread here that implied that a router ran out of usable memory. The user claimed his router was storing a lengthy feedback message he had sent (or tried to send) to ASUS from within the router GUI. If so, I assume this is the sort of miscellaneous data that the GUI Initialize function will purge. So, I use Initialize whenever possible.

OE

 

[Grisu]

seems I didnt read well enough and assumed pressing button while powering on, but you wrote till power LED slowly flashing.
Could you excuse this huge mistake?

 

[OzarkEdge]

seems I didnt read well enough and assumed pressing button while powering on, but you wrote till power LED slowly flashing.
Could you excuse this huge mistake?

No problem... you're not the issue... helping the OP is my only goal here.

OE

 

[stan79]

The new firmware is much stable but still after 1-2 days of usage, the connection between the router n node will keep on disconnecting resulting the node kicking the client out. Gotta wait for several minutes after the router n node connection is back, then the client will be able to connect to the node.

Rebooting helps a little but no much help. Even re-initialize both the router and node and reconfigure do not help much too. Or maybe my 2 x AC68U are too old and slow or ASUS really can't solve this issue. This issue had been around even since AiMesh was made available.