Release Asuswrt-Merlin 386.7 is now available for all models

[amomp3]

Hello, first of all this is what i think of humans that make things like these firmwares (not only scripst). As cooking is an act of love I can see this very similar so THANK YOU VERY MUCH!
(as you can see i was already reading about scmerlin because i really need wireguard)

I come from freshtomato (Asus RT-AC3200) because i need newer kernel to use wireguard for my work. Tried successfully with openwrt (on a mikrotik hap ac3) (nice wireguard gui) but also took the oportunity to upgrade hardware...

Have just unboxed a new AX88U. Is coming out of the box with version 386_48631-g10d88e5 so...

Can I just flash this latest version from the gui ?

some advice to do a successfull entry in this firmware to take advantage the fact that i am starting from zero ?

Thank you.

 

[isr25]

Odd. There could be a bug in the dnsmasq fix then, tho I haven`t seen them make any further change to that patch since it was published weeks ago.

I'll consider reverting it for the next release unless I don`t get any other similar report of dnsmasq crashes.

Tried to do some test after some feedback from you and @Jeffrey Young so I restarted my router using my phone. All devices connected normally. No dnsmasq crashes for 5 minutes. Turned on my work computer and connected it to the network, and immediately the dnsmasq crashed, albeit only once now. Seems like this is related to the crash. I can try to do a wipe of the router if you request it - I have not wiped my router for close to a year now, since dirty upgrades worked fine for me and I never skipped any Asuswrt-Merlin™ release

Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: DHCPREQUEST(br0) 192.168.50.224 84:c5:a6:XX:XX:XX
Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: Ignoring domain xxxx.com.my for DHCP host name XXXX00076
Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: DHCPACK(br0) 192.168.50.224 84:c5:a6:XX:XX:XX XXXX00076
Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: DHCPSOLICIT(br0) 00:01:00:01:25:fc:25:80:XX:XX:XX:XX:XX:XX
Jun 24 05:44:48 RT-AX86U-1F70 kernel: <unknown>: hw csum failure
Jun 24 05:44:48 RT-AX86U-1F70 kernel: CPU: 0 PID: 4971 Comm: dnsmasq Tainted: P           O    4.1.52 #2
Jun 24 05:44:48 RT-AX86U-1F70 kernel: Hardware name: Broadcom-v8A (DT)
Jun 24 05:44:48 RT-AX86U-1F70 kernel: Call trace:
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc000087398>] dump_backtrace+0x0/0x150
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0000874fc>] show_stack+0x14/0x20
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0005589d0>] dump_stack+0x90/0xb0
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003fe05c>] netdev_rx_csum_fault+0x3c/0x50
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003f22d0>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0004f8468>] udpv6_recvmsg+0x2a0/0x7d8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0004a616c>] inet_recvmsg+0xa4/0xc8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003df4d4>] sock_recvmsg+0x14/0x20
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003e10e4>] ___sys_recvmsg+0xac/0x1a8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003e3b18>] __sys_recvmsg+0x40/0x80
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc000423410>] compat_SyS_recvmsg+0x10/0x18

 

[Bobcat00]

For those of you who were having issues with 5ghz disconnecting with the previous few releases, how is it working with 386.7 build?

I never could solve the disconnects so I've been using 386.3_2 in the meantime.

Didn't someone say the 5ghz issue was recognized by ASUS and that a fix was coming? Weird how not all were experiencing it though. RT-AX68U here.

I just have an AX68U as a router, no mesh or anything. The 5 GHz used to crap out on a random basis. Sometimes within a few hours, sometimes in a week or two.

Since I updated to beta 2 on the 19th, and now the released version, I haven't had any drops.

 

[Lee MacMillan]

Dirty upgrade after 112 days uptime on 386.5_0. I remembered to dismount my USB drive this time! No issues after the first hour.

 

[Smokey613]

Updated both units to this latest version. So far no issues.

 

[AntonK]

Update from Beta2, no issues and network running smoothly hours later.

 

[Deleted member 22229]

Just flashed 386.7 AX58U. Clean install all good.

 

[predatorz]

Dirty upgrade from 386.5_2 to 386.7 for AC88U.
All good

 

[emwgee]

GT-AX11000 dirty upgraded from 386.7_beta2 to 386.7.
All seemed well except getting the following messages all the time, any idea what is wrong?


Jun 23 14:05:02 hostapd: wl0.1: STA ac:83:c6:64:67:06 IEEE 802.11: associated
Jun 23 14:05:02 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Jun 23 14:05:02 hostapd: wl0.1: STA ac:83:c6:64:67:06 RADIUS: starting accounting session BB4F14ED4BBE1886
Jun 23 14:05:02 hostapd: wl0.1: STA ac:83:c6:64:67:06 WPA: pairwise key handshake completed (RSN)

 

[RoiDesRois]

