Those aren't similar. The RT-AX88U Pro is superior.
That is not my experience. But go ahead and believe (partial) specs.
Both routers use the exact same SDK (5.04axhnd), with the same driver code.My guess is the same as usual: newer SDK
Didn't we already have this discussion here, and the one (not two) year difference inJust curious if something new has developed which I've missed by not camping in the forums recently.
Apart from surmised longer-support / line-up-existence, or possible appearance preference, what is the nature of your experience where the AX88 Pro exhibits any functional superiority over its fraternal twin?
Exactly what I'd had in mind, though this time the statement was more emphatic. Hence my seeking clarification.Didn't we already have this discussion here, ...
That sounds like you've had one in comparative service. Is this the case? The RT is truly all those things vs. the GT? Aside from indication there has been a revised switch (I believe it was that) in the RT since start of production, it still seems to me the greatest difference between them is an alternate board for the router form factor.The RT-AX88U Pro is a noticeably more stable, responsive, and slightly more performant router vs the older GT-AX6000.
My apologies for the delay. I updated on about 24th of January 2024. So far, only this new issue. It's an annoyance, since it does create additional steps for me whenever I reboot. I'll have to ponder on ways to improve the way I deal with it.Have you installed the latest FW 3.0.0.6.102_33308 for the RT-AX88U Pro? I just installed today and I am having a lot of Web UI inconsistencies and some kind of data corruption, I make an update, Apply the change and the Web UI shows like nothing was changed, only a Reboot will fix in some cases, in other not even a reboot
Web UI related issues I troubleshoot with basic principles in mind, fresh browser profile (Firefox, Chromium based, etc.), staying close to defaults as possible. Keeping in mind, Hard Refresh for a browser page, once in a while.Apply the change and the Web UI shows like nothing was changed, only a Reboot will fix in some cases, in other not even a reboot
Relatively simple investigation involved.In Wireless > General: With Smart Connect ON, Target Wake Time for 5GHz doesn't stay enabled.
Not sure if it's just a cosmetic issue on the frontend or there is an issue with an actual operation on the backend. Same toggle didn't have an issue with a Smart Connect OFF.
Though I wasn't bothered by the issue with TWT, I appreciate your reply very much. Was always curious to try SSH in general. Never had a reason to. Maybe I'll find some time during the week to give it a try.Relatively simple investigation involved.
Disable "Smart Connect". ssh in and issue command "nvram show > /tmp/twt.disabled". Or ".enabled" if that was the state of TWT.
Alter the state of TWT.
ssh back in if necessary and issue the complementary command (appropriate filename extension).
Enable both TWT and Smart Connect (perhaps sequentially), ssh back in if necessary, and do "nvram show > /tmp/twt.smart".
Now you've got 3 text files you can compare.
"diff /tmp/twt.*abled"
See which variables pertain. Say it's 'wl?_twt' so issue "sed -i '/_twt/!d' /tmp/twt.*"
Then "for i in /tmp/twt.*; do echo $i:; cat $i; echo; done"
It will be completely evident what's going on.
You can delete the text files if you wish, but they're innocuous, exist only in RAM, and will disappear on their own at the next reboot (what, a year from now? hopefully).
diff
and scp
were not found. Couldn't figure out how to operate in the router, so I just copied files to USB, then played with them locally.nvram show > /mnt/USB/twt.default
nvram show > /mnt/USB/twt.enabled
diff --unified twt.default twt.enabled
sed -i '/_twt/!d' twt.*
for i in twt.*; do echo $i:; cat $i; echo; done
twt.default:
wl0_twt=0
wl1_twt=0
wl_twt=0
twt.enabled
wl0_twt=1
wl1_twt=0
wl_twt=1
enable
TWT on 5GHz, CLI will say that TWT is enabled=1
but the web GUI still says disabled
. Forced refresh and logging in, in private window.RT-AX88U_Pro: start https:1024
RT-AX88U_Pro: start httpd:80
httpd: reload cert and clean all files
httpd: Save SSL certificate...1024
httpd: Generating SSL certificate...1024
Mastiff: init
httpd: Succeed to init SSL certificate...1024
httpd: Succeed to init SSL certificate...80
There'd be no feedback for that command unless it failed ("no news" is good news). The "-i" means edit the files in place and the "'/_twt/!d'" means delete any line which does not contain the character string "_twt". So the files then contain /only/ such lines (less to weed through).Not sure I follow how sed operates,
Copy to buffer to use for the next command? (Terminal didn't give output.)Bash:sed -i '/_twt/!d' twt.*
!
and d
individually do, for better comprehension, in hopes it creates a sticky note in my mind, to have less wasted space in there. (Who knows, might save a life one day.)!
- "does not contain" and d
- "string/line".TI calculator... Could have never imagined that was part of forming your suggestion.! is a negator. So the programmers would take the implied urgency the exactly wrong way! Hahaha.
Honestly, although I've rather lost track of exactly what was your dilemma, I do recall in working through my suggestion that I couldn't remember whether it was !/regex/ (as in a TI calculator [and didn't work]) or /regex/! (as in an HP better calculator [RPN]).
diff world.default world.beware_scribes_add_remove
This little bit of discussion reminded me of my P100 with, I think, 4 Mb RAM running Slackware with an early 2.x Linux kernel, before tabbed browser windows (Netscape). Somewhere I've got a screenshot indicating 96 netscape windows open, and the system was highly responsive! This was about the time Y2K was becoming a concern. The 32-bit seconds-counter overflow was actually more of a concern, but it wasn't until Windows98 itself was nearly done-for before anyone discovered a counter Windows used in W95 overflowed in like 39 days and caused a system lockup. This tells me that few people had left (were able to leave) such a system running long enough to identify the issue!Regarding 'time to do some housekeeping'... her thoughts exactly!
OE
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!