What's new
  • 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!

ASUS RT-BE92U

  • Thread starter Thread starter Deleted member 77025
  • Start date Start date
Locked in few different places.
 
  • Like
Reactions: TnF
Seriously, don't buy the BE92U nano. It just use USB2.0 standard. Details:

For the ROG one I have no any detailed information.
 
Intel AX211 is fine. I used one for nearly a year in my laptop with zero issues, and my previous laptop had an AX200 or AX201, which was fine for many years. I recently upgraded to an Intel BE100 mostly for test/dev purposes.
 
New ASUS RT-BE92U.
fwebp






Specification:
WiFi 7 was nothing but a PITA for me, with the GT-BE98 Pro that I purchased and returned within a month of ownership, for a full refund. I'm back to WiFi 6 wired backhaul mesh setup with ZERO issues what so ever. WiFi 7 still needs a LOT of work, IMHO, especially the 6GHz channels.
 
I am having great success with this internal card upgrade. This way you can use existing laptop antennas. I generally avoid USB for permanent devices like this. I usually use PCI slot cards for desktops too.

 
You can do Guest Network to VPN on your RT-AX86U running Asuswrt-Merlin and YazFi script.


It's available in AMTM. I personally wouldn't replace good working RT-AX86U with RT-BE92U.
Tech9, you were right... After switching the RT-AX86U with the RT-BE92U for a week, I noticed the signal strength at favorite spots around the house were at best the same, but mostly worse (all 2x2 clients though). I couldn't get the VPN set up on the RT-BE92U as I wanted it (somehow it messed up the separate IoT network) and despite running the latest Merlin fw (3006.102.4 Beta 2) I got random reboots every other day.
And thanks for the tip with YazFi, just figured it out this morning, seems to be working like a charm! And with the latest fw for my old RT-AX86U (3004.388.9_2) some minor headaches on my IoT network are gone too (some clients wouldn't reconnect automatically after a fw upgrade).

I did like that the RT-BE92U was running much cooler (stable at 59C for all temps) and power consumption was about the same as the RT-AX86U (running two 80mm USB fans on the back though)

So I'll keep using my RT-AX86U until it falls off of Merlin's list of supported routers. Hopefully by then, there's a true successor out (not counting the RT-BE86U due to the lack of 6Ghz).

Tech9, thanks again for your advice, could have saved a lot of time ;-)
 
Tech9, you were right... After switching the RT-AX86U with the RT-BE92U for a week, I noticed the signal strength at favorite spots around the house were at best the same, but mostly worse (all 2x2 clients though). I couldn't get the VPN set up on the RT-BE92U as I wanted it (somehow it messed up the separate IoT network) and despite running the latest Merlin fw (3006.102.4 Beta 2) I got random reboots every other day.
And thanks for the tip with YazFi, just figured it out this morning, seems to be working like a charm! And with the latest fw for my old RT-AX86U (3004.388.9_2) some minor headaches on my IoT network are gone too (some clients wouldn't reconnect automatically after a fw upgrade).

I did like that the RT-BE92U was running much cooler (stable at 59C for all temps) and power consumption was about the same as the RT-AX86U (running two 80mm USB fans on the back though)

So I'll keep using my RT-AX86U until it falls off of Merlin's list of supported routers. Hopefully by then, there's a true successor out (not counting the RT-BE86U due to the lack of 6Ghz).

Tech9, thanks again for your advice, could have saved a lot of time ;-)
I have two BE92U's in an AiMesh setup and have the VPN connected 24/7 with 0 issues and not a single disconnection since day one. I am running the latest ASUS firmware though not Merlin.
 
I have two BE92U's in an AiMesh setup and have the VPN connected 24/7 with 0 issues and not a single disconnection since day one. I am running the latest ASUS firmware though not Merlin.
giving the new one from asus a try, hopefully 6hz behaves better and router doesnt crash... 3.0.0.6.102_37548
 
ok this new version from 04/21 is definitely more stable, 6hz now working, will report back later - also trying MLO one more time
I am using MLO since day one, one SSID, one connection, no headaches, stable as a rock.

I also set this option on my laptop:

Bcj5ryZe25.png
 
so should i send this device back @RMerlin, looks like a driver bug, i activated MLO again... so i'll be turning it off again.

