Beta Asuswrt-Merlin 388.1 Beta is available for select models

[skeal]

Do you even read my posts?

For what it's worth yes.

 

[Groslol]

Actually ASUS is very aware by now from every other user with your router model.

Ok perfect so! I hope they will fix that as soon as possible

 

[Groslol]

If he have read first post he should know about it. Common behave to not read first.

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

 

[skeal]

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

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.

 

[skeal]

If you need the basic settings I'll gladly post my settings in a separate thread for you.

 

[Groslol]

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.

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!

 

[John35]

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.

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.

 

[skeal]

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.

@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.

 

[Stpa67]

388.1 Beta 3 is running fine on my RT-AX58U, system log looks ok and every feature i use works fine:

- AiProtection
- Adaptive QoS
- Traffic Analyzer - Statistic
- UPnP Media Server, Samba (smb v2)
- OpenVPN Server
- DNSSEC, UPnP Secure

Beta 3 feels better than Asus Official Fw.

What i haven't tried is WPA3 Personal but i only got one device (Dell G7 notebook) with WPA3 support, not sure if the Galaxy Tab A, Galaxy S8, Galaxy A71 or the AppleTV 4k supports WPA3. The old Toshiba Satellite and HP DV7 does not support WPA3.

 

[John35]

@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.

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.

 

[skeal]

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.

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.

 

[RamGuy]

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.

 

[Ripshod]

The setting is still visible and active on RT-AX88U.

 

[archiel]

Sorry if this has already been covered but should Bandwidth Monitor (basic no Apps) be working on an RT-AX88U? Everything else looks fine (no wifi issues, no DNS leaking, IPv4 and IPv6 firewalls look fine, no drops in connectivity, no complaints from the family) and I can see traffic in the System Status box and in Traffic Monitor, but nothing at all in Bandwidth Monitor (tested with Edge and Firefox under Windows 10 & 11)

 

[blackfireball5]

Outside of Merlin's control, it is an ASUS issue, report it to them.

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.

I discovered an issue, unrelated to Merlin, in the firmware earlier with Beta 1 on the AXE-16000 and RMerlin worked with Asus engineers directly to create a temporary workaround until they can create a permanent resolution on their end.

Lets be real here. Whether we like it or not, we are indirect testers for Asus own firmware issues with access to firmware not released to the general public yet. Us communicating issues here is important.

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.

 

[RamGuy]

The setting is still visible and active on RT-AX88U.

I'm running 388.1 BETA3 on my RT-AX88U as well and it's still visible in the WebUI on that one. Seems like this is simply an oversight on the AsusWRT-Merlin firmware for the GT-AX6000.

 

[ColinTaylor]

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.

RMerlin has already answered this question here.

 

[RamGuy]

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.

 

[RMerlin]

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).

Backend code is identical, the only difference is the webui itself.

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.

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.

I worked with them on the crashing issue because it was a very critical one (complete router reboot), it was obviously not related in any way to a misconfiguration or a broken client, because multiple persons had the exact same issue (so it wasn't a hardware issue), and because when I asked their DPI/QoS engineer if he was aware of such an issue, turns out he already was (but on a different platform), and so there was already a simple fix to implement. So, this was a very specific situation, and people shouldn't take that as meaning I will accept to become a fulltime unpaid contact person between customers and Asus, especially not on something as generic as "My wifi no longer works properly", where you have 50 different variables involved that require investigating, including the end user's own environment, which means this has to be done on a case-by-case basis, it cannot be done globally as a whole.

If you look at this beta thread, as well as pretty much every previous beta thread, you will see a regular amount of people telling me that something suddenly got broken, and my answer often ends up being "There has been zero changes between the two versions". I'm sure you can see why I simply no longer start investigating every single reported cases, because it's insanely time consumming.

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.

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.

 

[blackfireball5]

Quite honestly, I ignore any Wifi-related complains.

Completely understand and respect that. I'm not insinuating that is your job.

However, my issue was not just that my wifi stopped working. It took down my entire network, including internet connectivity to my ethernet devices in an unusual manner that I've never seen before. Where connectivity was maintained, yet internet was only working for a game I was playing and nothing else on my ethernet connected computer was working. It required a reboot to restore functionality. This only happened during Beta 3.

That to me warranted reporting an issue and a concern that did not appear to be related to configuration. Then when 3-4 others reported the same network crippling issue, that raised alarm bells to me.

I am not intelligent enough on the matter to discern what is Beta 3 related verse an Asus's problem. So I just reported it.

If you are telling me it is unrelated to Beta 3, I respect that and I will move on.