What's new

ASUS RT-AC86U Firmware version 3.0.0.4.384.45717

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

This build seems to do/log this:

Code:
May 25 14:58:10 acsd: selected channel spec: 0xe19b (153/80)
May 25 14:58:10 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 14:58:10 acsd: selected channel spec: 0xe19b (153/80)
May 25 15:13:12 acsd: selected channel spec: 0xe19b (153/80)
May 25 15:13:12 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 15:13:12 acsd: selected channel spec: 0xe19b (153/80)
May 25 15:28:14 acsd: selected channel spec: 0xe19b (153/80)
May 25 15:28:14 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 15:28:14 acsd: selected channel spec: 0xe19b (153/80)
May 25 15:43:16 acsd: selected channel spec: 0xe02a (36/80)
May 25 15:43:16 acsd: Adjusted channel spec: 0xe02a (36/80)
May 25 15:43:16 acsd: selected channel spec: 0xe02a (36/80)
May 25 15:58:18 acsd: selected channel spec: 0xe19b (153/80)
May 25 15:58:18 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 15:58:18 acsd: selected channel spec: 0xe19b (153/80)
May 25 16:13:20 acsd: selected channel spec: 0xe02a (36/80)
May 25 16:13:20 acsd: Adjusted channel spec: 0xe02a (36/80)
May 25 16:13:20 acsd: selected channel spec: 0xe02a (36/80)
May 25 16:28:22 acsd: selected channel spec: 0xe19b (153/80)
May 25 16:28:22 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 16:28:22 acsd: selected channel spec: 0xe19b (153/80)
May 25 16:43:24 acsd: selected channel spec: 0xe19b (153/80)
May 25 16:43:24 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 16:43:24 acsd: selected channel spec: 0xe19b (153/80)
May 25 16:58:26 acsd: selected channel spec: 0xe29b (157/80)
May 25 16:58:26 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 16:58:26 acsd: selected channel spec: 0xe29b (157/80)
May 25 17:13:27 acsd: selected channel spec: 0xe19b (153/80)
May 25 17:13:27 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 17:13:27 acsd: selected channel spec: 0xe19b (153/80)
May 25 17:28:29 acsd: selected channel spec: 0xe29b (157/80)
May 25 17:28:29 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 17:28:29 acsd: selected channel spec: 0xe29b (157/80)
May 25 17:43:31 acsd: selected channel spec: 0xe29b (157/80)
May 25 17:43:31 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 17:43:31 acsd: selected channel spec: 0xe29b (157/80)
May 25 17:58:33 acsd: selected channel spec: 0xe29b (157/80)
May 25 17:58:33 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 17:58:33 acsd: selected channel spec: 0xe29b (157/80)
May 25 18:13:35 acsd: selected channel spec: 0xe02a (36/80)
May 25 18:13:35 acsd: Adjusted channel spec: 0xe02a (36/80)
May 25 18:13:35 acsd: selected channel spec: 0xe02a (36/80)
May 25 18:28:37 acsd: selected channel spec: 0xe22a (44/80)
May 25 18:28:37 acsd: Adjusted channel spec: 0xe22a (44/80)
May 25 18:28:37 acsd: selected channel spec: 0xe22a (44/80)
May 25 18:43:39 acsd: selected channel spec: 0xe29b (157/80)
May 25 18:43:39 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 18:43:39 acsd: selected channel spec: 0xe29b (157/80)
May 25 18:58:41 acsd: selected channel spec: 0xe29b (157/80)
May 25 18:58:41 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 18:58:41 acsd: selected channel spec: 0xe29b (157/80)
May 25 19:13:43 acsd: selected channel spec: 0xe29b (157/80)
May 25 19:13:43 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 19:13:43 acsd: selected channel spec: 0xe29b (157/80)
May 25 19:28:44 acsd: selected channel spec: 0xe29b (157/80)
May 25 19:28:44 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 19:28:44 acsd: selected channel spec: 0xe29b (157/80)
May 25 19:43:46 acsd: selected channel spec: 0xe02a (36/80)
May 25 19:43:46 acsd: Adjusted channel spec: 0xe02a (36/80)
May 25 19:43:46 acsd: selected channel spec: 0xe02a (36/80)
May 25 19:58:48 acsd: selected channel spec: 0xe29b (157/80)
May 25 19:58:48 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 19:58:48 acsd: selected channel spec: 0xe29b (157/80)
May 25 20:13:50 acsd: selected channel spec: 0xe02a (36/80)
May 25 20:13:50 acsd: Adjusted channel spec: 0xe02a (36/80)
May 25 20:13:50 acsd: selected channel spec: 0xe02a (36/80)
May 25 20:28:52 acsd: selected channel spec: 0xe29b (157/80)
May 25 20:28:52 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 20:28:52 acsd: selected channel spec: 0xe29b (157/80)
May 25 20:43:54 acsd: selected channel spec: 0xe29b (157/80)
May 25 20:43:54 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 20:43:54 acsd: selected channel spec: 0xe29b (157/80)
May 25 20:58:56 acsd: selected channel spec: 0xe29b (157/80)
May 25 20:58:56 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 20:58:56 acsd: selected channel spec: 0xe29b (157/80)
May 25 21:13:58 acsd: selected channel spec: 0xe19b (153/80)
May 25 21:13:58 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 21:13:58 acsd: selected channel spec: 0xe19b (153/80)
May 25 21:29:00 acsd: selected channel spec: 0xe19b (153/80)
May 25 21:29:00 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 21:29:00 acsd: selected channel spec: 0xe19b (153/80)
May 25 21:44:02 acsd: selected channel spec: 0xe29b (157/80)
May 25 21:44:02 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 21:44:02 acsd: selected channel spec: 0xe29b (157/80)
May 25 21:59:03 acsd: selected channel spec: 0xe29b (157/80)
May 25 21:59:03 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 21:59:03 acsd: selected channel spec: 0xe29b (157/80)
May 25 22:14:06 acsd: selected channel spec: 0xe19b (153/80)
May 25 22:14:06 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 22:14:06 acsd: selected channel spec: 0xe19b (153/80)
May 25 22:29:08 acsd: selected channel spec: 0xe19b (153/80)
May 25 22:29:08 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 22:29:08 acsd: selected channel spec: 0xe19b (153/80)
May 25 22:44:10 acsd: selected channel spec: 0xe19b (153/80)
May 25 22:44:10 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 22:44:10 acsd: selected channel spec: 0xe19b (153/80)
May 25 22:59:12 acsd: selected channel spec: 0xe19b (153/80)
May 25 22:59:12 acsd: Adjusted channel spec: 0xe19b (153/80)
May 25 22:59:12 acsd: selected channel spec: 0xe19b (153/80)
May 25 23:14:14 acsd: selected channel spec: 0xe29b (157/80)
May 25 23:14:14 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 23:14:14 acsd: selected channel spec: 0xe29b (157/80)
May 25 23:29:16 acsd: selected channel spec: 0xe29b (157/80)
May 25 23:29:16 acsd: Adjusted channel spec: 0xe29b (157/80)
May 25 23:29:16 acsd: selected channel spec: 0xe29b (157/80)

