Beta Asuswrt-Merlin 388.1 Beta is available for select models

[Damit1]

Not sure if it is just me, WiFi optimization was easier and less "buggier" in Beta1, something is changed in my AX88U for sure between the 2 Betas.
Hope Beta3 would (intentionally or not) resolve it, it just annoying- worked flawlessly in Beta1.

 

[RMerlin]

Yes, that was my point.

What VPN type are you monitoring? Each type has its own separate refresh mechanism, which will be every 1-2 secs depending on the type.

Not sure if it is just me, WiFi optimization was easier and less "buggier" in Beta1, something is changed in my AX88U for sure between the 2 Betas.

Zero change to the wireless code between Beta 1 and Beta 2.

 

[zer0bitz]

I have just updated my GT-AX6000 to Beta2 from 386.7.2

My DDNS (Google Domains) was showing an exclamation mark
I disabled IPv6 Update in DDNS (i have native ipv6) and its working fine now for ipv4
is this a google problem or router problem?

I was having DDNS issues with NO-IP.com. Tried this and it worked right away. Thank you!

 

[DarkKnight75]

So will the AC86U be supported on .388 code? It's been several months since ASUS released a firmware update for this model.

 

[archiel]

I was having DDNS issues with NO-IP.com. Tried this and it worked right away. Thank you!

I have a slightly different setup - RT-AX88U and Asus DDNS, but I was also finding that DDNS would fail when IPv6 Native mode was enabled. (For Asus) DDNS needs to pick up the wan address on eth0, but on my setup it was only showing on br0 - you can use ifconfig br0, ifconfig eth0 to check.

More importantly, if the DDNS check fails for IPv6 it will also fail for IPv4 - hence the 'disable IPv6' solution.

Ended up creating ipv6add.sh in /jffs/addons/ddnsipv6

#!/bin/sh
sleep 10s
ip -6 address add dev eth0 $(nvram get ipv6_rtr_addr)/128
nvram set ddns_ipv6_update=1
service restart_ddns

and calling it from post-mount by adding

sh /jffs/addons/ddnsipv6/ipv6add.sh

as the last entry.

 

[Deleted member 22229]

So will the AC86U be supported on .388 code? It's been several months since ASUS released a firmware update for this model.

No, AC routers will remain on 386 code and updates will be fewer from what Merlin said.

388.1 Release notes
This code base is only available for AX models, AC models will stay on the 386.x code base. Asus hasn't added any of these to their End-of-Life list as of now, so that means they will still get updates, just not as frequently. Most of these models being 5-7 years old now, having reduced support isn't unreasonable (as opposed to competitors typically completely dropping ALL support within 2-4 years). On my end, I currently don't plan to drop support for these AC models for the time being, but as with upstream updates, these older models will get less frequent updates from me as well.

 

[skeal]

@RMerlin I found that when I was resetting to defaults to figure out what was causing the HW Accel to be enabled persistently, that "Game Boost" (probably out of your control) seems to force both HW Accel and Flow Cache. The only way to back out of this setting and it's effects is to reset to defaults. Now that I have it figured out, my router is stable with both HW Accel and Flow Cache disabled.

 

[shabbs]

No, it will be in beta 3.

 

[Deleted member 22229]

Got the whole weekend off.. Bring on Beta 3.

 

[shabbs]

Got the whole weekend off.. Bring on Beta 3.

Drop it like it's hot.

 

[Damit1]

Drop it like it's hot.

Oh lol. I have missinterpet the message. I thought Beta3 is out and I see not yet.

LOL
I missed a heartbeat

 

[S.claus]

@RMerlin I found that when I was resetting to defaults to figure out what was causing the HW Accel to be enabled persistently, that "Game Boost" (probably out of your control) seems to force both HW Accel and Flow Cache. The only way to back out of this setting and it's effects is to reset to defaults. Now that I have it figured out, my router is stable with both HW Accel and Flow Cache disabled.

Can you please explain why you would disable HW Accel and Flow Cache? Doesn't it severely limit your bandwidth throughput?

 

[skeal]

Can you please explain why you would disable HW Accel and Flow Cache? Doesn't it severely limit your bandwidth throughput?

I'm not doing it electively. Flow Cache and HW Accel are disabled when using Cake. Flow Cache is disabled for all kind of reasons. Enabling AI-Protection, Wireguard and other features does this by design. My ISP gives me 175/75 which on my router isn't impeded in any way with these settings.

 

[skeal]

If HW Accel and Flow Cache are not disabled in the above circumstances the feature being enabled probably won't work right

 

[skeal]

Basically I believe people should know that enabling these features can have an unwanted effect on the routers overall bandwidth capabilities.
What my point is in the above post, is that applying some settings messes with the intended operation of some of the routers previously applied settings. For instance, in my opinion if Cake is enabled you shouldn't be able to enable something like Game Boost, without some warning. Cake disables the dpi (deep packet inspection) engine, (for the most part), so that Cake can work. To disrupt this by applying a further setting (Game Boost), that somehow conflicts with it, without some kind of warning that it will disable Cake, or otherwise interfere with its operation, is not a transparent situation for the end user. IMHO. However this is the current situation with this firmware. This particular situation won't change anytime soon as @RMerlin doesn't support Game Boost. For now just be aware.

 

[DJBeat]

Hello, I have 388.1_beta2 on the AXE16000 and the 388.1_beta2 on the XT 12 - I reset both and wanted to set up the Mesh WiFi again, unfortunately the AXE16000 can't find the XT12 - do you have a tip for me, thank you very much

 

[skeal]

Hello, I have 388.1_beta2 on the AXE16000 and the 388.1_beta2 on the XT 12 - I reset both and wanted to set up the Mesh WiFi again, unfortunately the AXE16000 can't find the XT12 - do you have a tip for me, thank you very much

Have you tried using stock ASUS firmware on the XT12? This has helped others.

 

[DJBeat]

Have you tried using stock ASUS firmware on the XT12? This has helped others.

I have now installed version 3.0.0.4.388.21293 for XT 12 - reset XT 12 - unfortunately AXE16000 still does not find the XT12 :-(

maybe it's because there is no official 388 firmware for the AXE16000 yet...

Merlin 388.1beta2 Mesh Bug?

 

[RMerlin]

Merlin 388.1beta2 Mesh Bug?

Everything related to AiMesh is closed source and outside of my control.

 

[visortgw]

I have now installed version 3.0.0.4.388.21293 for XT 12 - reset XT 12 - unfortunately AXE16000 still does not find the XT12 :-(

maybe it's because there is no official 388 firmware for the AXE16000 yet...

Merlin 388.1beta2 Mesh Bug?

Try wired connection for initial setup if you have not already.