What's new

ASUS RT-AC68U AiMesh drops (Again)

  • 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!

After my initial post I set a fixed IP address outside of the DHCP range, which is basically what I do for all know devices anyhow. I began to watch this under the AiMesh tab for the network, but less than "eagle eye". I did this until i received these replies. I saw no node disconnects and even with my laptop closer to the primary node, it stayed on the mesh node most of the time. I did have a couple of instances where my laptop connected to the router and then back to the node, not sure if this was after waking up from sleep, but in any event I do not know why the client moved back to the mesh node which was further away (see below).

@OE - The mesh node is about 35 feet and a few walls from the router. I have 2 primary use locations;
1 - Office about 10 feet past the mesh node
2 - Livingroom between the nodes, about 15 feet from the router and about 25 feet and 3 walls from the mesh node.

@OE, I have now read your config notes, and will try reducing the 2.4 RSSI to -55. Will this not make the clients want to move more? WiFi Analyzer indicates that that about midpoint the RSSI for 2.4Ghz is -37 <=> -42 range.

@liquor, thank you.

I have reset my config (IE removed the static IP) and spent some time today closely monitoring the GUI. I see 2 different issues.

1 - I do see the node dropping, a total of 4 times in about 90 minutes. Two of the times the node dropped while trying to connect a client to the network, once on each band. The other 2 times, on 2.4Ghz, the node disappeared from the GUI for a couple of minutes. As I have other unrelated APs it found something else to connect to.

2 - I am seeing the client move between nodes, ATM, I am sitting on my office, (past the mesh node) and, twice while writing this, the laptop moved to the router (45 feet). Reconnecting the device indicates it is reconnecting to the Router, which it does, and then a few seconds later moves to the node.

I will reset the fixed IP and drop the RSSI for 2.4 and report back in a few days.
 
Glad I found this thread.

I am also suffering from this exact same issue. 2x RT-AC68U and 1x RT-AC66U B1. The main router will drop connection to both nodes (AC68U & AC66U B1) a few times a day. Digging into the logs does not reveal anything unusual.

So far, I have done everything what everyone else have been repeating, yet the issue still persists.

I am trialing to make sure that this setup is as stable as it can be, as I plan to put one of the AC68U and AC66U B1 at my parents' place, but this frequent disconnection issues is quite a headache.

Funnily, with my own RT-AX56U + RT-AC68U combo as a mesh, it is a rock solid setup. No disconnection or weird error messages in the system log.
 
Glad I found this thread.

I am also suffering from this exact same issue. 2x RT-AC68U and 1x RT-AC66U B1. The main router will drop connection to both nodes (AC68U & AC66U B1) a few times a day. Digging into the logs does not reveal anything unusual.

So far, I have done everything what everyone else have been repeating, yet the issue still persists.

I am trialing to make sure that this setup is as stable as it can be, as I plan to put one of the AC68U and AC66U B1 at my parents' place, but this frequent disconnection issues is quite a headache.

Funnily, with my own RT-AX56U + RT-AC68U combo as a mesh, it is a rock solid setup. No disconnection or weird error messages in the system log.
First, upgrade to the new firmware. AC68U_300438643129 (also for the AC66U_B1)
For older routers that do not have SmartConnect use different SSID's for 2.4 and 5 GHZ.
Use fixed channels and bandwidth: 2.4 GHz at 20 MHz on channel 1, 6 or 11. 5 GHz at 80 MHz on channel 36 or 149. Do not use DFS channels.
Disable Airtime Fairness and Universal Beamforming in professional WIFI settings.
Manually assign the nodes an IP address in LAN/DHCP Server/Manually Assign IP... This does seem to help a lot.
 
First, upgrade to the new firmware. AC68U_300438643129 (also for the AC66U_B1)
For older routers that do not have SmartConnect use different SSID's for 2.4 and 5 GHZ.
Use fixed channels and bandwidth: 2.4 GHz at 20 MHz on channel 1, 6 or 11. 5 GHz at 80 MHz on channel 36 or 149. Do not use DFS channels.
Disable Airtime Fairness and Universal Beamforming in professional WIFI settings.
Manually assign the nodes an IP address in LAN/DHCP Server/Manually Assign IP... This does seem to help a lot.

nice, I saw your reply in the AC68U firmware thread. this gives me some hope that the ac68u isn't completely wasted
 
It's only been a couple of hours since i flashed the latest firmware, but nodes are dropping again