There is no other 5 GHz around me so I don't understand what all the scanning is about.

After the above, the node backhaul was found at 2G and a client would not connect to 5G.

A router webUI reboot seems to have cleared the issue... for now.

This acsd scanning/logging issue is new to me with this build.

OE
 
Last edited:
This build seems to do/log this:

...

There is no other 5 GHz around me so I don't understand what all the scanning is about.

After the above, the node backhaul was found at 2G and a client would not connect to 5G.

A router webUI reboot seems to have cleared the issue... for now.

This acsd scanning is new to me with this build.

OE

A number of people are seeing this now. Seems to be something happening. I've had my channels manually set forever, so I've not experienced it. If you have no other 5 GHz neighbors, the easy solution is to set your channels manually (Ch 157 has the highest power from my testing of both UNI-1 and UNI-III on my AC86Us) because it appears to fix the connection issues. I know that manual channel selection doesn't fix the underlying auto channel mode problem, but probably nothing you can do about it, and manual channel selection is better in an isolated environment because some channels clearly transmit at higher power than others, at least for my US version routers. I think its also better because auto channel mode seems to channel hop for no good reason.
 
A number of people are seeing this now. Seems to be something happening. I've had my channels manually set forever, so I've not experienced it. If you have no other 5 GHz neighbors, the easy solution is to set your channels manually (Ch 157 has the highest power from my testing of both UNI-1 and UNI-III on my AC86Us) because it appears to fix the connection issues. I know that manual channel selection doesn't fix the underlying auto channel mode problem, but probably nothing you can do about it, and manual channel selection is better in an isolated environment because some channels clearly transmit at higher power than others, at least for my US version routers. I think its also better because auto channel mode seems to channel hop for no good reason.