RT-AC86U dirty upgrade from 386.5_2 several hours ago with no issues to note. Thanks for your hard work.

 

[Jeffrey Young]

Tried to do some test after some feedback from you and @Jeffrey Young so I restarted my router using my phone. All devices connected normally. No dnsmasq crashes for 5 minutes. Turned on my work computer and connected it to the network, and immediately the dnsmasq crashed, albeit only once now. Seems like this is related to the crash. I can try to do a wipe of the router if you request it - I have not wiped my router for close to a year now, since dirty upgrades worked fine for me and I never skipped any Asuswrt-Merlin™ release

Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: DHCPREQUEST(br0) 192.168.50.224 84:c5:a6:XX:XX:XX
Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: Ignoring domain xxxx.com.my for DHCP host name XXXX00076
Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: DHCPACK(br0) 192.168.50.224 84:c5:a6:XX:XX:XX XXXX00076
Jun 24 05:44:15 RT-AX86U-1F70 dnsmasq-dhcp[4971]: DHCPSOLICIT(br0) 00:01:00:01:25:fc:25:80:XX:XX:XX:XX:XX:XX
Jun 24 05:44:48 RT-AX86U-1F70 kernel: <unknown>: hw csum failure
Jun 24 05:44:48 RT-AX86U-1F70 kernel: CPU: 0 PID: 4971 Comm: dnsmasq Tainted: P           O    4.1.52 #2
Jun 24 05:44:48 RT-AX86U-1F70 kernel: Hardware name: Broadcom-v8A (DT)
Jun 24 05:44:48 RT-AX86U-1F70 kernel: Call trace:
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc000087398>] dump_backtrace+0x0/0x150
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0000874fc>] show_stack+0x14/0x20
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0005589d0>] dump_stack+0x90/0xb0
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003fe05c>] netdev_rx_csum_fault+0x3c/0x50
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003f22d0>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0004f8468>] udpv6_recvmsg+0x2a0/0x7d8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0004a616c>] inet_recvmsg+0xa4/0xc8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003df4d4>] sock_recvmsg+0x14/0x20
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003e10e4>] ___sys_recvmsg+0xac/0x1a8
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc0003e3b18>] __sys_recvmsg+0x40/0x80
Jun 24 05:44:48 RT-AX86U-1F70 kernel: [<ffffffc000423410>] compat_SyS_recvmsg+0x10/0x18

Looks like something to do with the kernel hw csum failure.

A quick Google search says that error is;

This means driver injected a packet into kernel with bad flags.

 

[aublumberg]

