Beta Asuswrt-Merlin 3006.102.6 Beta is now available

[John Adler]

Check to see if mu-Mimo is still showing up for you under both bands. I reset my settings after I updated so idk if that makes a difference.

Please explain how to do that , thxs

 

[Chestertheman]

Please explain how to do that , thxs

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.

 

[bennor]

Please explain how to do that , thxs

See Wireless > Professional in the router GUI. Example from the 3006.102.5 firmware:

The option(s) are there for both 2.4Ghz and 5Ghz bands on 3006.102.5 firmware for the RT-AX86U Pro.

 

[Mutzli]

Yes, I do have the operational LED lights ON, and the RGB lights Off.

"Clark, when one goes out, the whole string is out."

Joke aside, everything works as expected on my BE96U since I installed it earlier this week.

 

[pavlfz]

Updated to latest beta a few days ago. All is well with my ax86u pro, VPNs working as they should, the mu-mimo option is present on both wifi bands (I never fiddle around with this stuff because I know nothing, but it's currently set to DL OFDMA only), the new traffic analyser looks great and I also get the amusing 'successed' message after logging on, so for my use case it's all good! Thanks very much for putting the work in Merlin.

 

[RMerlin]

Does this mean that WISP will also be available on the ASUS RT-BE92U?

No.

 

[pavlfz]

Should've looked more closely, the option Multi-User Mimo isn't there on my ax86u pro

 

[Chestertheman]

View attachment 68926

Should've looked more closely, the option Multi-User Mimo isn't there on my ax86u pro

Good to know I’m not only one I guess. Idk what other models could have the same problem. I still wonder why target wake Time and WiFi agile band got removed even though it’s still in stock.

 

[halcy0n9001]

Dirty upgrade RT-AX86U Pro from 3006.102.5 to 3006.102.6_beta1 (running almost 2 days). Statistics page is working. Still cannot connect the Awair Element sensor as in previous 3006.102.x versions, still working around that with connecting it to the Access Point RT-AX86U (Non Pro). No other noticeable issues.

Is this a 2.4g device, and did it connect OK on previous firmware?

I'm deciding if I should upgrade from 3004.388.8_2 which has been very stable, but is now quite old.

 

[jksmurf]

I'm deciding if I should upgrade from 3004.388.8_2 which has been very stable, but is now quite old.

Not sure of your model but have a look at the thread below for opinions on the update.

3006.102 has a few very nice features like Guest Network Pro with VLANs for various models, has been through a few iterations of 102.x to 102.6 beta so is getting more reliable, but check the releases for issues for your model. You must factory reset after installing it, and manual configuration is also a must, do not import a saved CFG file.

There is actually quite an recent update from 3004.388.8_2 to 3004.388.10_2 btw, if you’re not ready for 3006.102.x just yet, assuming your model supports the latter.

RT-AX86UPro - Should I upgrade from 3004 to 3006 now?

I've been away for a while and left my AX86UPro on 3004.388.8_4 because it's mission critical: my wife works from home so it *must* work 100% of the time - which it has been. I'm aware of all the reasons why I should upgrade to 3006, but have also read the horror stories. Is it safe to upgrade...

www.snbforums.com

 

[FLA_NL]

Is this a 2.4g device, and did it connect OK on previous firmware?

I'm deciding if I should upgrade from 3004.388.8_2 which has been very stable, but is now quite old.

Yes, it is a 2,4g device and did connect on the 3004.388.8_2 firmware, issues started with 3006.102.x firmwares. But for the 3004.388.x firmwares it also never worked on guest networks, I had to put it on the main network. However that doesn't do the job either for 3006.102.x firmwares. If I search the internet the Awair Element device isn't the most compatible device either. It is also the only device having issues in my network.

 

[jksmurf]

device isn't the most compatible device either

Quite a few older or finicky IoT devices suffer that fate… quite a few threads on this, so won’t disrupt this thread with detail, but I find that WPA2 Personal, 2.4Ghz only, do not hide the SSID, set a static IP on the device itself, all improve the reliability of the connectivity to the devices, for my 30-40 odd IoT devices anyway.

Many also disable Smart Connect and narrow the 2.4Ghz bandwidth to 20Mhz and select a non crowded channel. I do not do this, Smart Connect works fine for me.

Guest networks and propagation to nodes is another whole set of separate threads, but if the networks are not propagating to nodes, then you might think it’s an IoT device issue, whereas it’s actually a proximity to node issue, a node that might not actually be broadcasting the guest network because the network is not being propagated to it.

 

[halcy0n9001]

Quite a few older or finicky IoT devices suffer that fate… quite a few threads on this, so won’t disrupt this thread with detail, but I find that WPA2 Personal, 2.4Ghz only, do not hide the SSID, set a static IP on the device itself, all improve the reliability of the connectivity to the devices, for my 30-40 odd IoT devices anyway.

Many also disable Smart Connect and narrow the 2.4Ghz bandwidth to 20Mhz and select a non crowded channel. I do not do this, Smart Connect works fine for me.

Guest networks and propagation to nodes is another whole set of separate threads, but if the networks are not propagating to nodes, then you might think it’s an IoT device issue, whereas it’s actually a proximity to node issue, a node that might not actually be broadcasting the guest network because the network is not being propagated to it.

This is pretty much what I did too, minus narrowing the bandwith. I guess I'll just have to repeat on newer FW. That's fine.

 

[FLA_NL]

Quite a few older or finicky IoT devices suffer that fate… quite a few threads on this, so won’t disrupt this thread with detail, but I find that WPA2 Personal, 2.4Ghz only, do not hide the SSID, set a static IP on the device itself, all improve the reliability of the connectivity to the devices, for my 30-40 odd IoT devices anyway.

Many also disable Smart Connect and narrow the 2.4Ghz bandwidth to 20Mhz and select a non crowded channel. I do not do this, Smart Connect works fine for me.

Guest networks and propagation to nodes is another whole set of separate threads, but if the networks are not propagating to nodes, then you might think it’s an IoT device issue, whereas it’s actually a proximity to node issue, a node that might not actually be broadcasting the guest network because the network is not being propagated to it.

Tried several of those settings, did a factory reset coming to the 3006 firmware, I don't use AiMesh. Only thing I can think of is doing a factory reset and don't use any Guest network related features and test again as it had also issues with that with pre 3006 firmwares. Thanks for the suggestions anyway.

 

[David Cavalli]

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!

 

[penguin22]

This build has been very stable, though I was finding that SmartConnect wasn't running properly and wouldn't roam clients between nodes properly (being sticky even when RSSI should have moved them). I suspect this could be a combination of using MLO and WiFi 7 modes. I changed Roaming Assistant to -65 for the 5GHz band, leaving 2.4GHz at -70 and clients have been roaming more consistently now. Short version, if people are seeing some non-desirable roaming behavior with the 39099 branch, it may be worth adjusting some of the settings to see if it improves.

 

[elorimer]

option Multi-User Mimo isn't there on my ax86u pro

It is in the pull-down for me.

 

[Geraner]

The Beta installed perfectly fine on my BE86U and has been stable so far. I was running Alpha 1 previously, so glad to see that this works with the new GPL since Alpha 2 wouldn't install.

Same here, was working perfectly for me now with Beta1.

 

[MDM]

It is in the pull-down for me.

??
Where?

 

[elorimer]

??
Where?