Thanks for the feedback. If I disable Smart Connect to be able to manage/fix the channel selection, then I will likely want to switch to using separate SSIDs, yes?

I'm tempted because Auto WiFi settings are my least favorite feature of AiMesh/Smart Connect.

OE
 
I didn't realize that you are using AiMesh. Is it now possible to do manual channel selection with AiMesh now? I'm not running AiMesh. I use a separate SSID for my 2.4 GHz band that is only enabled on my main router, but both my AC86Us use the same SSID for the 5 GHz band.
 
I didn't realize that you are using AiMesh. Is it now possible to do manual channel selection with AiMesh now? I'm not running AiMesh. I use a separate SSID for my 2.4 GHz band that is only enabled on my main router, but both my AC86Us use the same SSID for the 5 GHz band.

I believe the choice is independent of using/not using AiMesh... if you select Dual-Band Smart Connect (node band steering), then wireless mode, channel bandwidth, control channel, and extension channel are adjusted automatically. If NOT using Smart Connect, then you would be wise to use separate SSIDs.

I've never used AiMesh without Smart Connect and with seaparate SSIDs... maybe this new issue with excessive scanning will require it... I would like to set channels and have them stick.

OE
 

And again this scanning issue persists:

Code:
Similar June 7, 8, 9 entries removed for brevity...
Jun  9 00:09:29 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:09:29 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:09:29 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:24:31 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:24:31 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:24:31 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:39:33 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:39:33 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:39:33 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:54:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:54:35 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:54:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:09:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:09:37 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 01:09:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:24:39 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 01:24:39 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 01:24:39 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 01:39:40 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:39:40 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 01:39:40 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:54:42 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:54:42 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 01:54:42 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:09:44 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:09:44 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:09:44 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:24:46 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:24:46 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:24:46 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:39:48 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:39:48 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:39:48 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:54:50 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:54:50 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:54:50 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:09:52 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:09:52 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 03:09:52 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:24:55 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:24:55 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 03:24:55 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:39:57 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:39:57 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 03:39:57 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:54:58 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 03:54:58 acsd: Adjusted channel spec: 0xe09b (149/80)
Jun  9 03:54:58 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 04:10:01 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:10:01 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 04:10:01 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:25:03 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 04:25:03 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 04:25:03 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 04:40:05 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:40:05 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 04:40:05 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:55:06 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 04:55:06 acsd: Adjusted channel spec: 0xe09b (149/80)
Jun  9 04:55:06 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 05:10:09 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 05:10:09 acsd: Adjusted channel spec: 0xe02a (36/80)
Jun  9 05:10:09 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 05:25:10 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:25:10 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 05:25:10 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:40:12 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:40:12 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 05:40:12 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:55:14 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 05:55:14 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 05:55:14 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 06:10:16 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:10:16 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 06:10:16 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:25:17 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:25:17 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 06:25:17 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:40:20 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 06:40:20 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 06:40:20 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 06:55:22 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:55:22 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 06:55:22 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:10:23 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:10:23 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 07:10:23 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:25:24 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:25:24 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 07:25:24 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:40:26 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 07:40:26 acsd: Adjusted channel spec: 0xe02a (36/80)
Jun  9 07:40:26 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 07:55:28 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 07:55:28 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 07:55:28 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 08:10:30 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 08:10:30 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 08:10:30 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 08:25:32 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 08:25:32 acsd: Adjusted channel spec: 0xe02a (36/80)
Jun  9 08:25:32 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 08:40:34 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 08:40:34 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 08:40:34 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 08:55:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 08:55:35 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 08:55:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:10:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:10:37 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 09:10:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:25:39 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:25:39 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 09:25:39 acsd: selected channel spec: 0xe19b (153/80)

This time I noticed a 5 GHz client not able to obtain an IP address, and again the AiMesh backhaul dropped to 2.4 GHz. WiFi Analyzer still showed the 5 GHz signal, so rather than suspect radio hardware, I suspect the firmware code that started this scanning business.

I disabled/enabled the 5 GHz radio and the above two symptoms cleared.

OE
 
And again this scanning issue persists:

