randomName
Very Senior Member
I'm gonna upload 384.13 tomorrow and test things out. The other odd issue is my cable modem page is a lot slower to open up than before. I'll report back my findings.
Yes.If you login to the router, can you nslookup the name of your time server?
Yes.
And since I'm using <countrycode>.pool.ntp.org this should work even if one server went down temporarily?
@Adamm, is qos broken only on AX88 only or AC86U as well?Running self compiled 384.14_beta3-g907d21657b (7756 branch). Can confirm the DPI engine is working again and correctly identifying traffic. QOS is still broken but besides that everything else is running smooth, can't replicate any of the other issues people have been posting about the new SDK,
Are your drivers and os version the latest?Re-flashed 384.14b3 on RT-AC5300 and WiFi dropouts are back
Does anyone else have an Intel AX200 client to test with (almost every x570 motherboard)? So far I've only had the dropouts on this device but ONLY with 384.14b3 (384.13 completely stable)
If you don't mind me asking what is still broken in QoS, I'm assuming adaptive QoS is what you are referring to?Running self compiled 384.14_beta3-g907d21657b (7756 branch). Can confirm the DPI engine is working again and correctly identifying traffic. QOS is still broken but besides that everything else is running smooth, can't replicate any of the other issues people have been posting about the new SDK,
So, now that we've determined that fiber is better than DSL, what is the consensus on running beta 3 on an 86U?
It's hard to sort the wheat from the chaff in this thread lately.
Just the AX88U using the new SDK.
Well Merlin said he wasn't using the new SDK for it, until 384.15. So if you're using his latest beta build for the AX88U, QoS should be working just fine. I know I have it on, on the Beta3 build from the other day, and adaptive QoS seems to be working just fine.
Running self compiled 384.14_beta3-g907d21657b (7756 branch).
Well Merlin said he wasn't using the new SDK for it, until 384.15. So if you're using his latest beta build for the AX88U, QoS should be working just fine. I know I have it on, on the Beta3 build from the other day, and adaptive QoS seems to be working just fine.
Asus sent me a fix for the broken bwdpi with the new ax SDK. I'm dropping a beta3 test build with the new SDK + the bwdpi fix in https://www.asuswrt-merlin.net/test-builds/ .
My plan still hasn't changed for the RT-AX88U, 384.14 will stick to the previous SDK, and the new SDK will be scheduled for 384.15.
EDIT:I know that the System page is still broken, I haven't fixed that branch yet.I uploaded build g6ed03020e2 which contains the System page fixes.
The build he just uploaded today, does appear to have the new SDK back in it. As there's around a 5.7mb increase in file size. However the beta3 build before the build today, didn't have the new SDK for the AX88U. As I have been using it, and adaptive QoS is working on it. The file sizes seems to back me up on that as well. As it's 79.8mb vs 85.5mb(build he uploaded today).RMerlin is using the latest SDK on that alpha/beta build (he won't use it for 384.14 final though).
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!