May 23 13:11:51 syslog: wlceventd_proc_event(527): eth2: Auth 10:62:EB:A4:0A:F6, status: Successful (0), rssi:0
May 23 13:11:51 syslog: wlceventd_proc_event(556): eth2: Assoc 10:62:EB:A4:0A:F6, status: Successful (0), rssi:0
May 23 13:11:51 syslog: wlceventd_proc_event(527): eth1: Auth 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:11:51 syslog: wlceventd_proc_event(556): eth1: Assoc 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:11:54 syslog: wlceventd_proc_event(508): eth1: Disassoc 10:62:EB:A4:0A:F3, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-43
May 23 13:11:58 syslog: wlceventd_proc_event(527): eth1: Auth 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:11:58 syslog: wlceventd_proc_event(556): eth1: Assoc 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:12:42 roamast: [EXAP]ignore static clients 10:62:EB:A4:0A:F3
May 23 13:12:45 syslog: wlceventd_proc_event(508): eth1: Disassoc 10:62:EB:A4:0A:F3, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:-41
May 23 13:12:51 syslog: wlceventd_proc_event(527): eth1: Auth 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:12:51 syslog: wlceventd_proc_event(527): eth1: Auth 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:12:51 syslog: wlceventd_proc_event(556): eth1: Assoc 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:12:59 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 10:62:EB:A4:0A:F3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-39
May 23 13:13:09 syslog: wlceventd_proc_event(527): eth1: Auth 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:13:09 syslog: wlceventd_proc_event(556): eth1: Assoc 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:16:52 syslog: wlceventd_proc_event(508): eth1: Disassoc 10:62:EB:A4:0A:F3, status: 0, reason: Class 3 frame received from nonassociated station (7), rssi:-45
May 23 13:16:53 syslog: wlceventd_proc_event(527): eth1: Auth 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:16:53 syslog: wlceventd_proc_event(556): eth1: Assoc 10:62:EB:A4:0A:F3, status: Successful (0), rssi:0
May 23 13:16:54 syslog: wlceventd_proc_event(527): eth2: Auth 50:3E:AA:62:54:D5, status: Successful (0), rssi:0
May 23 13:16:54 syslog: wlceventd_proc_event(537): eth2: ReAssoc 50:3E:AA:62:54:D5, status: Successful (0), rssi:0
 
It's only been a couple of hours since i flashed the latest firmware, but nodes are dropping again
Do you have wireless backhaul? Since I switched to wired I didn't notice any drop on the node.

What I noticed however is that the 5Ghz network occasionally slow down to a crawl on my main AC86u router, which might explain why my node was disconnecting when I had a wireless backhaul. So root cause in my case might be the 5Ghz band on my main router... I was using fixed channel 36 but with 20/40/80 Mhz width option. I changed that to a fixed 80 Mhz to see if it help the 5Ghz stability on the main router...
 
Do you have wireless backhaul? Since I switched to wired I didn't notice any drop on the node.

What I noticed however is that the 5Ghz network occasionally slow down to a crawl on my main AC86u router, which might explain why my node was disconnecting when I had a wireless backhaul. So root cause in my case might be the 5Ghz band on my main router... I was using fixed channel 36 but with 20/40/80 Mhz width option. I changed that to a fixed 80 Mhz to see if it help the 5Ghz stability on the main router...
Yeah I am using wireless backhaul since wired is not an option.

Tried using fixed 80 Mhz channel, but it just only dropped.
 
So, admittedly I do not know how to properly interpret the logs, but they look similar to mine.

A few things I noticed
  • Lots of "rssi:0"
  • The connections indicate ETH1 or ETH2, not wireless

I have also seen entries similar to this, not sure if this is the mesh node saying good bye.
Code:
May 23 13:12:59 syslog: wlceventd_proc_event(491): eth1: Deauth_ind 10:62:EB:A4:0A:F3, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-39
 
I've initialized that problematic RT-AC68U as an AiMesh node and things seem stable so far. fingers crossed
 
I had a similar drop problem between a pair of 68Us. Eventually RMA'd one unit but even that didn't resolve it. I went around and around with this before finding the fix - reverting to Firmware Version 3.0.0.4.384 finally solved the problem. Since then the connection has been rock solid, no drops. A later firmware might still work but I'm not interested in chasing this around. I'm just happy that it works.
 

Latest threads

Sign Up For SNBForums Daily Digest

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