Code:
Similar June 7, 8, 9 entries removed for brevity...
Jun  9 00:09:29 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:09:29 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:09:29 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:24:31 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:24:31 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:24:31 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:39:33 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:39:33 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:39:33 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:54:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 00:54:35 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 00:54:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:09:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:09:37 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 01:09:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:24:39 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 01:24:39 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 01:24:39 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 01:39:40 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:39:40 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 01:39:40 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:54:42 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 01:54:42 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 01:54:42 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:09:44 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:09:44 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:09:44 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:24:46 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:24:46 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:24:46 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:39:48 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:39:48 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:39:48 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:54:50 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 02:54:50 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 02:54:50 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:09:52 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:09:52 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 03:09:52 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:24:55 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:24:55 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 03:24:55 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:39:57 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:39:57 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 03:39:57 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 03:54:58 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 03:54:58 acsd: Adjusted channel spec: 0xe09b (149/80)
Jun  9 03:54:58 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 04:10:01 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:10:01 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 04:10:01 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:25:03 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 04:25:03 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 04:25:03 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 04:40:05 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:40:05 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 04:40:05 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 04:55:06 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 04:55:06 acsd: Adjusted channel spec: 0xe09b (149/80)
Jun  9 04:55:06 acsd: selected channel spec: 0xe09b (149/80)
Jun  9 05:10:09 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 05:10:09 acsd: Adjusted channel spec: 0xe02a (36/80)
Jun  9 05:10:09 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 05:25:10 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:25:10 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 05:25:10 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:40:12 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:40:12 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 05:40:12 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 05:55:14 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 05:55:14 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 05:55:14 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 06:10:16 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:10:16 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 06:10:16 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:25:17 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:25:17 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 06:25:17 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:40:20 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 06:40:20 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 06:40:20 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 06:55:22 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 06:55:22 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 06:55:22 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:10:23 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:10:23 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 07:10:23 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:25:24 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:25:24 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 07:25:24 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 07:40:26 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 07:40:26 acsd: Adjusted channel spec: 0xe02a (36/80)
Jun  9 07:40:26 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 07:55:28 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 07:55:28 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 07:55:28 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 08:10:30 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 08:10:30 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 08:10:30 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 08:25:32 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 08:25:32 acsd: Adjusted channel spec: 0xe02a (36/80)
Jun  9 08:25:32 acsd: selected channel spec: 0xe02a (36/80)
Jun  9 08:40:34 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 08:40:34 acsd: Adjusted channel spec: 0xe29b (157/80)
Jun  9 08:40:34 acsd: selected channel spec: 0xe29b (157/80)
Jun  9 08:55:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 08:55:35 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 08:55:35 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:10:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:10:37 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 09:10:37 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:25:39 acsd: selected channel spec: 0xe19b (153/80)
Jun  9 09:25:39 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun  9 09:25:39 acsd: selected channel spec: 0xe19b (153/80)

This time I noticed a 5 GHz client not able to obtain an IP address, and again the AiMesh backhaul dropped to 2.4 GHz. WiFi Analyzer still showed the 5 GHz signal, so rather than suspect radio hardware, I suspect the firmware code that started this scanning business.

I disabled/enabled the 5 GHz radio and the above two symptoms cleared.

OE

I've disabled Smart Connect to manage the basic wireless settings myself with separate SSIDs. I'll see if that stops the scanning.

OE
 
I've disabled Smart Connect to manage the basic wireless settings myself with separate SSIDs. I'll see if that stops the scanning.

OE

24 hours without Smart Connect enabled seems to have eliminated the rampant scanning like this:

Code:
Jun 10 18:07:51 acsd: selected channel spec: 0xe19b (153/80)
Jun 10 18:07:51 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun 10 18:07:51 acsd: selected channel spec: 0xe19b (153/80)

Now the log is simply this today:

Code:
Jun 11 16:55:36 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -72dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -80dbm)
Jun 11 16:55:36 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:55:46 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -72dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -84dbm)
Jun 11 16:55:46 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:55:56 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -72dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -84dbm)
Jun 11 16:55:56 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:56:06 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -62dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -84dbm)
Jun 11 16:56:06 roamast: eth6: disconnect weak signal strength station [64:bc:0c:66:87:13]
Jun 11 16:56:06 roamast: eth6: remove client [64:bc:0c:66:87:13] from monitor list
Jun 11 16:58:16 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -70dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -83dbm)
Jun 11 16:58:16 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:58:21 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -70dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -83dbm)
Jun 11 16:58:21 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:58:31 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -70dbm) for

OE
 
I just bought ac rt86u it works really well but im trying to keep track of my router is having 360mb of ram in use all the time a normal thing ? Also i had the same spam in log as the person above me thats why i got interesed and after disabling Smart Connect it seems that it stopped.