Code:
May  4 14:34:07 wlceventd: wlceventd_proc_event(842): wl1: Radar detected
May  4 14:34:08 kernel: {BSS_UPDN::}wl1:0: wlc_mlo_bss_state_hndl: AUX to MAP update
May  4 14:34:08 kernel: {BSS_UPDN::}[wl1.0] [AUX2MAP] op 3 [wlc_mlo_bss_state_upd_aux2map 27255]
May  4 14:34:08 kernel: {BSS_UPDN::}[wl1.0] [CONT BSS OP] wlc state 3 op 3 flags3 0x0 [wlc_mlo_bss_state_hndl 27475]
May  4 14:34:08 kernel: {BSS_UPDN::}[wl2.0] [BSS OP PEER] op 3 [wlc_mlo_process_bss_state_upd 27313]
May  4 14:34:08 cfg_server: cm_updateChanspec call wl_chanspec_changed_action
May  4 14:34:08 cfg_server:  event: wl_chanspec_changed_action_a103_1 of eid(0) of cfgs(4676)
May  4 14:35:25 rc_service: httpd 3757:notify_rc restart_ddns
May  4 14:35:26 Mastiff: Got AAE_SIG_EULA_FLAG_SIGNED
May  4 14:35:26 Mastiff: Select error
May  4 15:05:51 wlceventd: wlceventd_proc_event(842): wl1: Radar detected
May  4 15:05:51 cfg_server: cm_updateChanspec call wl_chanspec_changed_action
May  4 15:05:51 cfg_server:  event: wl_chanspec_changed_action_a103_1 of eid(1) of cfgs(4676)
May  4 15:25:54 kernel: PKT:
May  4 15:25:54 kernel:   0000: dc b2 82 c2 ae 00 00 00 ab ae ac f0 0f 04 02 02
May  4 15:25:54 kernel:   0010: 0e 00 00 00 00 0d 00 00 00 00 00 00 ff ff 00 00
May  4 15:25:54 kernel:   0020: 00 80 00 01 09 18 02 ae 00 00 74 ad 82 c2 ba 0e
May  4 15:25:54 kernel:   0030: 00 00 00 00 28 00 01 04 02 00 af b2 af 80 0d f9
May  4 15:25:54 kernel:   0040: 49 90 00 00 00 0d 00 00 00 00 ab b5 80 80 80 80
May  4 15:25:54 kernel:   0050: 80 80 00 01 00 00 00 00 00 00 82 8d 1f 00 00 00
May  4 15:25:54 kernel:   0060: fb f9 7b cf ff f9 7d ad c9 7f ff ef f7 ef fe e7
May  4 15:25:54 kernel:   0070: ff ff db ff ff ff ff ef f7 fb e7 fe 7e ff ff bf
May  4 15:25:54 kernel:   0080: 7e ef ff ef bd df fb fd f3 ff ff ff ff 35 db ef
May  4 15:25:54 kernel:   0090: e7 5a bc df f3 f7 fe ff da 7e f7 ff fb fb df ef
May  4 15:25:54 kernel:   00a0: dc ff df 6f 7f f7 6e fb 3f ef de ff 7f ff fe df
May  4 15:25:54 kernel:   00b0: ed ef fc ff 5f f9 db db 5f ff 7f 7f f7 ff f7 ed
May  4 15:25:54 kernel:   00c0: 00 00 00 00 00 01 eb 7f 02 00 00 00 00 00 00 00
May  4 15:25:54 kernel:   00d0: 00 00 00 00 01 40 c2 07 7b 02 1f 02 6c 2a 1e 05
May  4 15:25:54 kernel:   00e0: ff ff 00 00 33 33 00 00 00 fb d8 b3 70 37
May  4 15:25:55 kernel: PKT:
[...]
May  4 15:26:28 kernel: PKT:
May  4 15:26:28 kernel:   0000: 6c e7 84 c4 ad 00 00 00 a8 ac ad e9 72 00 02 02
May  4 15:26:28 kernel:   0010: 0e 00 00 00 00 0d 00 00 00 00 00 00 ff ff 00 00
May  4 15:26:28 kernel:   0020: 00 80 00 01 09 18 02 ad 00 00 d2 e6 84 c4 f2 0e
May  4 15:26:28 kernel:   0030: 00 00 00 00 28 00 01 04 02 00 ad b0 b0 80 15 f8
May  4 15:26:28 kernel:   0040: 31 90 00 00 00 15 00 00 00 00 a8 b4 80 80 80 80
May  4 15:26:28 kernel:   0050: 80 80 00 01 00 00 00 00 00 00 ab 8f 1f 00 00 00
May  4 15:26:28 kernel:   0060: fb f9 7b cf ff f9 7d ad c9 7f ff ef f7 ef fe e7
May  4 15:26:28 kernel:   0070: ff ff db ff ff ff ff ef f7 fb e7 fe 7e ff ff bf
May  4 15:26:28 kernel:   0080: 7e ef ff ef bd df fb fd f3 ff ff ff ff 35 db ef
May  4 15:26:28 kernel:   0090: e7 5a bc df f3 f7 fe ff da 7e f7 ff fb fb df ef
May  4 15:26:28 kernel:   00a0: dc ff df 6f 7f f7 6e fb 3f ef de ff 7f ff fe df
May  4 15:26:28 kernel:   00b0: ed ef fc ff 5f f9 db db 5f ff 7f 7f f7 ff f7 ed
May  4 15:26:28 kernel:   00c0: 00 00 00 00 00 01 4b 0c 00 00 00 00 00 00 00 00
May  4 15:26:28 kernel:   00d0: 00 00 00 00 01 40 c2 07 41 01 5f 04 6c 57 1e 05
May  4 15:26:28 kernel:   00e0: ff ff 00 00 01 00 5e 00 00 fb d8 b3 70 37
May  4 15:56:53 kernel: {BSS_UPDN::}wl0:0: wlc_mlo_bss_state_hndl: AUX to MAP update
May  4 15:56:53 kernel: {BSS_UPDN::}[wl0.0] [AUX2MAP] op 3 [wlc_mlo_bss_state_upd_aux2map 27255]
May  4 15:56:53 kernel: {BSS_UPDN::}[wl0.0] [CONT BSS OP] wlc state 3 op 3 flags3 0x0 [wlc_mlo_bss_state_hndl 27475]
May  4 15:56:53 kernel: {BSS_UPDN::}[wl2.0] [BSS OP PEER] op 3 [wlc_mlo_process_bss_state_upd 27313]
May  4 16:14:15 kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
May  4 16:14:15 kernel: rcu:     0-...!: (0 ticks this GP) idle=758/0/0x0 softirq=9824580/9824580 fqs=0
May  4 16:14:15 kernel: rcu:     3-...!: (1 GPs behind) idle=612/0/0x1 softirq=6589050/6589050 fqs=0
May  4 16:14:15 kernel: rcu:     (detected by 2, t=1099434 jiffies, g=8377901, q=4)
May  4 16:14:15 kernel: Call trace:
May  4 16:14:15 kernel:  __switch_to+0xe8/0x170
May  4 16:14:15 kernel:  0xffffff8008cb8dd8
May  4 16:14:15 kernel: Call trace:
May  4 16:14:15 kernel:  __switch_to+0xe8/0x170
May  4 16:14:15 kernel:  0xffffff80080abef0
May  4 16:14:15 kernel: rcu: rcu_preempt kthread starved for 1099434 jiffies! g8377901 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=2
May  4 16:14:15 kernel: rcu: RCU grace-period kthread stack dump:
May  4 16:14:15 kernel: Call trace:
May  4 16:14:15 kernel:  __switch_to+0xe8/0x170
May  4 16:14:15 kernel:  __schedule+0x214/0x5a0
May  4 16:14:15 kernel:  schedule+0x38/0xa0
May  4 16:14:15 kernel:  schedule_timeout+0x15c/0x2a0
May  4 16:14:15 kernel:  rcu_gp_kthread+0x488/0x900
May  4 16:14:15 kernel:  kthread+0x118/0x150
May  4 16:14:15 kernel:  ret_from_fork+0x10/0x24
Oct 13 08:45:19 crond[3756]: time disparity of 15011999 minutes detected
Oct 13 08:45:19 disk_monitor: Got SIGALRM...
Oct 13 08:45:19 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Oct 13 08:45:19 kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
Oct 13 08:45:19 kernel: rcu:     3-....: (1 ticks this GP) idle=61a/1/0x4000000000000002 softirq=6589051/6589051 fqs=4
Oct 13 08:45:19 kernel: rcu:     3-...!: (1 ticks this GP) idle=61a/1/0x4000000000000002 softirq=6589051/6589051 fqs=0
Oct 13 08:45:19 kernel: rcu:      (t=900719960767 jiffies g=8377901 q=96423)
Oct 13 08:45:19 kernel: rcu:     (detected by 0, t=900718861343 jiffies, g=497589, q=249)
Oct 13 08:45:19 kernel:   running task   
Oct 13 08:45:19 kernel:   running task   
Oct 13 08:45:19 kernel:     0  1081      2 0x0000000a
Oct 13 08:45:19 kernel:     0     0      0 0x0000000a
Oct 13 08:45:19 kernel: Call trace:
Oct 13 08:45:19 kernel: Call trace:
Oct 13 08:45:19 kernel:  __switch_to+0xe8/0x170
Oct 13 08:45:19 kernel:  __switch_to+0xe8/0x170
Oct 13 08:45:19 kernel:  wl_worker_thread_func+0xb8/0x180 [wl]
Oct 13 08:45:19 kernel:  0xffffff8008c63ea0
Oct 13 08:45:19 kernel:  kthread+0x118/0x150
Oct 13 08:45:19 kernel:  ret_from_fork+0x10/0x24
Oct 13 08:45:19 kernel: rcu: rcu_sched kthread starved for 900718861347 jiffies! g497589 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
Oct 13 08:45:19 kernel: Call trace:
Oct 13 08:45:19 kernel: rcu: RCU grace-period kthread stack dump:
Oct 13 08:45:19 kernel:  dump_backtrace+0x0/0x150
Oct 13 08:45:19 kernel:  show_stack+0x14/0x20
Oct 13 08:45:19 kernel:     0    11      2 0x00000008
Oct 13 08:45:19 kernel:  sched_show_task+0x100/0x120
Oct 13 08:45:19 kernel: Call trace:
Oct 13 08:45:19 kernel:  dump_cpu_task+0x40/0x4c
Oct 13 08:45:19 kernel:  __switch_to+0x148/0x170
Oct 13 08:45:19 kernel:  rcu_dump_cpu_stacks+0x90/0xcc
Oct 13 08:45:19 kernel:  __schedule+0x214/0x5a0
Oct 13 08:45:19 kernel:  rcu_check_callbacks+0x67c/0x810
Oct 13 08:45:19 kernel:  schedule+0x38/0xa0
Oct 13 08:45:19 kernel:  update_process_times+0x2c/0x70
Oct 13 08:45:19 kernel:  schedule_timeout+0x15c/0x2a0
Oct 13 08:45:19 kernel:  tick_sched_timer+0x54/0xd0
Oct 13 08:45:19 kernel:  rcu_gp_kthread+0x488/0x900
Oct 13 08:45:19 kernel:  __hrtimer_run_queues+0x13c/0x1d0
Oct 13 08:45:19 kernel:  kthread+0x118/0x150
Oct 13 08:45:19 kernel:  hrtimer_interrupt+0xe4/0x2b0
Oct 13 08:45:19 kernel:  ret_from_fork+0x10/0x24
Oct 13 08:45:19 kernel:  arch_timer_handler_phys+0x30/0x40
Oct 13 08:45:19 kernel:  handle_percpu_devid_irq+0x80/0x140
Oct 13 08:45:19 kernel:  __handle_domain_irq+0x70/0xd0
Oct 13 08:45:19 kernel:  gic_handle_irq+0x5c/0xc0
Oct 13 08:45:19 kernel:  el1_irq+0xe8/0x190
Oct 13 08:45:19 kernel:  get_page_from_freelist+0xbc0/0x1110
Oct 13 08:45:19 kernel:  __alloc_pages_nodemask+0xd0/0x940
Oct 13 08:45:19 kernel:  allocate_slab+0x22c/0x4a0
Oct 13 08:45:19 kernel:  ___slab_alloc.constprop.0+0x3e4/0x740
Oct 13 08:45:19 kernel:  __slab_alloc.constprop.0+0x24/0x40
Oct 13 08:45:19 kernel:  kmem_cache_alloc+0x154/0x190
Oct 13 08:45:19 kernel:  __alloc_skb+0x4c/0x1f0
Oct 13 08:45:19 kernel:  __netdev_alloc_skb+0x40/0x140
Oct 13 08:45:19 kernel:  linux_pktget+0x90/0x110 [hnd]
Oct 13 08:45:19 kernel:  wlc_hdr_proc+0x70/0x360 [wl]
Oct 13 08:45:19 kernel:  wlc_sendpkt+0x664/0xc40 [wl]
Oct 13 08:45:19 kernel:  wl_start_txqwork+0x428/0x4e0 [wl]
Oct 13 08:45:19 kernel:  wl_worker_thread_func+0xb8/0x180 [wl]
Oct 13 08:45:19 kernel:  kthread+0x118/0x150
Oct 13 08:45:19 kernel:  ret_from_fork+0x10/0x24
May  4 16:15:15 crond[3756]: time disparity of -15011998 minutes detected
May  4 16:34:14 wlceventd: wlceventd_proc_event(706): wl0.1: ReAssoc 4C:49:6C:96:29:95, status: Successful (0), rssi:-59
May  4 16:34:17 wlceventd: wlceventd_proc_event(673): wl2.1: Disassoc 4C:49:6C:96:29:95, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
 
