Beta Asuswrt-Merlin 3004.388.5-beta is now available

[RMerlin]

Asuswrt-Merlin 3004.388.5 Beta is now available for all supported Wifi 6 models. The focus of this release is component updates, bug fixes, and reworking the way the QOS Classification page works (solving various issues, and also making it works even when not using Adaptive QoS).

3004.388.5 (xx-xxx-xxxx)
  - UPDATED: OpenSSL to 1.1.1w.
  - UPDATED: Curl to 8.4.0.
  - UPDATED: OpenVPN to 2.6.8.
  - CHANGED: Enable fast-io for OpenVPN clients and servers that
             use UDP, which will speed up performance on some models.
  - CHANGED: You can now directly enter an IPv6 address on the
             Network Tools page as a target.
  - CHANGED: Display tracked connections on the QoS/Classification
             page even if QoS isn't set to Adaptive QoS.
  - CHANGED: QOS/Classification page can now resolve local IPv6
             addresses.
  - CHANGED: Allow custom MTU for Wireguard clients (patch from
             Asus).
  - FIXED: CIDR-formatted addresses were rejected on the Network
           Filter page.  Implemented temporary workaround.
  - FIXED: Various issues with the QOS Classification page.
  - FIXED: Netfilter TEE kernel module is missing.
  - FIXED: OpenVPN client state getting cleared when Wireless
           was being restarted.
  - FIXED: Networkmap wasn't recognizing the GT-AX11000_PRO as
           having USB 3.0 ports

Please keep discussions in this thread on this specific beta release.

Downloads are here.
Changelog is here.

 

[RMerlin]

Reserved post.

 

[DJones]

Here’s a comparison of the alpha 3004.388.5 change log for those that are curious what has changed between alpha and beta.

Alpha: “3004.388.5 (xx-xxx-xxxx)
- UPDATED: OpenSSL to 1.1.1w.
- UPDATED: Curl to 8.4.0.
- UPDATED: OpenVPN to 2.6.6.
- CHANGED: Enable fast-io for OpenVPN servers using UDP, which
will speed up performance on some models.
- CHANGED: You can now directly enter an IPv6 address on the
Network Tools page as a target.
- CHANGED: Display tracked connections on the QoS/Classification
page even if QoS isn't set to Adaptive QoS.
- CHANGED: QOS/Classification page can now resolve local IPv6
addresses.
- FIXED: CIDR-formatted addresses were rejected on the Network Filter
page. Implemented temporary workaround.”

 

[RMerlin]

Here’s a comparison of the alpha 3004.388.5 change log

The changelog does not reflect all changes between builds.

merlin@ubuntu-dev:~/amng$ git log --oneline ea1e2fbf24..HEAD
3bff71cf6c (HEAD -> master, tag: 3004.388.5-beta1, origin/master) Bumped revision to beta 1
611582d70d Updated documentation
3ff1e7364c Revert "rc: move ovpn nvram reset to init_nvram() to better match upstream"
6e6e491ee8 rom: fix filename format of retrieved changelog
0c7f029771 Updated documentation
aace5c8adc build: re-enable XT_TEE kernel module at all time
68986f5ad5 webui: implement interface for Wireguard client MTU
6f07de9766 rc: implement MTU support for Wireguard client (patch from Asus)
dc412d44e3 libovpn: enable fast-io for OpenVPN UDP clients
b376d7bd39 openvpn: update to 2.6.8

 

[DJones]

The changelog does not reflect all changes between builds.

merlin@ubuntu-dev:~/amng$ git log --oneline ea1e2fbf24..HEAD
3bff71cf6c (HEAD -> master, tag: 3004.388.5-beta1, origin/master) Bumped revision to beta 1
611582d70d Updated documentation
3ff1e7364c Revert "rc: move ovpn nvram reset to init_nvram() to better match upstream"
6e6e491ee8 rom: fix filename format of retrieved changelog
0c7f029771 Updated documentation
aace5c8adc build: re-enable XT_TEE kernel module at all time
68986f5ad5 webui: implement interface for Wireguard client MTU
6f07de9766 rc: implement MTU support for Wireguard client (patch from Asus)
dc412d44e3 libovpn: enable fast-io for OpenVPN UDP clients
b376d7bd39 openvpn: update to 2.6.8

Yes I understand that. Merely wished to show that the differences were not a cosmetic name change from alpha to beta. The alpha build seemed generally stable I know that is not a universal observation when dealing with so many router builds. A true diff changelog would have been better as you have provided above.

 

[DJones]

-GT-AX11000 - Dirty successful upgrade from alpha 3004.388.5 to beta 3004.388.5 no factory reset.

-RT-AX58U - (Used as Mesh) Dirty successful upgrade from alpha 3004.388.5 to beta 3004.388.5 no factory reset.

-Amtm entware is present on the gt-ax11000 no issue with packages noticed all appear to be present and functioning.

Not tracking uptime as I prefer to schedule a router reboot daily. Will update if instability is observed.

---

[Non-issue below but someones going to post about it. Aka me.... because I forget sometimes.]

GT-AX11000 Broadcom Driver/Kernel information noticed in logs. Unsure if relevant or just boot-time information will provide here in case it's information that is useful in some way. I understand dcd is a well known issue and is a closed component of Trend Micro, and cannot be fixed by RMerlin. The rest I'm not so sure if it's related to that or not, but likely just a crash log of dcd.