Also if i want the most stable realase so that i set it up and forget that router exists should i use stock or merlin firmware?
 
I just bought ac rt86u it works really well but im trying to keep track of my router is having 360mb of ram in use all the time a normal thing ? Also i had the same spam in log as the person above me thats why i got interesed and after disabling Smart Connect it seems that it stopped.

Also if i want the most stable realase so that i set it up and forget that router exists should i use stock or merlin firmware?
Just go with latest Merlin firmware. I am using the same with all the available scripts and the uptime is solid 18 days without any issues.
 
Would be nice to hear from @RMerlin about stock vs his latest realase when it comes to stability for years.
 
For me this is the best firmware so far. No issues at all for me.

30 days 12 hours 14 minute(s) 3 seconds
 
thanks for confirming the same behavior...anybody else?

this is frustrating...this is the most money I've ever spent on router(s)...i bought 2 of these AC86U routers as a mesh setup thinking this was finally THE setup to fix all my dead spots and be future-proof
I have the same issues, dead router, three lights on reboot. Contacted ASUS, no response yet. Only firmware 32799 is stable for me. Waiting.
 
after upgrading to this firmware, I tried resetting to factory settings...then as I would make all my configurations and then reboot, the router would eventually hang and I'd end up with "3 lights on" (power, and two wifi lights)...the same thing happened with two different 86u's....right now, I'm trying to guess which settings lead to this problem...possibilities:
-turning on the dOS protection under Firewall
-turning on ipv6
-turning on traffic monitor
-turning on parental settings

any thoughts? both routers worked smoothly the last several months and I never experienced any issues like this until installing this firmware...curious if others are experiencing this...I've read about a "boot loop" or something but I'm not sure if this is what I'm seeing.

Same issues, I had to firmware restore back to FW_RT_AC86U_300438432799 to get a stable router.
 
Download Master still doesn't work for me.
I'm constantly getting error of ERR_CONNECTION_REFUSED, or when i can enter it just takes too long.
 
24 hours without Smart Connect enabled seems to have eliminated the rampant scanning like this:

Code:
Jun 10 18:07:51 acsd: selected channel spec: 0xe19b (153/80)
Jun 10 18:07:51 acsd: Adjusted channel spec: 0xe19b (153/80)
Jun 10 18:07:51 acsd: selected channel spec: 0xe19b (153/80)

Now the log is simply this today:

Code:
Jun 11 16:55:36 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -72dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -80dbm)
Jun 11 16:55:36 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:55:46 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -72dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -84dbm)
Jun 11 16:55:46 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:55:56 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -72dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -84dbm)
Jun 11 16:55:56 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:56:06 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -62dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -84dbm)
Jun 11 16:56:06 roamast: eth6: disconnect weak signal strength station [64:bc:0c:66:87:13]
Jun 11 16:56:06 roamast: eth6: remove client [64:bc:0c:66:87:13] from monitor list
Jun 11 16:58:16 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -70dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -83dbm)
Jun 11 16:58:16 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:58:21 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -70dbm) for weak signal strength client [64:BC:0C:66:87:13](rssi: -83dbm)
Jun 11 16:58:21 roamast: roaming reject!!! candidate rssi over threshold(-70dbm)
Jun 11 16:58:31 roamast: discover candidate node [2C:FD:A1:A1:90:78](rssi: -70dbm) for

OE

An update on this issue... I returned to using Smart Connect and same SSIDs... roaming is better with this. So far, no weird/excessive acsd scanning in the log. This reversion entailed removing/resetting my node and configuring it to be the router... how it's done when using identical routers! Also, I have disabled AiProtection since it once again stopped doing anything. :rolleyes: And, I have not reconnected a USB 3.0 HDD... which has me wondering if USB 3.0 interference with WiFi caused the router to scan excessively for another channel... edit: probably not since the drive was not in use, just idly spinning.

OE
 
Last edited:
An update on this issue... I returned to using Smart Connect and same SSIDs... roaming is better with this. So far, no weird/excessive acsd scanning in the log. This reversion entailed removing/resetting my node and configuring it to be the router... how it's done when using identical routers! Also, I have disabled AiProtection since it once again stopped doing anything. :rolleyes: And, I have not reconnected a USB 3.0 HDD... which has me wondering if USB 3.0 interference with WiFi caused the router to scan excessively for another channel... edit: probably not since the drive was not in use, just idly spinning.

OE

Having tried 81039, I'm back to 45717 and no Smart Connect to stop the endless channel scanning/changes.

OE
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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