Thought so, you dint pay attention not that one; look at my post first page or at bennor-s screenshot a couple posts back - Multi-User Mimo isn't the same as OFDMA / MU-MIMO...
The 3006.102.5 firmware has a similar choice option in the OFDMA / MU-MIMO drop down selection box. It has DL/UL OFDMA + MU-MIMO. Example from an RT-AX86U Pro running 3006.102.5:
That one is the same for me, but no - Multi-User Mimo.The 3006.102.5 firmware has a similar choice option in the OFDMA / MU-MIMO drop down selection box. It has DL/UL OFDMA + MU-MIMO. Example from an RT-AX86U Pro running 3006.102.5:
PS: The 3006.102.5 firmware has both Multi-User MINO and OFDMA/MU-MIMO options.
Wireless drivers crashing. Nothing Merlin can do about it as they're closed source and precompiled.I've upgraded from Merlin 3006.102.4 -> 3006.102.6.
Router = BE86U
Current uptime = 2 days
I've received messages like this at least 3 times. Thoughts on this please....?
Nov 14 15:45:19 kernel: ===DDD===
Nov 14 15:45:19 kernel: 00010000 - 00092000, [dcd]
Nov 14 15:45:19 kernel: f6f77000 - f6f7b000, [libnss_dns.so.2]
Nov 14 15:45:19 kernel: f6f8c000 - f6f9d000, [libresolv.so.2]
Nov 14 15:45:19 kernel: f6fb1000 - f6fce000, [libgcc_s.so.1]
Nov 14 15:45:19 kernel: f6fdf000 - f6fe8000, [libnss_files.so.2]
Nov 14 15:45:19 kernel: f7201000 - f7204000, [libnss_mdns4_minimal.so.2]
Nov 14 15:45:19 kernel: f7b1a000 - f7c4a000, [libc.so.6]
Nov 14 15:45:19 kernel: f7c60000 - f7d62000, [libshn_pctrl.so]
Nov 14 15:45:19 kernel: f7d84000 - f7d86000, [libdl.so.2]
Nov 14 15:45:19 kernel: f7d97000 - f7df3000, [libm.so.6]
Nov 14 15:45:19 kernel: f7e04000 - f7e1a000, [libpthread.so.0]
Nov 14 15:45:19 kernel: f7e2e000 - f7e34000, [libshn_utils.so]
Nov 14 15:45:19 kernel: f7e47000 - f7e6a000, [ld-linux.so.3]
Nov 14 15:45:19 kernel: CPU: 1 PID: 5796 Comm: dcd Tainted: P O 4.19.294 #1
Nov 14 15:45:19 kernel: Hardware name: Broadcom-v8A (DT)
Nov 14 15:45:19 kernel: pstate: 200b0010 (nzCv q A32 LE aif)
Nov 14 15:45:19 kernel: pc : 00000000000263e0
Nov 14 15:45:19 kernel: lr : 000000000002667c
Nov 14 15:45:19 kernel: sp : 00000000ffd9a550
Nov 14 15:45:19 kernel: x12: 00000000817eff01
Nov 14 15:45:19 kernel: x11: 00000000000812f4 x10: 0000000000000012
Nov 14 15:45:19 kernel: x9 : 0000000000000003 x8 : 0000000000000012
Nov 14 15:45:19 kernel: x7 : 00000000f64ffd90 x6 : 0000000000000036
Nov 14 15:45:19 kernel: x5 : 000000000000010c x4 : 00000000f64ffdf0
Nov 14 15:45:19 kernel: x3 : 0000000000000000 x2 : 0000000000000011
Nov 14 15:45:19 kernel: x1 : 0000000000000011 x0 : 0000000000000000
---
Nov 14 21:23:18 kernel: ===DDD===
Nov 14 21:23:18 kernel: 00010000 - 00020000, [asd]
Nov 14 21:23:18 kernel: f706d000 - f7071000, [libnss_dns.so.2]
Nov 14 21:23:18 kernel: f7082000 - f7093000, [libresolv.so.2]
Nov 14 21:23:18 kernel: f70a7000 - f70aa000, [libnss_mdns4_minimal.so.2]
Nov 14 21:23:18 kernel: f70bb000 - f70c4000, [libnss_files.so.2]
Nov 14 21:23:18 kernel: f72dc000 - f72ee000, [libasd.so]
Nov 14 21:23:18 kernel: f72ff000 - f731c000, [libgcc_s.so.1]
Nov 14 21:23:18 kernel: f732d000 - f745d000, [libc.so.6]
Nov 14 21:23:18 kernel: f7473000 - f747a000, [libjson-c.so.2.0.2]
Nov 14 21:23:18 kernel: f748b000 - f748d000, [libasc.so]
Nov 14 21:23:18 kernel: f749f000 - f750e000, [libssl.so.1.1]
Nov 14 21:23:18 kernel: f7524000 - f7763000, [libcrypto.so.1.1]
Nov 14 21:23:18 kernel: f7787000 - f77ee000, [libcurl.so.4.8.0]
Nov 14 21:23:18 kernel: f7801000 - f785d000, [libm.so.6]
Nov 14 21:23:18 kernel: f786e000 - f7884000, [libpthread.so.0]
Nov 14 21:23:18 kernel: f7898000 - f78a2000, [libwlcsm.so]
Nov 14 21:23:18 kernel: f78b5000 - f78b7000, [libdl.so.2]
Nov 14 21:23:18 kernel: f78c8000 - f78cf000, [libcrypt.so.1]
Nov 14 21:23:18 kernel: f7907000 - f79c0000, [libshared.so]
Nov 14 21:23:18 kernel: f79f9000 - f7a01000, [libnvram.so]
Nov 14 21:23:18 kernel: f7a13000 - f7a36000, [ld-linux.so.3]
Nov 14 21:23:18 kernel: CPU: 3 PID: 3582 Comm: asd Tainted: P O 4.19.294 #1
Nov 14 21:23:18 kernel: Hardware name: Broadcom-v8A (DT)
Nov 14 21:23:18 kernel: pstate: 00030010 (nzcv q A32 LE aif)
Nov 14 21:23:18 kernel: pc : 00000000f735a68c
Nov 14 21:23:18 kernel: lr : 00000000f72d6508
Nov 14 21:23:18 kernel: sp : 00000000f72d6508
Nov 14 21:23:18 kernel: x12: 0000000000000000
Nov 14 21:23:18 kernel: x11: 00000000f72d6790 x10: 00000000f7452eac
Nov 14 21:23:18 kernel: x9 : 00000000f746f000 x8 : 0000000000000001
Nov 14 21:23:18 kernel: x7 : 00000000000000af x6 : 00000000f72d6748
Nov 14 21:23:18 kernel: x5 : 00000000f72d6748 x4 : 0000000000000006
Nov 14 21:23:18 kernel: x3 : 0000000000000008 x2 : 0000000000000000
Nov 14 21:23:18 kernel: x1 : 00000000f72d6508 x0 : 0000000000000000
That option is for AC wireless, it's usable if you still have AC clients(most at this time iOT clients). Lesser importance nowadays since WFI 6,WIFI 7 are the present thing. This is sign of obsolesce for those clients. It doesn't mean it will not work now, those clients will be just last priorities.That one is the same for me, but - Multi-User Mimo.
But I do have AC clients, and service them for clients (I know it usability was never any good)...That option is for AC wireless, it's usable if you still have AC clients(most at this time iOT clients). Lesser importance nowadays since WFI 6,WIFI 7 are the present thing. This is sign of obsolesce for those clients. It doesn't mean it will not work now, those clients will be just last priorities.
The multiuser-Mimo is still available on latest stock firmware which released not to long ago. So it makes me wonder how it got removed in the first place. Also disabling ac/ax beam forming tells you that multiuser-Mimo doesn’t work without it but the setting isn’t actually there anymore. So to me it seems like it’s supposed to be there.That option is for AC wireless, it's usable if you still have AC clients(most at this time iOT clients). Lesser importance nowadays since WFI 6,WIFI 7 are the present thing. This is sign of obsolesce for those clients. It doesn't mean it will not work now, those clients will be just last priorities.
I know it hidden but my question is why get rid of the setting or implement an all in one setting for mu-mimo for download and upload streams so we can have more freedom to choose and not have to enable ofdma.
Can anyone running this beta (3006.102.6) tell me the wireless driver version?
On 3006.102.5 its: version 17.10.188.6401 (r808804)
This information is on the System Info page.
I had some issues, primarily with AiMesh, with this beta. I’m back to 3006.102.5 for now.
| wl0: Oct 14 2025 11:33:25 version 17.10.369.39012 (r839077) BSPv1W13 on GT-BE98 PRO |
Hasn't changed for WiFi 6 models...Can anyone running this beta (3006.102.6) tell me the wireless driver version?
On 3006.102.5 its: version 17.10.188.6401 (r808804)
This information is on the System Info page.
I had some issues, primarily with AiMesh, with this beta. I’m back to 3006.102.5 for now.
I would guess, being on my 3rd Asus router now, that there is a logic to selecting options to get your router operating in the manner you desire that isn’t clearly delineated in any manual, How-To/FAQ. And that’s -IF- you understand the differences between the options/what they do/how they work.Under wireless professional settings. Check both 2.4ghz and 5ghz. There’s an option for ofdma/mu-mimo that is for ax devices but there should be an option called just mu-mimo that’s for ac devices.
Do you allow the GUI to save cookies in your browser? It should only remind you once and set a cookie, usually. Or browse directly with https…Hi,
I`m receiving the attached message everytime I start the login access to my router since the beta1 update.
I followed the installation with no success.
any suggestion?
if(ofdma_support){
var wl_11ax = '<% nvram_get("wl_11ax"); %>';
if(document.form.wl_nmode_x.value == '0' || document.form.wl_nmode_x.value == '8'){
if (based_modelid != 'RT-AX92U' || (wl_unit_value != '0' && wl_unit_value != '1')) {
$('#ofdma_field').show();
document.getElementById("wl_MU_MIMO_field").style.display = "none";
if(wl_11ax == '0'){
document.form.wl_ofdma.value = 0;
document.form.wl_ofdma.disabled = true;
$('#ofdma_hint').show();
}
}
}
if(ofdma_support){
if(document.form.wl_ofdma.value == '3' || document.form.wl_ofdma.value == '4'){
document.form.wl_mumimo.value = '1';
}
}
Best release in months for me. Finally stability since 102.4 or earlier. Haven't rebooted since installation. Replaced cable modem, patch cables, office 50' cable, switch to no avail over this time period. NOTHING. The 102.6_beta1 release seems to stop the >=1x daily router reboot. Synology counter issues, whether the stability source problem or not, also seem to be gone.Dirty install of 102.6 beta 1 up and running great for the day so far. No idea if it fixes the random need for rebooting daily, but the Synology / Client count bug hasn't resurfaced. Will update on any weirdness, but so far, so great! Thanks for the release!

Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!