so should i send this device back @RMerlin, looks like a driver bug, i activated MLO again... so i'll be turning it off again.
Ask Asus' tech support.
 
I am using MLO since day one, one SSID, one connection, no headaches, stable as a rock.

I also set this option on my laptop:

View attachment 65469
i bought a be92u nano very cheap off ebay and wanted to see if it crashes the be92u router, interestingly so far it didn't i have an update of 1h with MLO turned on. so maybe the BE92u router can't deal with certain chipsets... the nano is silly obviously, but will transmit at USB2 peak rates only naturally. but simultaneous 5+6ghz does work. maybe just need to wait out until broadcom etc. drivers improve...
 
I notice quite a few in here are experiencing constant reboots. I can t seem to get my BE92U to go beyond approx 20hrs without rebooting. It's been like this for the last few weeks, despite trying with MLO on/off, enabling/disabling the 6ghz band and even changing channels. Hoping someone with some smarts might have a few ideas on how to address this before i reach out to ASUS Support.
 
I notice quite a few in here are experiencing constant reboots. I can t seem to get my BE92U to go beyond approx 20hrs without rebooting. It's been like this for the last few weeks, despite trying with MLO on/off, enabling/disabling the 6ghz band and even changing channels. Hoping someone with some smarts might have a few ideas on how to address this before i reach out to ASUS Support.
i just noticed you can send emails to asus right from the interface now, so i'll submit a couple of reports - but turning off 6gz, disabling automatic updates, rejecting all the privacy stuff seems to have made it a bit more stable

