skeal
Part of the Furniture
For what it's worth yes.Do you even read my posts?
For what it's worth yes.Do you even read my posts?
Ok perfect so! I hope they will fix that as soon as possibleActually ASUS is very aware by now from every other user with your router model.
Sorry I just searched how to reproduce the WiFi issues in order to help for resolution and mixed one problem with another. I've read almost all the page of the post in order to find a solution to the WiFi problem, just forget about the WireGuard part as I read it like 2-3 weeks agoIf he have read first post he should know about it. Common behave to not read first.
My advice for WiFi is to use the minimalist approach. No extra features. Don't use smart connect, don't use WPA 3, don't use DFS channels etc.Sorry I just searched how to reproduce the WiFi issues in order to help for resolution and mixed one problem with another. I've read almost all the page of the post in order to find a solution to the WiFi problem, just forget about the WireGuard part as I read it like 2-3 weeks ago
Yes, I already use what you mention (No Smart connect, no DFS) but I use WPA 3 as it adds another layer of security. As I fallbacked to 386.7_2 I'm not really ready to retest 388 and factory reset another time to 386.7_2 :/ But thanks for the tips! I always try the minimalist approach as I always try to think security first (Although WiFi is less secure than cable it now provides better speeds now). Thanks for your help!My advice for WiFi is to use the minimalist approach. No extra features. Don't use smart connect, don't use WPA 3, don't use DFS channels etc.
You misunderstand. What I was asking was if the EEPROM data was the same between GT-AX6000 "standard" and "rog" user-interface firmwares, so you can switch between the two without having to reconfigure anything or having strange stuff happen (or does the ROG version add extra data, e.g. for user-interface settings). I of course understand you need to flash the other firmware to change between them.You either flash the ROG version of the firmware or the Classic version. You can't switch back and forth without reflashing the firmware again.
@RMerlin would be the best person to decide if switching back and forth using saved settings would work correctly or not. I personally don't see the point. If it's just colors that change and you like them stay with ROG.You misunderstand. What I was asking was if the EEPROM data was the same between GT-AX6000 "standard" and "rog" user-interface firmwares, so you can switch between the two without having to reconfigure anything or having strange stuff happen (or does the ROG version add extra data, e.g. for user-interface settings). I of course understand you need to flash the other firmware to change between them.
As I said, I might find initial setup easier with the "standard" interface and if the "rog" one has a bunch or gaming extras that might be nice afterwards.@RMerlin would be the best person to decide if switching back and forth using saved settings would work correctly or not. I personally don't see the point. If it's just colors that change and you like them stay with ROG.
Probably saving settings in each GUI would be advisable rather than using one setting file to go between the two. IMHO. But you've likely thought of this.As I said, I might find initial setup easier with the "standard" interface and if the "rog" one has a bunch or gaming extras that might be nice afterwards.
This is dismissive and unhelpful. Also, we don't know this as fact yet as we are still in discovery with what may be causing this.Outside of Merlin's control, it is an ASUS issue, report it to them.
The setting is still visible and active on RT-AX88U.
RMerlin has already answered this question here.I just got myself the GT-AX6000 and I noticed when using the stock AsusWRT firmware I can change between Symmetrical and Full-Cone NAT under WAN settings. Just like on my RT-AX88U. But after installing Asuswrt-Merlin 388.1 BETA3 the option has disappeared. I seem to be able to toggle Full-Cone NAT via SSH, it's just not visible in the WebUI.
Backend code is identical, the only difference is the webui itself.You misunderstand. What I was asking was if the EEPROM data was the same between GT-AX6000 "standard" and "rog" user-interface firmwares, so you can switch between the two without having to reconfigure anything or having strange stuff happen (or does the ROG version add extra data, e.g. for user-interface settings).
Quite honestly, I ignore any Wifi-related complains. Because out of 10 complains, 9 of them turn out to be configuration issues, or caused by people using cheap, broken IoT wifi clients. There are wifi-related complains with every single release. I refuse to become an unpaid tech support devoting hours of my time trying to investigate every single issue, and I'm can't expect their engineers to start devoting time and resources helping people troubleshoot their network just for the odd case that there _might_ be a genuine issue. That's the job of the tech support department, not the engineering department.That being said, I'm hoping RMerlin can comment whether he has any knowledge of the issue I shared in post #662 and whether it's something Asus is aware of.
Nothing strange there. As I mentioned, that feature does not work with the kernel 4.19 used by these newer models. That setting was simply not doing anything, hence its removal from these models that don't support it.Sounds a bit strange as the native AsusWRT firmware does feature the toggle for Full-Cone NAT. I had it when running 3.0.0.4.388.21617.
Quite honestly, I ignore any Wifi-related complains.
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!