The issue was mostly with the main router, not the nodes.Does this mean that running your firmware on the nodes will be preferred until Asus stock catches up, or is it only relevant on the main router?
That would only work until they decide to jump to 4.0.0.x, which may very well happen at some point. I am actually a bit surprised that the next release will be using 3.0.0.6 rather than 3.1.0.0 or even 4.0.0.0, based on some of the coming changes that I know.Since Asus' nomenclature is moving up from 3.0.0.4.xxx to 3.0.0.6.xxx, maybe you can consider just adapting one number prior for your future releases. Can move from 388.2_xx to 6.110_xxx when they migrate to that scheme later. The "6" in front can help identify it to be a later release than the 388.2_xx and previous ones. Even if they keep going to 3.0.0.7.xxx, you are okay as well. If they rehash it to something completely new in the future, no need to worry about it again until then.
Any details you can share with the community? Is it a proper big upgrade ie completely revamped router UI? Or is it some amazing new features we didn't know we needed until they released them?That would only work until they decide to jump to 4.0.0.x, which may very well happen at some point. I am actually a bit surprised that the next release will be using 3.0.0.6 rather than 3.1.0.0 or even 4.0.0.0, based on some of the coming changes that I know.
It was just math example not new coming release.Any details you can share with the community? Is it a proper big upgrade ie completely revamped router UI? Or is it some amazing new features we didn't know we needed until they released them?
Nothing I am allowed to reveal yet beside the already announced VLAN + SDN support. All I can say is there is more.Any details you can share with the community?
you can just install alpha 1 for now and then upgrade to alpha 2 once its thereFirst of all, thank you @RMerlin for your excellent work, I just got my hands on the AX86U Pro and I was wondering if I should wait for the alpha 2 (I couldn't find it in OneDrive) to configure everything, or if the alpha 1 is perfectly fine? I am guesing there is some blocking point that is delaying the firmware build for the AX86U Pro, I tried searching in this thread but I couldn't find the reason. Thank you!
Yes LACP is working.Is LACP (link aggregation 802.3ad) actually working for you? When I used it on 388.2 alpha 2 on my GT-AX11000 it wasn’t actually working beyond one Ethernet functioning in a non LACP bonded state. Might be a device specific issue not sure, but LACP works fine on 388.1.
You are the only one in position to ask Asus upstream what changes in your firmware may cause AiMesh issues. The fact someone recognized the issue now and is working on a fix is much better than "works for me" and "outside of my control". Let's forget the heated conversations and move forward. Don't take issues reports as complaints. At the end of the day the entire community benefits from the better firmware. Looking forward to 388.2 release.
It is very interesting, because on RT-AX82U i have been running a fork: 388.1_0-gnuton1We just have to wait until asus sort it out. I gave up on it, sometimes it stays at 160 for me othertimes it drops to 80. I just let it go, 388.2 is working great otherwise. I think there is some major changes coming this year and hope that wifi stability is sorted on all fronts. It seems pretty stable since latest stock fw so it's heading in the right direction.
I am still having issues with 36/160 even in new firmware.
It switches to 36/80 on 5GHz, and device connects as 1200Mbit/s instead of 2400Mbit/s:
View attachment 48686
In wireless settings, 160MHz is selected at 160MHz only, not as AUTO or 20/40/80/160 selection
If I use old build RT-AX86U_386.5_2 it always stays at 36/160 and all devices that are capable always connect at 2400Mbit/s.
Anyone else has problems with 160MHz ?
and device connects as 1200Mbit/s instead of 2400Mbit/s:
What makes you think it's not working as indended, dropping channel width when it detects interference?We just have to wait until asus sort it out. I gave up on it, sometimes it stays at 160 for me othertimes it drops to 80.
Well where i live, all the neighbors use 2.4GHz only , no one is on 5GHz.What makes you think it's not working as indended, dropping channel width when it detects interference?
160 MHz requires a lot of bandwidth - more than is available without DFS channel. That means you are guaranteed to overlap with every neighbour also using 5 GHz, on top of interfering with any local radar. If the router drops from 160 to 80 MHz, then it muyst be doing so because something happened prompting it to do so.
One example would be Samsung S23 Ultra.Do you have this device with a problem on the Realtek chip?
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!