What's new

Asus AC86U 5ghz switched to channel 0, all clients dropped, everything else working fine.

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

punchsuckr

Senior Member
Hi!,

I recently got an Ac86u after years with the n66u on john's fork. Updated to the merkin firmware 384.18 about 10 days ago.

I have a vpn server setup which is rock solid with very little overhead and excellent throughput. It was working just fine for about 6 days when today all 5ghz clients disconnected when I just woke my laptop from standby.

All lights were on, and vpn was working just fine but the wireless symbol showed up as half and displayed channel 0 for 5ghz.

I have seen one exact same issue reported around 2 years ago but was apparently due to the user migrating settings or something which I haven't done. The router was setup as new and I had updated to merlin fw from stock upon first boot before I configured it.

Some settings I have changed from default:

5ghz is set to use channel 36 with other settings (some of my clients don't see the channels in the high 100+mhz range) on auto.
Smart connect is off. I only use the 5ghz band with no clients on 2.4 (it is a different ssid).
WPS is disabled for security.
Adaptive qos is on, aiprotection is on.

I saw the following messages in the log when this occurred. This goes on for many more lines.
Code:
21:06:45 wlceventd: WLCEVENTD wlceventd_proc_event(500): eth6: Auth 58:00:**:**:5A:BD, status: Successful (0)
Aug  9 21:06:45 wlceventd: WLCEVENTD wlceventd_proc_event(529): eth6: Assoc 58:00:**:**:5A:BD, status: Successful (0)
Aug  9 21:06:47 kernel: DUMP CONSOLE: xstrt 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 574816.584 ampdu_dbg: cwcur0-3 f f 7 3 bslots cur/0-3 15 0 0 0 0 ifs_boff 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 574816.584 ampdu_dbg: again1 ifsstat 0xaf nav_stat 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 574816.584 ampdu_dbg: again2 ifsstat 0xaf nav_stat 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: wl1.0 50:3e:aa:49:75:69 scb:00333a58 tid:4
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: wl1.0 dead_cnt 2 tx_in_transit 1 psm_mux 0xfff0 aqmqmap 0x0x404 aqmfifo_status 0x0x4000 fifordy 0x0 cpbusy 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: ifsstat 0xaf nav_stat 0x0 txop 108007
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: pktpend: 0 0 0 0 0 ap 1
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: txall 52 txbcn 0 txrts 0 rxcts 0 rsptmout 0 rxstrt 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: cwcur0-3 f f 7 3 bslots cur/0-3 2 0 0 0 0 ifs_boff 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: again1 ifsstat 0xaf nav_stat 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 ampdu_dbg: again2 ifsstat 0xaf nav_stat 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 wl1: wlc_ampdu_watchdog: cleaning up ini tid 4 due to no progress for 2 secs tx_in_transit 1
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575362.584 wl1: wlc_ampdu_tx_send_delba: tid 4 initiator 1 reason 39
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575384.584 wl1.0: wlc_send_bar: seq 0x996 tid 4
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575805.666 flow_create : bitmap_size=512  maxitems=2048
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575805.669 wl1.0: wlc_send_bar: seq 0x1 tid 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575805.674 wl1: wlc_rrm_recv_nrreq: Unsupported
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575805.953 flow_create : bitmap_size=512  maxitems=512
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575805.954 wl1.0: wlc_send_bar: seq 0x1 tid 6
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575806.943 wl1: wlc_ampdu_tx_recv_delba: AMPDU OFF: tid 0 initiator 0 reason 1
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575807.050 wl1.0: wlc_send_bar: seq 0xa tid 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 575807.174 wl1.0: wlc_send_bar: seq 0x1 tid 3
Aug  9 21:06:47 kernel: DUMP CONSOLE: 576120.612 flow_create : bitmap_size=512  maxitems=1024
Aug  9 21:06:47 kernel: DUMP CONSOLE: 576120.613 wl1.0: wlc_send_bar: seq 0x3 tid 4
Aug  9 21:06:47 kernel: DUMP CONSOLE: 576639.285 wl1.0: wlc_send_bar: seq 0xd09 tid 4
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: wl1.0 50:3e:aa:49:75:69 scb:00333a58 tid:2
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: wl1.0 dead_cnt 2 tx_in_transit 1 psm_mux 0xfff0 aqmqmap 0x0xb01 aqmfifo_status 0x0x4000 fifordy 0x0 cpbusy 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: ifsstat 0xaf nav_stat 0x0 txop 105203
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: pktpend: 0 0 0 0 0 ap 1
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: txall 114 txbcn 0 txrts 0 rxcts 0 rsptmout 0 rxstrt 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: cwcur0-3 f f 7 3 bslots cur/0-3 0 0 0 0 0 ifs_boff 0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: again1 ifsstat 0xaf nav_stat 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 ampdu_dbg: again2 ifsstat 0xaf nav_stat 0x0
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 wl1: wlc_ampdu_watchdog: cleaning up ini tid 2 due to no progress for 2 secs tx_in_transit 1
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577125.584 wl1: wlc_ampdu_tx_send_delba: tid 2 initiator 1 reason 39
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577127.803 wl1.0: wlc_send_bar: seq 0x1b5 tid 2
Aug  9 21:06:47 kernel: DUMP CONSOLE: 577538.311 wl1.0: wlc_send_bar: seq 0x4 tid 5
Aug  9 21:06:47 kernel: DUMP CONSOLE: 578239.787 flow_create : bitmap_size=512  maxitems=1024
Aug  9 21:06:47 kernel: DUMP CONSOLE: 578239.834 wl1.0: wlc_send_bar: seq 0x1 tid 2
Aug  9 21:06:47 kernel: DUMP CONSOLE: 578443.440 wl1: Proxy STA 58:00:**:**:5a:bd link is already gone !!??
Aug  9 21:06:47 kernel: DUMP CONSOLE: 578443.440 wl1: STA 58:00:**:**:5a:bd removed from MU client set.
Aug  9 21:06:47 kernel: DUMP CONSOLE: 578443.500 wl1: wlc_recvfilter: scb is null, dont resend deauth
Aug  9 21:06:47 kernel: DUMP CONSOLE: 578443.584 wl1: STA 1c:12:b0:77:88:8c removed from MU client set.
Aug  9 21:06:47 kernel: DUMP CONSOLE: 578443.585 wlc_ucode_download: wl1: Loading non-MU ucode
...
Censored MAC of my laptop because I do not know. :)