I'm curious to know too, because it's not just the US getting gouged and ground down by their ISPs.
(then again, don't Hong Kongers have to contend with the Great Firewall?)

Equivalent of USD58 per month. No 'great firewal' in Hong Kong (well, not at this stage anyway) and VPNs fully functional to any global destination. I've been very pleased with the GT-AX6000 performance (credit to Merlin!) and also use a QNAP QSW-1105-5T which nicely extends the 2.5Gbps to multiple devices.

 

[Tech9]

Small, but nice detail in Media Bridge mode:

When connected to 5GHz AP the indicator and Tools page show correctly single radio in use only. On 386.5_2 it was showing incorrectly both.

 

[Calkulin]

Unable to update from 386.7_beta1, RT-AX68U

Stuck on "applying settings please wait", waited 10 to 20 minutes, internet disconnects, nothing happens, rebooting router shows beta1 again

tried 4 times

Were you trying to update the router remotely? I've seen that behavior mostly if trying to update remotely but locally it updates fine

That`s definitely not related, since the only changes between beta 2 and final were related to Tor and OpenVPN:

merlin@ubuntu-dev:~/amng$ git log 386.7-beta2..386.7 --oneline
94cc3d910e Bumped revision to 386.7 final
b7b2da99b0 Updated documentation
77bf6e916b shared: increase max ipv6_dns1_x length to 39 chars
6303f0be67 libovpn: also allow inbound OVPN client traffic destined at the router itself when the firewall is set to allow it
98b053d93c tor: updated to 0.4.7.8

I will say that this release does not have all the weird log entries that the Alphas and Betas had on my GT-AX11000. It's been almost 24 hrs now and no abnormal log entries compared to the Betas that started showing a bunch of kernel messages after 12 hrs post reboot. Either way if you did something or not, thanks

 

[Sneakytiki]

I do not post often - no need, everything is usually great and I've been dirty upgrading all year. This time - my AX88U did not like it.

Beta 1 was fine, Beta 2 started having intermittent client drops and radio cycling. Then this one completely borked my network.

50 Devices - Mesh with AX88U and AC3100. The ethernet ports were turning off and on, which I think turned out to be a WAN Aggregation problem. WIFI off and on, DNS issues, I could not set my network to channel 36 and 160Mhz, which is what I thought I usually set it at, but it easily could have been 36 and (20/40/80/160). There were also Broadcom errors, memory leaks maybe, possible USB drive issues, reboots, basically a very angry router. I only have pieces of logs from before the update and pretty much the entire log post reset and update. Not sure if they'll be helpful.

Did not have time to chase errors so wiped the USB drive, WPS reset, rebuilt the network. Everything works except WAN Aggregation and maybe setting to channel 36 and 160mhz manually. 160 worked for like an hour or two and now its gone which is unusual for me since its never been an issue.

Might rebuild and switch back to the last version, its something with the wireless updates. I have a 1200 down / 50 up connection which can do just over those numbers. Or maybe its time to node the AX88U and get a newer router. I've been wanting to get rid of the AC3100 for awhile now.

 

[Tech9]

UPNP is complaining in Double NAT:

Jun 23 20:50:13 miniupnpd[4040]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
Jun 23 20:52:32 miniupnpd[4040]: private/reserved address 192.168.144.16 is not suitable for external IP

I believe it was working and showing forwarded ports correctly in System Log, Port Forwarding on 386.5_2 firmware.

 

[capncybo]

I do not post often - no need, everything is usually great and I've been dirty upgrading all year. This time - my AX88U did not like it.

Beta 1 was fine, Beta 2 started having intermittent client drops and radio cycling. Then this one completely borked my network.

50 Devices - Mesh with AX88U and AC3100. The ethernet ports were turning off and on, which I think turned out to be a WAN Aggregation problem. WIFI off and on, DNS issues, I could not set my network to channel 36 and 160Mhz, which is what I thought I usually set it at, but it easily could have been 36 and (20/40/80/160). There were also Broadcom errors, memory leaks maybe, possible USB drive issues, reboots, basically a very angry router. I only have pieces of logs from before the update and pretty much the entire log post reset and update. Not sure if they'll be helpful.

Did not have time to chase errors so wiped the USB drive, WPS reset, rebuilt the network. Everything works except WAN Aggregation and maybe setting to channel 36 and 160mhz manually. 160 worked for like an hour or two and now its gone which is unusual for me since its never been an issue.

Might rebuild and switch back to the last version, its something with the wireless updates. I have a 1200 down / 50 up connection which can do just over those numbers. Or maybe its time to node the AX88U and get a newer router. I've been wanting to get rid of the AC3100 for awhile now.

160mHz is as wide a frequency range as possible meaning the chance of radio interference is that much greater + to use 160 you are within the DFS range. Meaning any radar signal detected & the router is basically mandated to drop the DFS ch & effectively your 5G/6 radio will essentially restart without it. Do yourself a solid favor & try maxing out your frequency at 80. Note: You can select auto & disable 160mHz(DFS)

 

[Sneakytiki]

160mHz is as wide a frequency range as possible meaning the chance of radio interference is that much greater + to use 160 you are within the DFS range. Meaning any radar signal detected & the router is basically mandated to drop the DFS ch & effectively your 5G/6 radio will essentially restart without it. Do yourself a solid favor & try maxing out your frequency at 80. Note: You can select auto & disable 160mHz(DFS)

That’s where it is for now. Just not sure what changed with the update, no interference, no radar, nothing. It’s been there for a couple years. It won’t even clear the channel for radar or whatever and won’t let me select channels on any of them. Auto is the only option. I’ll look through it again this weekend for some obscure setting I probably forgot about.

It could be a coincidence, I’ll probably leave it for a little while to see. The aggregation thing bugs me though, but both of the issues are only noticeable when moving large files or we have every device running plus gaming.

 

[Tech9]

It’s been there for a couple years.

DFS channels are not guaranteed. Some folks in Europe found they can no longer use DFS due to military activities in relation to Eastern Europe events. They also had no issues for years. If you want stable Wi-Fi - 36-48 or 149-161 @80MHz wide.

 

[Morac]

Did a dirty upgrade of my RT-AC88U from 386.5_2 to 386.7. Prior to doing so I unplugged the router and attached an ezOutlet3 (that powers router off it it locks up which happens now and then). I then upgraded.

Things seemed okay, but my August lock kept trying to renew its IP address over and over again. I checked the logs and it did so prior to upgrading, so I unplugged it and the router and plugged the router back in and then the August. It then grabbed a different IP address and worked. I’ve seen some devices simply not work with the assigned IP address until both the router and device are simultaneously powered off, but have no idea why that happens.

After this though my Ooma VOIP device wouldn‘t go online. Also I noticed my Apple Home traffic wasn’t working properly and devices kept losing their IPv6 address. I’ve seen that before. This sometimes happens after a reboot and another reboot fixes it, so that’s what I did and now everything is working. Not the smoothest upgrade though. I’m wondering if the RT-AC88U just isn’t that good of a router.