- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2024 10:35 AM - edited 12-10-2024 10:37 AM
I've had the RT-BE92U for a few weeks now and a couple of times a day it simply stops routing DNS WAN traffic and the Wi-Fi networks also stop routing. All Internet access grinds to a halt because of this. Sometimes it returns to normal on its own but today it was so inconvenient that I got it to reboot via the web UI. It's then fine again for several hours.
It's like the unit itself enters some kind of semi-hung/crashed state. I'm thinking there's some kind of memory leak or that the RAM capacity is insufficient. It runs for several hours and then begins going faulty.
I am 26 years into an advanced IT solutions architecture/engineering career covering pretty much all kinds of infrastructure. So, the most I'm guilty of is not trying the basics.
I am able to ping externally, however I tend to find that I cannot get DNS traffic to pass and that includes direct queries of external DNS services, e.g. 8.8.8.8 (I can ping this guy).
The Wi-Fi networks can't even reach the router itself. I have to go to my wired laptop to engage with the router. The router web UI responds normally. The system log just seems to show either long pauses between log entries or errors about wireless client disconnects.
This kind of error seems to be common in the log just now:
kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
kernel: WLC_SCB_DEAUTHORIZE error (-30)
Could be red herrings but they always seem to be around when the crashes happen.
I have a lot of smart devices. It says I have a total of 54 clients but the vast majority of those will generate very little traffic.
I use Sky Stream. So, there can be a lot of throughput there. I also watch a lot of Twitch. Again a lot of data passing through for that. Nothing I wouldn't expect this router to handle though.
I have AiMesh up and running with two nodes.
I use the Time Machine backup capability with a USB drive attached. There's an hourly backup.
I have the AiProtection turned on. DoS protection enabled.
I also have the DNS over TLS enabled opportunistically but I've tried putting this off and it doesn't help.
I just fear that the hardware spec isn't able to handle the workload.
It just seems like the firmware isn't stable enough yet. I need to decide if I should be returning this or just be patient and wake for the next firmware updates.
Anyone else with this router experiencing issues despite factory resetting?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2025 06:57 AM
This forum format is not very great, dont know who reply to who and all out of order. I just reply to All that message me here.
yes, I did submit a report to ASUS.
Their engineer have sent me Beta firmware 37803 . Anyone that interested I can share the link here.
Now I have it update for more than a day, here is the new founding. Core usage seen normal now with couple time that multi core stuck at 100 not moving. I just ignore them and they go away.
As for Wifi reboot, that might happened couple time. I still have my old AC-3100 running. I knew because it switched over to the other network.
Ram at 730mb with everything on.
Temp error is back
While my RT-AC3100 can run all the same software with only 2 core hardly go over 50% and 171/512mb Ram with All my wifi thing connected to it. And only 1 client connected to BE92U with 4 times the processing power. But I do have Asuswrt-Merlin firmware on my 3100. Hope they release one for the 92U soon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-10-2025 05:21 AM
Hi, would you share 37803 firmware for us to test?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-07-2025 07:10 AM
I have been struggling to reply here as the site just wouldn't let me. Clicking reply has done nothing for several days.
I am on 37748 and this is my log for 60 secs. It does this all day! They have emailed me 37803 but I just get the impression ASUS are guessing and don't seem to do any testing of their own. On 37748 I don't have thermal errors, the cores aren't bouncing but my wifi and ethernet will drop without warning and I have had to disable several options I wanted to use. IoT, guest wifi and no SDD over USB.
Feb 7 14:59:03 kernel: wlc_rrm_process_rep: response count == 0
Feb 7 14:59:03 kernel: wlc_rrm_parse_response: type: REFUSED
Feb 7 14:59:04 kernel: wlc_rrm_recv_bcnrep: channel :100, duration: 150, frame info: 4, rcpi: 56, rsni: 50, bssid b0:6e:bf:e1:fd:94,
Feb 7 14:59:04 kernel: antenna id: 1, parent tsf: 987604074, fragment num 0
Feb 7 14:59:04 kernel: wlc_rrm_recv_bcnrep: channel :100, duration: 150, frame info: 4, rcpi: 80, rsni: 58, bssid 92:7c:61:ef:4c:25,
Feb 7 14:59:04 kernel: antenna id: 1, parent tsf: 987609803, fragment num 0
Feb 7 14:59:04 kernel: wlc_rrm_recv_bcnrep: channel :100, duration: 150, frame info: 4, rcpi: 40, rsni: 34, bssid f0:2f:74:ee:3e:7e,
Feb 7 14:59:04 kernel: antenna id: 1, parent tsf: 987651156, fragment num 0
Feb 7 14:59:15 kernel: wlc_rrm_recv_bcnrep: channel :100, duration: 150, frame info: 4, rcpi: 74, rsni: 66, bssid b0:6e:bf:e1:fd:94,
Feb 7 14:59:15 kernel: antenna id: 1, parent tsf: 998048927, fragment num 0
Feb 7 14:59:15 kernel: wlc_rrm_recv_bcnrep: channel :100, duration: 150, frame info: 4, rcpi: 80, rsni: 56, bssid 92:7c:61:ef:4c:25,
Feb 7 14:59:15 kernel: antenna id: 1, parent tsf: 998054613, fragment num 0
Feb 7 14:59:15 kernel: wlc_rrm_recv_bcnrep: channel :100, duration: 150, frame info: 4, rcpi: 48, rsni: 38, bssid f0:2f:74:ee:3e:7e,
Feb 7 14:59:15 kernel: antenna id: 1, parent tsf: 998095971, fragment num 0
Feb 7 14:59:23 kernel: wl1.1: 5a:40:4d:3f:5a:1e wlc_apps_ps_timedout: 1 packets timed out
Feb 7 14:59:23 kernel: PS:on listen:2 inPS:12031ms in_pvb:1(7302ms)
Feb 7 14:59:23 kernel: ps_trans_status:0x0 ps_requester:0x1 ps_txfifo_blk:0
Feb 7 14:59:23 kernel: tx_block:0 ext_qos_null:0 psp_onresp:0 psp_pending:0 pspoll_pkt_waiting:0
Feb 7 14:59:23 kernel: prio[7]: psq:0 supr_psq:0 bytes:101
Feb 7 14:59:23 kernel: AID:35
Feb 7 14:59:23 kernel: PVB offset:4 bcmc_bytes:0 length:1 08
Feb 7 14:59:32 roamast: [EXAP]Deauth old sta in 1 1: 46:21:9A:1B:0F:38
Feb 7 14:59:32 roamast: wl1.1: disconnect weak signal strength station [46:21:9a:1b:0f:38]
Feb 7 14:59:32 kernel: iov:SCB_DEAUTHENTICATE_FOR_REASON 46:21:9a:1b:0f:38
Feb 7 14:59:32 kernel: wl1.1: wlc_send_deauth: send deauth for 46:21:9a:1b:0f:38 with reason 2
Feb 7 14:59:32 kernel: wl1.1: wlc_senddeauth_ex: station 46:21:9a:1b:0f:38 has been notified of deauthentication
Feb 7 14:59:32 kernel: wl1: wlc_scb_set_auth: 46:21:9a:1b:0f:38: deauthenticated
Feb 7 14:59:32 kernel: iov:SCB_DEAUTHENTICATE_FOR_REASON 46:21:9a:1b:0f:38
Feb 7 14:59:32 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Feb 7 14:59:32 kernel: iov:SCB_DEAUTHENTICATE_FOR_REASON 46:21:9a:1b:0f:38
Feb 7 14:59:32 roamast: wl1.1: remove client [46:21:9a:1b:0f:38] from monitor list
Feb 7 14:59:35 kernel: 5A:40:4D:3F:5A:1E not mesh client, can't delete it
Feb 7 14:59:35 kernel: wl1.1: 5a:40:4d:3f:5a:1e wlc_apps_ps_timedout: 1 packets timed out
Feb 7 14:59:35 kernel: PS:on listen:2 inPS:24383ms in_pvb:1(19654ms)
Feb 7 14:59:35 kernel: ps_trans_status:0x0 ps_requester:0x1 ps_txfifo_blk:0
Feb 7 14:59:35 kernel: tx_block:0 ext_qos_null:0 psp_onresp:0 psp_pending:0 pspoll_pkt_waiting:0
Feb 7 14:59:35 kernel: prio[0]: psq:0 supr_psq:0 bytes:50
Feb 7 14:59:35 kernel: AID:35
Feb 7 14:59:35 kernel: PVB offset:2 bcmc_bytes:0 length:3 001008
Feb 7 14:59:35 kernel: wl1.1: wlc_deauth_sendcomplete: no ACK from 46:21:9a:1b:0f:38 for Deauth (txs suppr: 0x0)
Feb 7 14:59:35 kernel: wl1.1: 46:21:9a:1b:0f:38 wlc_apps_ps_timedout: 1 packets timed out
Feb 7 14:59:35 kernel: PS:off
Feb 7 14:59:35 kernel: prio[7]: psq:0 supr_psq:0 bytes:78
Feb 7 14:59:35 kernel: AID:28
Feb 7 14:59:35 kernel: PVB offset:2 bcmc_bytes:0 length:3 001008
Feb 7 14:59:35 kernel: wl1.1: wlc_scb_clearstatebit: 46:21:9a:1b:0f:38: clear bits 0x13 [ AUTHENTICATED ASSOCIATED AUTHORIZED ]
Feb 7 14:59:35 kernel: wl1.1: wlc_scb_clearstatebit: 46:21:9a:1b:0f:38: oldstate = 0x13, scb->state = 0x00 [ ]
Feb 7 14:59:35 kernel: wl1 taf_retrig_check: timer late ! (zw) expected 0us, actual 17156us, delay 17156us, perf mode
Feb 7 14:59:35 kernel: wl1: STA 46:21:9a:1b:0f:38 has disassociated tx_type 17
Feb 7 14:59:35 kernel: wl1.1: wlc_ap_scb_unusable_stas_timeout Timeout Free scb:46:21:9a:1b:0f:38
Feb 7 14:59:35 kernel: wlc_ap_aid_free releasing bit = 28 for bsscfg 1 in AIDMAP
Feb 7 14:59:35 kernel: wl1.1: wlc_scb_clearstatebit: 46:21:9a:1b:0f:38: clear bits 0xff [ AUTHENTICATED ASSOCIATED PENDING_AUTH PENDING_ASSOC AUTHORIZED SAE_AUTH_CF ]
Feb 7 14:59:35 kernel: wl1.1: wlc_scb_clearstatebit: 46:21:9a:1b:0f:38: oldstate = 0x00, scb->state = 0x00 [ ]
Feb 7 14:59:35 kernel: wl1: notify system/blog disconnection event.
Feb 7 14:59:35 kernel: wl_handle_blog_event: mark as DIS-associated. addr=46:21:9a:1b:0f:38
Feb 7 14:59:35 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 46:21:9A:1B:0F:38, status: 0, reason: Previous authentication no longer valid (2), rssi:0
Feb 7 14:59:35 kernel: wl1: wlc_iovar_ext: sta_info: BCME -21
Feb 7 14:59:40 kernel: wl1.1: 5a:40:4d:3f:5a:1e wlc_apps_ps_timedout: 1 packets timed out
Feb 7 14:59:40 kernel: PS:on listen:2 inPS:28607ms in_pvb:1(23878ms)
Feb 7 14:59:40 kernel: ps_trans_status:0x0 ps_requester:0x1 ps_txfifo_blk:0
Feb 7 14:59:40 kernel: tx_block:0 ext_qos_null:0 psp_onresp:0 psp_pending:0 pspoll_pkt_waiting:0
Feb 7 14:59:40 kernel: prio[0]: psq:0 supr_psq:0 bytes:50
Feb 7 14:59:40 kernel: AID:35
Feb 7 14:59:40 kernel: PVB offset:4 bcmc_bytes:0 length:1 08
Feb 7 14:59:44 kernel: wl1: wlc_ap_sta_probe_complete: no ACK from 5a:40:4d:3f:5a:1e for Null Data, txstatus 0x0000, PS 1
Feb 7 14:59:44 kernel: PS:on listen:2 inPS:32770ms in_pvb:1(28041ms)
Feb 7 14:59:44 kernel: ps_trans_status:0x0 ps_requester:0x1 ps_txfifo_blk:0
Feb 7 14:59:44 kernel: tx_block:0 ext_qos_null:0 psp_onresp:0 psp_pending:0 pspoll_pkt_waiting:0
Feb 7 14:59:44 kernel: prio[0]: psq:0 supr_psq:0 bytes:50
Feb 7 14:59:44 kernel: AID:35
Feb 7 14:59:44 kernel: PVB offset:4 bcmc_bytes:0 length:1 08
Feb 7 14:59:44 kernel: wl1.1: 5a:40:4d:3f:5a:1e wlc_apps_ps_timedout: 1 packets timed out
Feb 7 14:59:44 kernel: PS:on listen:2 inPS:32799ms in_pvb:1(28070ms)
Feb 7 14:59:44 kernel: ps_trans_status:0x0 ps_requester:0x1 ps_txfifo_blk:0
Feb 7 14:59:44 kernel: tx_block:0 ext_qos_null:0 psp_onresp:0 psp_pending:0 pspoll_pkt_waiting:0
Feb 7 14:59:44 kernel: prio[0]: psq:0 supr_psq:0 bytes:50
Feb 7 14:59:44 kernel: AID:35
Feb 7 14:59:44 kernel: PVB offset:4 bcmc_bytes:0 length:1 08
Feb 7 14:59:44 kernel: wl1.1: wlc_ap_scb_unusable_stas_timeout: send deauth to 5a:40:4d:3f:5a:1e with reason 4
Feb 7 14:59:44 kernel: wl1.1: wlc_send_deauth: send deauth for 5a:40:4d:3f:5a:1e with reason 4
Feb 7 14:59:44 kernel: wl1.1: wlc_senddeauth_ex: station 5a:40:4d:3f:5a:1e has been notified of deauthentication using hwrs_scb
Feb 7 14:59:44 kernel: wl1.1: wlc_deauth_sendcomplete: no ACK from 5a:40:4d:3f:5a:1e for Deauth (txs suppr: 0x0)
Feb 7 14:59:44 kernel: wl1: notify system/blog disconnection event.
Feb 7 14:59:44 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 5A:40:4D:3F:5A:1E, status: 0, reason: Disassociated due to inactivity (4), rssi:-87
Feb 7 14:59:44 kernel: wl_handle_blog_event: mark as DIS-associated. addr=5a:40:4d:3f:5a:1e
Feb 7 14:59:44 kernel: iov:SCB_DEAUTHORIZE 5a:40:4d:3f:5a:1e
Feb 7 14:59:44 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Feb 7 14:59:45 kernel: wl1.1: wlc_scb_clearstatebit: 5a:40:4d:3f:5a:1e: clear bits 0x13 [ AUTHENTICATED ASSOCIATED AUTHORIZED ]
Feb 7 14:59:45 kernel: wl1.1: wlc_scb_clearstatebit: 5a:40:4d:3f:5a:1e: oldstate = 0x13, scb->state = 0x00 [ ]
Feb 7 14:59:45 kernel: wl1.1: wlc_ap_scb_unusable_stas_timeout Timeout Free scb:5a:40:4d:3f:5a:1e
Feb 7 14:59:45 kernel: wlc_ap_aid_free releasing bit = 35 for bsscfg 1 in AIDMAP
Feb 7 14:59:45 kernel: wl1.1: wlc_scb_clearstatebit: 5a:40:4d:3f:5a:1e: clear bits 0xff [ AUTHENTICATED ASSOCIATED PENDING_AUTH PENDING_ASSOC AUTHORIZED SAE_AUTH_CF ]
Feb 7 14:59:45 kernel: wl1.1: wlc_scb_clearstatebit: 5a:40:4d:3f:5a:1e: oldstate = 0x00, scb->state = 0x00 [ ]
Feb 7 15:00:00 kernel: 5A:40:4D:3F:5A:1E not mesh client, can't delete it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-16-2025 05:25 PM - edited 02-16-2025 05:26 PM
I have the beta firmware (RT-BE92U_9.0.0.6_102_37803) and my son is noticing disconnects on his iPad playing roblox. Around the time of the disconnects, I see the following in the router's log:
Feb 16 13:21:03 wlceventd: wlceventd_proc_event(696): wl1.1: Auth XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:0
Feb 16 13:21:03 wlceventd: wlceventd_proc_event(706): wl1.1: ReAssoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-69
Feb 16 13:21:40 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated due to inactivity (4), rssi:-75
Feb 16 13:21:40 kernel: WLC_SCB_DEAUTHORIZE error (-30)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2025 04:00 AM - edited 02-21-2025 04:01 AM
Yesterday a new firmwareupdate applies on the router of my father!
3.0.0.6.102_37500-g4c425bc_1088-g416ff_BB0B
Let us be surprised!!!
