What's new

Release RT-AX86U Pro Version 3.0.0.6.102_34319 09OCT24 (2024/10/16 ?)

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

I don't understand why you bother to make unnecessary changes. N/AC/AX Mixed is the same as Auto because A clients don't exist. 20/40/80MHz only leaves ACSD enabled, 80MHz works well even in dense Wi-Fi environment condominium buildings. The more you play with settings the closer you get to the next factory reset. This is my experience on 388 firmware and I strongly believe 102 is even more fragile at the moment.
 
I don't remember what caused me to choose these settings. I'll change them as you suggest sometime and see how it works.

I don't understand what you are saying here:
20/40/80MHz only leaves ACSD enabled
 
Setting fixed channel and channel bandwidth stops Automatic Channel Selection Daemon so it doesn't check and hunt for better channel or bandwidth. Changes to both made automatically by ACSD may disconnect some of your Wi-Fi clients and some of them may not reconnect for some time after.
 
Setting fixed channel and channel bandwidth stops Automatic Channel Selection Daemon so it doesn't check and hunt for better channel or bandwidth.
That makes sense. That's why I set them :)

I'm confused what you said next - changes made by ACSD may disconnect some clients? I don't want that, right? Are you saying I should/can fix either channel or bandwidth but not both? Currently the Wi-Fi is super stable.
 
I can confirm this bug as well. But after using Ctrl + F5 it displays correctly after that. It's just displays wrong the first time changed. If you log out and back in, mine displays correctly when setting a specific channel. I have not tested auto because I always manually assign a channel.
 
Last edited:
I don't understand why you bother to make unnecessary changes. N/AC/AX Mixed is the same as Auto because A clients don't exist. 20/40/80MHz only leaves ACSD enabled, 80MHz works well even in dense Wi-Fi environment condominium buildings. The more you play with settings the closer you get to the next factory reset. This is my experience on 388 firmware and I strongly believe 102 is even more fragile at the moment.
Well, because the mouse over description says that Auto means 802.11ac, 802.11n, and 802.11a. Since I don't want 802.11a, I selected N/AC/AX Mixed which the mouse over says means Maximize Performance but does not allow 802.11a devices.
 
Well, because the mouse over description says

This mouse over tip is copy/paste from older versions of Asuswrt and was never fixed/updated for years. You may find your router doesn't even support AX according to this tip. Does it say 802.11ax somewhere? Attention to details... not good in Asuswrt. Even if you want A you most likely won't find such client. Just leave it on Auto and forget about it. Some things don't need further optimizing.
 
This mouse over tip is copy/paste from older versions of Asuswrt and was never fixed/updated for years. You may find your router doesn't even support AX according to this tip. Does it say 802.11ax somewhere? Attention to details... not good in Asuswrt. Even if you want A you most likely won't find such client. Just leave it on Auto and forget about it. Some things don't need further optimizing.
Thanks.
 
How is ASUS Merlin update coming along for this model? I need 3.0.0.6 for VLAN creation via GUI, but there are other features I need, such as add custom on-boot script, that are present in Merlin. Is it actually planned to release ASUS Merlin firmware for 3.0.0.6?
 
How is ASUS Merlin update coming along for this model? I need 3.0.0.6 for VLAN creation via GUI, but there are other features I need, such as add custom on-boot script, that are present in Merlin. Is it actually planned to release ASUS Merlin firmware for 3.0.0.6?

There is no ETA for a release for AX models. Merlin is still waiting on GPL code and it's not for sure if he even plans a release for AX models he has said it's a low priority.
 
Is it actually planned to release ASUS Merlin firmware for 3.0.0.6?
Only people who know for certain are at Asus since they are the one's who have to release the model GPL 3006.102 firmware to RMerlin. As already indicated RMerlin has repeatedly indicated the ETA is vague or non existent at this time. He posted this past Tuesday that he has a new ETA likely for the WiFi 7 models but who knows if Asus will stick to it this time around. For more see RMerlin's posts in the following discussions:
 
Sucks... I need 3.0.0.6 for VLAN management. I think it is possible to create VLAN using Merlin via CLI and that makes it difficult to manage.

How can I contact ASUS to ask them to release whatever information to Eric Sauvageau (Merlin developer) to make it easier for him to develop Merlin for 3.0.0.6 on AX86U Pro and whichever older models supported.
 
make it easier for him to develop Merlin for 3.0.0.6

This will be eventually done when 3006 code is mature enough for RMerlin to build his firmware on top. Otherwise it's a waste of time and resources. Even though AX-class RT/GT 3006 GPL for some of the compatible models is available - he knows better than anyone else when to start working on it.

 

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