Nov 26 23:24:01 kernel: potentially unexpected fatal signal 11.
Nov 26 23:24:01 kernel: CPU: 1 PID: 28002 Comm: dcd Tainted: P O 4.1.51 #2
Nov 26 23:24:01 kernel: Hardware name: Broadcom-v8A (DT)
Nov 26 23:24:01 kernel: task: ffffffc0256dcb00 ti: ffffffc01dab4000 task.ti: ffffffc01dab4000
Nov 26 23:24:01 kernel: PC is at 0xf711a39c
Nov 26 23:24:01 kernel: LR is at 0x1dce0
Nov 26 23:24:01 kernel: pc : [<00000000f711a39c>] lr : [<000000000001dce0>] pstate: 600f0010
Nov 26 23:24:01 kernel: sp : 00000000ffdf25d8
Nov 26 23:24:01 kernel: x12: 00000000000a2050
Nov 26 23:24:01 kernel: x11: 00000000f63ff024 x10: 00000000000a23c4
Nov 26 23:24:01 kernel: x9 : 00000000f63ff760 x8 : 00000000000a287c
Nov 26 23:24:01 kernel: x7 : 00000000f63ff798 x6 : 00000000000a2876
Nov 26 23:24:01 kernel: x5 : 0000000000000000 x4 : 00000000f63ff744
Nov 26 23:24:01 kernel: x3 : 0000000000000000 x2 : 00000000ffdf25b4
Nov 26 23:24:01 kernel: x1 : 000000000007d72a x0 : 0000000000000000

For a quick refresher on this dcd issue for those curious, and not a avid user of the forums search function.

In other word ignore it in your logs, it's a non issue dcd will most likely restart itself.

 

[aex.perez]

Had the BWDPI engine start back up for a for minutes like in the Alpha. During that time I was able to go to the Bandwidth Monitor and Data Classification page and see statististics like in the Alpha. After a few minutes post firmware update / reboot the BWDPI engine shut down and going back to the Bandwidth Monitor page there's no stats and at the Data Classification page I get the message "Note: Statistics require Traditional QoS mode or the TrendMicro bwdpi engine to be enabled." which is correct as both are disabled. It's only during startup that the BWDPI Engine runs, causing the Firewall to restart a times and kicking me out of the router GUI one time.

In the system log as the routher was starting up and the BWDPI engine was running there were a few instances of:

Nov 26 23:38:08 Router BWDPI: force to flush flowcache entries
Nov 26 23:38:08 Router kernel: IDPfw: Exit IDPfw
Nov 26 23:38:08 Router kernel: mod epilog takes 0 jiffies
Nov 26 23:38:08 Router kernel: IDPfw: Exit IDPfw
Nov 26 23:38:08 Router kernel: Exit chrdev /dev/idpfw with major 191
Nov 26 23:38:08 Router kernel: Exit chrdev /dev/idp with major 190
Nov 26 23:38:08 Router BWDPI: rollback fc
Nov 26 23:38:08 Router custom_script: Running /jffs/scripts/nat-start
Nov 26 23:38:08 Router custom_script: Running /jffs/scripts/firewall-start (args: eth0)

in the log. As I was going back and forth between to Data Classification and Bandwidth Monitor pages like I mentioned, I got kicked out of the router GUI one time. So I let it alone for a few minutes. After the few minutes, once the BWDPI enginge shut down and I could no longer get any stats from the Bandwidth Monitor or the Data Classification pages. The router stabilized and it's running smoothly just like with the Alpha for about the last hour.

Like before, reboot after applying firmware, start of bwdpi engine time stamp from bwdpi/dcd.stat;
Master@Router:/tmp/bwdpi# cat dcd.stat

***** data_colld statistics ************************************
start_time : 1701059896 (2023-11-26 23:38:16)

 

[Mikii]

- FIXED: OpenVPN client state getting cleared when Wireless
was being restarted.

Hi. Thanks for addressing this.

 

[Dedel66]

After a "dirty upgrade" from alpha router and node are up again and running without any problems.
All IOT devices reconnected. OVPN is working as expected.

 

[MDM]

Dirty upgrade from alpha, all working fine.

 

[shabbs]

Let's GO!

EDIT: Did a dirty upgrade on all my APs from the 2nd Alpha. No issues to report. Main router remains on Release version.

 

[elorimer]

Dirty upgrade on my AX-86Pro, with my USB drive attached, oops, from .4. Not pretty: the router did not restart after a power cycle. Unplugged the USB, power cycled and the router came up again but no system log. Plugged in the USB, power cycled, and it seems to be up, but my AIMesh node is gone. Going to let it settle a few hours and power cycle again.

EDIT: went back to .4, then upgraded without the USB attached, and all good.

 

[jerry6]

AX1100PRO and AXE1100 both working well after upgrade from latest Alpha build
Thanks

 

[Tech9]

@jerry6, you perhaps have GT-AXE11000 and GT-AX11000 Pro routers. You may want to fix your signature.

 

[ugandy]

AXE16000 upgraded, no issues

 

[LeoT]

what is the base version merged from? or it did not change?

e.g. in last version
3004.388.4 (21-Aug-2023)
- UPDATED: Merged GPL 388_23588.

 

[visortgw]

what is the base version merged from? or it did not change?

e.g. in last version
3004.388.4 (21-Aug-2023)
- UPDATED: Merged GPL 388_23588.

No change in GPL version from previous Merlin release.

 

[L&LD]

Yes, many changes.

Beta - Asuswrt-Merlin 3004.388.5-beta is now available

Asuswrt-Merlin 3004.388.5 Beta is now available for all supported Wifi 6 models. The focus of this release is component updates, bug fixes, and reworking the way the QOS Classification page works (solving various issues, and also making it works even when not using Adaptive QoS). 3004.388.5...

www.snbforums.com

 

[FLA_NL]

After 78 days of uptime on 3004.388.4, a dirty upgrade to 3004.388.5_beta1. No noticeable issues.

 

[Mutzli]

Upgraded from alpha2 to beta1, everything works as expected including traffic classification.