Any help is deeply appreciated. Hoping this is not a hardware issue.

Thank you.
 
You need to do a full reset to factory defaults after flashing to RMerlin firmware. :)



I would also skip 384.18_0 and flash the 384.19 Beta 1 instead (there is a reason for the RT-AC86U).

 
I thought I did not need to since it was flashed it before I configured anything. :|
I guess I will do it on Friday.
 
 
Hopefully the AC86 was a new one and not a unit manufactured in 2018.

You should do a nuclear reset now as outlined by L&LD with no shortcuts. If you still have problems with the 5 Ghz radio showing channel 0 after following this procedure return your router.

The channel 0 issue was a common failure for those routers manufactured in 2018 that had hardware issues.
 
Hopefully the AC86 was a new one and not a unit manufactured in 2018.

You should do a nuclear reset now as outlined by L&LD with no shortcuts. If you still have problems with the 5 Ghz radio showing channel 0 after following this procedure return your router.

The channel 0 issue was a common failure for those routers manufactured in 2018 that had hardware issues.
Thanks for your reply. The router was apparently manufactured last month itself so hopefully it wasn’t that issue.

I have reset it completely. It has gotten rid of some errors in the log as well as an “initialinsing” vpn server message on the openvpn server being displayed continuously even with it up and running and accepting connections.

Fingers crossed.
 
The channel 0 issue was a common failure for those routers manufactured in 2018 that had hardware issues.

There are reports of failing radios even in routers from 2019-2020, unfortunately. I really hope Asus fixed something because RT-AC86U is an excellent router when it works. Some say the units made in Vietnam are better.
 
If anybody encounters this thread... the issue is seemingly fixed on stock 82072 with auto channel selection on both bands. It has been 2 weeks of it running without issues.
Cannot attest to how long it stays that way and whether it is indeed fixed, but previous run ins with the issue were at 4 and 6 days.
The issue was showing up with a manually selected channel 36 or 40 with both stock and merlin.
 

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