Release Asuswrt-Merlin 386.7 is now available for all models

[L&LD]

Why are you running the (old) beta? Either run the latest Alpha or the release version.

I don't believe that a beta has been released yet that is newer than those.

 

[PR3MIUM]

Observations after 3 1/2 days running continuously (previously did multiple reboots while checking all addons were working)

Good
IPv6 all fine (using WAN Automatic IP, IPv6 Native, DHCP-PD, Stateless)
Wi-5i 5.0 GHz & 160 MHZ seems stable - no signs of disconnects / drop outs
No unexpected reboots
Challenges
Although Qos\Cake is enabled so is Flow Control (previously it was disabled) - default setup no extra Cake scripts. Eventually disabled via Wireguard Manager.
Browser interface much more sluggish (than 386.5_2) tried Edge, Chrome, Opera, Firefox and running on different machines. Especially noticeable running Scribe, any attempt to open to open multiple sub windows results in periods of hanging before 'catching up'

after 1 day it seems to be running fine without any wifi dropouts.

just 1 error at night:

Jul 19 04:31:18 kernel: ^[[0;33;41m[ERROR pktrunner] runnerUcast_inet6addr_event,187: Could not rdpa_system_ipv6_host_address_table_find ret=-5^[[0m

 

[RMerlin]

Why are you running the (old) beta? Either run the latest Alpha or the release version.

I don't believe that a beta has been released yet that is newer than those.

He`s probably referring to the 386.7_1 test builds that are currently available. They aren`t official betas releases, just test builds containing a few recent fixes.

 

[lepa71]

Why are you running the (old) beta? Either run the latest Alpha or the release version.

I don't believe that a beta has been released yet that is newer than those.

I was referring to the test build from Merlin.

 

[Gary_Dexter]

IPv6 native works like a charm here. However, it takes up to 10 minutes to get IPv6, but after that everything is smooth.

Maybe everyone has to be a little more patient?

Is 48+ hours enough time?

 

[Blacklistedcard]

I noticed that many using the ax88u doesn't get assigned an IP using IPv6 'Native' using default settings. Using this stable release and beta .1, I have been able to get my ISP IPv6. But, when I want to assign a custom ipv6 DNS such as cloudflare or google, it doesn't work using 6rd option. Any way to get custom IPv6 DNS on AX88U or it's a lost cause due to ASUS 'closed source' the unit?

My AX88U has been fine with native IPV6. No problem with this build.

 

[Kingp1n]

I had to turn off IPV6 'Native' on test fm 386.7_1 when using unbound combined. I couldn't pinpoint if the issue was with Unbound while using IPV6 or the test firmware. In the meantime, I'm back to the original 386.7 fw with IPV6 disabled and back to DoT. I was getting unstable internet where streaming would disconnect or constant loading. All this even after a clean install.

I decided to go back to 386.7 without IPV6 and Unbound. I read somwhere Unbound hasn't been properly tested with IPV6 enabled so I'm back to DoT (i believe RMerlin cant properly test IPV6 as well with his setup (ISP doesnt support it) so it seems it's trial and error when enabling IPV6 with the firmware. I haven't had issues with IPV4 so I'm back to what works!!

Please let me know if my info is wrong and I'll gladly update my post.

 

[Damit1]

For whoever not following OneDrive of test betas- and have AX88U with WiFi drops- Merlin posted a firmware with older wifi drivers.
For me- last 2-3h, the wifi connection much more stable.
Hopefully will keep it that way

 

[JSRF_Retro]

My AX88U has been fine with native IPV6. No problem with this build.

Yes, the 'native' has been working for me in both the stable 386.7 and test build 386.7_1. I was wondering if anyone was having issues with custom DNS such as cloudflare or Google. But yes it's been working fine with no problems with my ISP's IPv6 working. Just wanted to give a custom DNS a go but it's not working.

But after reading that Rmerlin doesn't have access to IPv6 with ISP. Not going to push the issue, just was curious if others found a possible solution with Custom DNS on ax88u as I believe other models might be working perfectly with custom DNS.

For whoever not following OneDrive of test betas- and have AX88U with WiFi drops- Merlin posted a firmware with older wifi drivers.
For me- last 2-3h, the wifi connection much more stable.
Hopefully will keep it that way

Yes, I've been having pretty stable connection with the 386.7 build for WiFi. But it's good to hear that the older build is working for WiFi stability if an issue should arrive for myself on 386.7. Thank you for the input.

 

[Treadler]

No IPv6 issues seen here with 386.5*, or 386.7*.

 

[Dedel66]

Yes, the 'native' has been working for me in both the stable 386.7 and test build 386.7_1. I was wondering if anyone was having issues with custom DNS such as cloudflare or Google. But yes it's been working fine with no problems with my ISP's IPv6 working. Just wanted to give a custom DNS a go but it's not working.

But after reading that Rmerlin doesn't have access to IPv6 with ISP. Not going to push the issue, just was curious if others found a possible solution with Custom DNS on ax88u as I believe other models might be working perfectly with custom DNS.

Yes, I've been having pretty stable connection with the 386.7 build for WiFi. But it's good to hear that the older build is working for WiFi stability if an issue should arrive for myself on 386.7. Thank you for the input.

I`ve got my synology with `adguard home` working as custom DNS-server for IPv4 and IPv6.

BTW: No issues with wifi at all.

 

[prosperot]

There isn`t. The test build contained an updated driver + SDK for the RT-AX86U, which is different from the RT-AX88U.


Not at this time, no. I don`t have any updated driver for that model, and I don`t want to ask Asus for 10 different driver updates either, which would take weeks to obtain. It will have to wait for the next GPL merge, which won`t happen until a new major release.

Very understandable, but for my AX88 it means back to 386.5_2 because the wifi drops drive the family crazy. Thanks for the good work, I'll be back

 

[CaptnDanLKW]

Uptime ~16 days. Everything seems to be fine up till now. My Scribe logs have been clear (or expected noise) up till yesterday when I saw this in my logs. I was not home at the time but as far as I can tell, nothing service affecting, and my WiFi Devices have all remained connected. First time I've seen this with any version. Layman analysis seems it had an issue with the NAT tables.

Jul 19 17:13:07 RTAC86U kernel: find_appropriate_src 398: loop_cnt 0 h 2890 htable sz 3584 init_net ffffffc000715cc0 net ffffffc000715cc0 nat ffffffc01748f0f8 prev_nat           (null)
Jul 19 17:13:07 RTAC86U kernel: data ffffffc01901da30 len 64
Jul 19 17:13:07 RTAC86U kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jul 19 17:13:07 RTAC86U kernel: 00 00 00 00 00 00 00 00 f8 47 ca 12 c0 ff ff ff
Jul 19 17:13:07 RTAC86U kernel: f8 f0 48 17 c0 ff ff ff 00 00 00 00 00 00 00 00
Jul 19 17:13:07 RTAC86U kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jul 19 17:13:07 RTAC86U kernel: print_debug_log: === log_idx 183 ===
Jul 19 17:13:07 RTAC86U kernel: nf_nat_setup_info: srchash 110 ct ffffffc012c778a8 nat ffffffc00a20d078 nat_bysource ffffffc019018880
Jul 19 17:13:07 RTAC86U kernel: 184     n1: n (v 1 ffffffc00a20d078) next           (null) prev (v 0           (null) 0)
Jul 19 17:13:07 RTAC86U kernel: 185   head: n (v 1 ffffffc004328ef8) next           (null) prev (v 1 ffffffc019018880 ffffffc004328ef8)
Jul 19 17:13:07 RTAC86U kernel: 186     n2: n (v 1 ffffffc00a20d078) next ffffffc004328ef8 prev (v 1 ffffffc019018880 ffffffc00a20d078)
Jul 19 17:13:07 RTAC86U kernel: get_unique_tuple: ct ffffffc0041e06f0 ext ffffffc0069ba6c0 nfct_nat ffffffc0069ba6f8
Jul 19 17:13:07 RTAC86U kernel: nf_nat_setup_info: srchash df ct ffffffc0041e06f0 nat ffffffc0069ba6f8 nat_bysource ffffffc0190186f8
Jul 19 17:13:07 RTAC86U kernel: 189     n1: n (v 1 ffffffc0069ba6f8) next           (null) prev (v 0           (null) 0)
Jul 19 17:13:07 RTAC86U kernel: 190   head: n (v 0           (null))
Jul 19 17:13:07 RTAC86U kernel: 191     n2: n (v 1 ffffffc0069ba6f8) next           (null) prev (v 1 ffffffc0190186f8 ffffffc0069ba6f8)
Jul 19 17:13:07 RTAC86U kernel: nf_nat_cleanup_conntrack: ct ffffffc005102010 nat ffffffc004261078

(repeats a lot)

Jul 19 17:13:11 RTAC86U kernel: print_debug_log: === end ===
Jul 19 17:13:11 RTAC86U kernel: get_tot_size_all_ext_types: type 0 len 24 align 8 alloc_size 88 destroy           (null) move           (null)
Jul 19 17:13:11 RTAC86U kernel: get_tot_size_all_ext_types: type 1 len 32 align 8 alloc_size 64 destroy nf_nat_cleanup_conntrack+0x0/0xc0 move nf_nat_move_storage+0x0/0x100
Jul 19 17:13:11 RTAC86U kernel: get_tot_size_all_ext_types: type 2 len 24 align 4 alloc_size 88 destroy           (null) move           (null)
Jul 19 17:13:11 RTAC86U kernel: get_tot_size_all_ext_types: type 3 len 80 align 8 alloc_size 144 destroy           (null) move           (null)
Jul 19 17:13:11 RTAC86U kernel: get_tot_size_all_ext_types: type 4 len 24 align 8 alloc_size 88 destroy           (null) move           (null)
Jul 19 17:13:11 RTAC86U kernel: print_nat_table_by_hash: h 2890 htable sz 3584 init_net ffffffc000715cc0 net ffffffc000715cc0 ext tot_size 472
Jul 19 17:13:11 RTAC86U kernel: print_nat_table_by_hash: nat_bysource first ffffffc01748f0f8
Jul 19 17:13:11 RTAC86U kernel: data ffffffc01748f0f8 len 32
Jul 19 17:13:11 RTAC86U kernel: 00 00 00 00 00 00 00 00 50 da 01 19 c0 ff ff ff
Jul 19 17:13:11 RTAC86U kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jul 19 17:13:11 RTAC86U kernel: print_nat_table_by_hash 345: loop 0
Jul 19 17:13:11 RTAC86U kernel: print_nat_table_by_hash 347: print nat ffffffc01748f0f8
Jul 19 17:13:11 RTAC86U kernel: data ffffffc01748f0f8 len 32
Jul 19 17:13:11 RTAC86U kernel: 00 00 00 00 00 00 00 00 50 da 01 19 c0 ff ff ff
Jul 19 17:13:11 RTAC86U kernel: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jul 19 17:13:11 RTAC86U kernel: print_nat_table_by_hash 359: invalid ct           (null)
Jul 19 17:13:11 RTAC86U kernel: print_nat_table_by_hash 361: next nat           (null)
Jul 19 17:13:11 RTAC86U kernel: print_nat_table_by_hash 370: next loop 1

 

[Damit1]

25h or so the system is up and running using 386.7_1-gc8d0c5e6ca
Weekend is ahead of us so I can check better, but for now- it seems perfectly fine with wifi older drivers.

Over night the backhaul link stability got better a lot, got the same as before.
As it seems from the last day- it looking good.

Thank you one more time!

 

[RMerlin]

Updated test builds have been uploaded to the Onedrive Test Builds folder. These include updated wifi driver for the RT-AX86U, and downgraded wifi drivers for the RT-AX88U and GT-AX11000.

 

[Damit1]

Updated test builds have been uploaded to the Onedrive Test Builds folder. These include updated wifi driver for the RT-AX86U, and downgraded wifi drivers for the RT-AX88U and GT-AX11000.

Same WiFi driver as I got? I mean, should I upgrade or same as I got already?

 

[RMerlin]

Same WiFi driver as I got? I mean, should I upgrade or same as I got already?

I don't know what you're running.

 

[jata]

for those of us running stock on AiMesh nodes, Asus are dropping quite a few new firmware(s) - just seen RT-AC68U (3.0.0.4.386_49703) and RT-AX58U (3.0.0.4.386_49674) have been released.

@RMerlin - I have gone back to 386.5 on my RT-AX86S as I continued to get occasional random restarts with 386.7 (even after clean install). Happy to help test the new test build once I have updated my nodes. Is it possible that the issue I have had with the random reboot on 386.7 on AX86S is wifi driver related?

 

[RMerlin]

Is it possible that the issue I have had with the random reboot on 386.7 on AX86S is wifi driver related?

No idea. That would be unexpected since wifi runs on the SoC's own CPU. Random reboot sound more likely to be hardware issues, as actual crashes would generate a kernel panic log entry.

 

[iJorgen]

These include updated wifi driver for the RT-AX86U

Same WiFi driver as I got? I mean, should I upgrade or same as I got already?

I can see the last part "FWID 01-130100" is changed in this new builds, what ever that means...

Previous build:
wl0: Jul 15 2022 09:34:33 version 17.10.157.2809 (r801046)
wl1: Jul 2 2022 12:07:27 version 17.10.157.2809 (r801046) FWID 01-2f99c769

New build:
wl0: Jul 15 2022 09:34:33 version 17.10.157.2809 (r801046)
wl1: Jul 2 2022 12:07:27 version 17.10.157.2809 (r801046) FWID 01-130100