RT-AC86U 2.4Ghz is gone

[thedarkness]

Hi,
Out of the blue, the 2.4 Ghz network on my AC86U is dead.

I can't be found by ANY device.

The router thinks is active, but it is definitely not. It's not hidden.
I tried:
- Rebotting
- Toggling Smart Connect (I don't use it)
- Toggle WiFi from the Android app
- Change WiFi name or Password

5Ghz works just fine.
Running 386.2_6

Syslog is spammed by this event which goes on and on.
Any clues?

Jul  9 14:02:26 roamast: ROAMING Start...
Jul  9 14:02:30 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:30 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:30 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:31 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:31 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:31 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:31 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:32 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:57 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:57 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:58 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:58 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:58 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:59 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:59 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:02:59 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:15 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:15 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:16 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:16 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:16 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:17 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:17 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:17 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:34 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:35 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:35 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:35 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:35 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:35 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:36 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:36 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:37 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:45 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:46 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:46 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:46 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:47 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:47 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:47 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:03:47 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:11 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:11 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:12 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:12 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:12 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:13 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:13 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:13 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:44 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:44 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:44 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:45 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:45 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:45 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:46 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:04:46 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:15 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:15 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:16 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:16 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:16 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:17 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:17 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:17 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:05:26 wlceventd: wlceventd_proc_event(527): eth5: Auth 50:EC:50:03:52:74, status: Successful (0), rssi:0
Jul  9 14:05:27 wlceventd: wlceventd_proc_event(527): eth5: Auth 50:EC:50:03:52:74, status: Successful (0), rssi:0
Jul  9 14:05:27 wlceventd: wlceventd_proc_event(527): eth5: Auth 50:EC:50:03:52:74, status: Successful (0), rssi:0
Jul  9 14:05:27 wlceventd: wlceventd_proc_event(527): eth5: Auth 50:EC:50:03:52:74, status: Successful (0), rssi:0
Jul  9 14:05:27 wlceventd: wlceventd_proc_event(527): eth5: Auth 50:EC:50:03:52:74, status: Successful (0), rssi:0
Jul  9 14:05:28 wlceventd: wlceventd_proc_event(527): eth5: Auth 50:EC:50:03:52:74, status: Successful (0), rssi:0
Jul  9 14:05:57 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0
Jul  9 14:07:21 wlceventd: wlceventd_proc_event(527): eth5: Auth 48:E1:E9:27:C2:5D, status: Successful (0), rssi:0

 

[L&LD]

Physically unplug the router (both from the wall plug and from the plug that goes into the router) for a few minutes leaving the power button 'on'.

What firmware is installed on the router? What firmware or configuration changes have you made to the router or your network recently (or, 'most recently')?

 

[thedarkness]

Physically unplug the router (both from the wall plug and from the plug that goes into the router) for a few minutes leaving the power button 'on'.

What firmware is installed on the router? What firmware or configuration changes have you made to the router or your network recently (or, 'most recently')?

I've kept it off for 5 minutes and upon reboot it worked. Thank you, but what kind of wizardry is this? Or should I say unstablity?
I had other WiFi issues in the past with this router, but nothing that could be solved with a good reboot.

I'm running Merlin 386.2_6.
The last change I've done was two weeks ago, where I added a DHCP reservation for my new Raspberry Pi 4.

Nothing since then, I don't change stuff unless I do need.

 

[sl4fko]

I've kept it off for 5 minutes and upon reboot it worked. Thank you, but what kind of wizardry is this? Or should I say unstablity?
I had other WiFi issues in the past with this router, but nothing that could be solved with a good reboot.

I'm running Merlin 386.2_6.
The last change I've done was two weeks ago, where I added a DHCP reservation for my new Raspberry Pi 4.

Nothing since then, I don't change stuff unless I do need.

Not wizardry, it's L&LD knowledge!


Thanks also to him, ASUS world is a better place...

 

[L&LD]

No wizardry on my part. Just memory (that works on demand, sometimes!) from all the posts I read here (I read them all).

You may want to invest in a more potent power supply for your RT-AC86U (same voltage, more amps - it will use only what's needed, but what shipped with the router has been hinted that it is not optimally matched to the hardware inside). I think 19V @ 3.42A is what is 'recommended' by others on these forums.

 

[routerq]

check the status tab for the 2.4g MAC... if the MAC id is missing, the 2.4G radio may about to go kaput... i have a5300 and I can see MAC for 2.4g and lower channel 5g radio. the 2nd 5G radio is dead.... and no MAC id visible on the page ...

 

[Xboxsx4life]

Hi everyone. I purchased an AC86U and just set it up last night. Running the latest stock Asus firmware. I’m coming from an AC68U. First thing I noticed is that the 2.4GHz range seems to be worse than my 68U router. In fact, my 5GHz signal on this new router is always stronger than my 2.4GHz signal (tested using a wifi analyzer) all over my house while indoors. The only time 2.4 is stronger than 5 is when I’m outside.

Also, my Ring Doorbell (which only supports 2.4) has already randomly disconnected twice and I’ve been using this router for less than 24 hours. I never had this problem with my old 68U router. The doorbell’s RSSI measures -54db. With my 68U, it was always around -44db to -46db…a full 10db stronger.

The 86U has a manufacturer date of 2020. Does anyone know if Asus fixed the dreaded 2.4GHz radio problem on this device with these latest 2020 builds? I was hoping that with a 2020 model they did, but in my limited testing so far, it would appear that the problem persists. I’m thinking of returning it and just sticking to my 68U for now.

Thoughts?

 

[Tech9]

I’m thinking of returning it and just sticking to my 68U for now.

I would send it back and use the trusted AC68U. Too many potential issues with AC86U routers.

Router temperatures

yes, and even the slightest bit helps. I had wired a 120mm 12v fan to a usb plug and taped it on my 86U and got 66C temperatures. This last time, I just set it standing on its edge about 4 to 5 inches away, not "pointed" at the chip, just towards the router, and that got me the same 66C temps...

www.snbforums.com

 

[Xboxsx4life]

Thanks for the quick reply. That’s most likely what I’ll do. Any thoughts on getting an AX86U instead? I don’t have any WiFi6 devices so I would run the router in AC mode. I know that’s sort of waste of money at this point but I like the idea of having a quad core router with lots of RAM. Not that I’m doing any intensive networking tasks but still

Does anyone know if the AX86U is more reliable than the AC86U and if Asus finally fixed the 2.4GHz problem?

 

[Tech9]

Any thoughts on getting an AX86U instead?

It's a good router, perhaps the best price/performance Asus offer so far. If you currently can't use the extra performance, the upgrade is going to be a waste of money indeed. You can always upgrade when you need the extra performance and for less. When AC86U was introduced to the market the price was over $250, now it's often on sale for $150. The same is expected to happen to current AX models when AXE routers hit the market. If you really want to play with AX86U now and you have the money - go for it.

 

[Xboxsx4life]

Thanks again!

 

[Xboxsx4life]

Here's an update. I fiddled around with some of the Professional wireless settings. I changed the modulation mode to 802.11n for the 2.4GHz network and 802.11ac for the 5GHz network (basically disabled Turbo/Nitro QAM under both networks). I also disabled Airtime Fairness and Universal beamforming under both networks. The 2.4GHz signal now seems more stable and appears to be better with its range. I'll continue to keep an eye on this for a few more days/weeks before I decide to return it.

 

[Tech9]

For maximum compatibility I would keep disabled:

- Protected Management Frames (in Wireless, General)
- Roaming assistant
- IGMP Snooping
- TX Bursting
- WMM APSD
- Turbo/NitroQAM
- Airtime Fairness
- MU-MIMO
- Explicit Beamforming
- Universal Beamforming

 

[Xboxsx4life]

Thanks. These are already disabled:

Protected Management Frames
Roaming Assistant
IGMP Snooping
Turbo/NitroQAM
Airtime Fairness
Universal Beamforming

These others (below) are still enabled. Do you know what they do and what the impact would be if leaving them enabled? Would any performance be lost if disabling them? And should they be disabled on both 2.4 and 5GHz networks? P.S. I don’t use band steering. I have separate SSIDs for 2.4 and 5GHz networks. Only two devices (doorbell and thermostat) are connected to 2.4. All other wireless devices connect to my 5GHz network.

These are still enabled:

TX Bursting
WMM APSD
MU-MIMO
Explicit Beamforming

I know Explicit Beamforming is only for 2.4GHz and my only two devices using that network probably don’t support explicit beamforming so I can turn that off. MU-MIMO seems beneficial though. Not sure what the other items do.

 

[Tech9]

TX Bursting - only for 802.11g clients and not supported by many even years ago
WMM APSD - automatic power save delivery - most devices manage PS on their own
MU-MIMO - not applicable to 2.4GHz 802.11n, no device supports it
Explicit Beamforming - non-standard attempt for beamforming without client response/support, may cause stability issues

 

[Xboxsx4life]

OK thanks for that. I thought explicit beamforming DOES require client response/support whereas universal beamforming does not?

 

[Tech9]

I thought explicit beamforming DOES require client response/support whereas universal beamforming does not?

Yes, my mistake. The above is about Universal Beamforming. The problem is no 802.11n client actually supports Explicit Beamforming. The idea was implemented in 802.11ac as part of specifications, on 5GHz band. I don’t know why Asus has it in 2.4GHz settings. It does nothing.

 

[Xboxsx4life]

Ah OK, got it. I’ve now disabled everything you’ve suggested. Thanks again. So far so good. Also, my AC86U is quite cool to the touch (temperature wise)…it actually runs cooler than my old AC68U. Do you think these 2020 versions were built differently (better)?

 

[Tech9]

Do you think these 2020 versions were built differently (better)?

I don't know. This is how to get CPU temp in Asuswrt:

http://router.asus.com/ajax_coretmp.asp

(login to your router first and click the link above, otherwise it will bring you to the login screen only)

 

[Xboxsx4life]

Done. It said 77.289. When I reloaded the link, it dropped to 76.798.