New record uptime on ASUS 3.0.0.6.102_37548

2 days 5 hour(s) 37 minute(s) 19 seconds
 
i just noticed you can send emails to asus right from the interface now, so i'll submit a couple of reports - but turning off 6gz, disabling automatic updates, rejecting all the privacy stuff seems to have made it a bit more stable

New record uptime on ASUS 3.0.0.6.102_37548

2 days 5 hour(s) 37 minute(s) 19 seconds

still going, here's the exact config: ASUS 3.0.0.6.102_37548 (recent release, dirty upgrade, with one rmerlin in between)

- AP mode
- 1 main MLO (activated) network combining 2.4/5/6 active with wifi7 and MLO fronthaul
- security & firmware upgrades off - policies rejected
- 5 GHZ no DFS
- 6 GHZ (4/5 power setting = good, not performance)
- Roaming assistant disabled, 2.4 b disabled
- everything else std

Connections are verified on 6GHz, using 6e AX211 client and Wifi 7 client. WPA2/3 - but WPA 3 is being used.

Previously i have gotten disconnects and reboots, reboots seem to be fixed atm. Disconnects still evaluating.

2 days 17 hour(s) 56 minute(s) 40 seconds
 
still going, here's the exact config: ASUS 3.0.0.6.102_37548 (recent release, dirty upgrade, with one rmerlin in between)

- AP mode
- 1 main MLO (activated) network combining 2.4/5/6 active with wifi7 and MLO fronthaul
- security & firmware upgrades off - policies rejected
- 5 GHZ no DFS
- 6 GHZ (4/5 power setting = good, not performance)
- Roaming assistant disabled, 2.4 b disabled
- everything else std

Connections are verified on 6GHz, using 6e AX211 client and Wifi 7 client. WPA2/3 - but WPA 3 is being used.

Previously i have gotten disconnects and reboots, reboots seem to be fixed atm. Disconnects still evaluating.

2 days 17 hour(s) 56 minute(s) 40 seconds

Did Asus fix the MLO issue?
 

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!
Back
Top