Beta Asuswrt-Merlin 386.5 Beta is now available

[RMerlin]

Asuswrt-Merlin 386.5 Beta is now available. This release introduces support for the RT-AC68U_V4 and GT-AXE11000 (both were originally planned for 386.4, but wifi issues with their GPLs forced both, to be delayed). This also merges with Asus's 386_46065 GPL code, and fixes a few issues.

The highlights:

• Merged with GPL 386_46065 (note that a number of its security fixes were already present in 386.4)
• Added support for the RT-AC68U V4. Just like with the original Asus firmware, support is implemented in a combined firmware image that supports both the older and newer models. That image might not work properly however when using Firmware Recovery Mode, in which case people should use a version older than 386.5.
• Added support for the GT-AXE11000 (without its ROG UI or VPN Fusion).
• Dnsmasq was reverted back to 2.85 in an attempt to improve its stability
• Avahi was updated to 0.8, and a few additional fixes were backported, which should resolve the incrementing hostname on some setups
• Miniupnpd was upgraded to 2.3.0.
• Fixed netatalk failing to load its modules, which was breaking Time Machine
• A number of fixes and improvements were implemented in Traditional QoS
• And a few other minor fixes and improvements, please view the changelog for more details

Things in need of testing:

• Everything on the RT-AC68U_V4 and GT-AXE11000
• Traditional QoS
• Time Machine on HND models

Please keep discussions on the topic of this specific beta release. Off-topic posts will be ignored, moved or deleted, depending on my mood at the moment.


Downloads are here.
Changelog is here.

 

[RMerlin]

Known issues:

• BWDPI and Flow Cache incompatibility on RT-AX68U and RT-AX86U (Compatibility issue with newer SDK for that platform, reverting bwdpi components as per Asus's suggestion)

 

[bbunge]

Smooth upgrade from the Alpha 2 on AX86U.

 

[heywire]

Anybody experiencing the known disconnection issues (especially affecting the AC86U hard, it seems) that have tested this. Did it solve your problem?

 

[jsbeddow]

Anybody experiencing the known disconnection issues (especially affecting the AC86U hard, it seems) that have tested this. Did it solve your problem?

I haven't experienced this issue, but I can confirm that the wireless driver for the RT-AC86U has not changed from 386.4 to any of the 386.5 versions.

 

[HorseCalledHorse]

I haven't experienced this issue, but I can confirm that the wireless driver for the RT-AC86U has not changed from 386.4 to any of the 386.5 versions.

That's interesting. Do we know which models are getting new wireless drivers?

 

[Ellenswamy]

Yay! I see the ax11000

update ax11000, updated wifi driver from Jan 25th. All looks good so far!

 

[Akore]

Smooth upgrade from Alpha 2 on a AC68U (main router) and a AC66U_B1 Node.

 

[banger]

Smooth upgrade from Alpha 2 to Beta on 2 AC68U.

 

[FLA_NL]

Dirty update from 386.4 to 386.5 beta1, don't notice any issues.

 

[shabbs]

Let's GO! Updating APs now...

EDIT: All three APs upgraded filthily from Alpha2... no issues so far. All devices reconnected. Nest cams behaving and stable so far. IOT devices all back on-line. So far so good. Will do another set of restarts later and then monitor for 24hr.

 

[ElmerFudd]

Just upgraded my AX88U to this Beta from 386.4 with no issues.

@RMerlin It appears the merge of GPL 386_46065 fixed all the problems I had with old TP-LINK smart being constantly dissociated with the 2.4GHZ band and thus becoming unusable with frequent disconnects. I wish I could remember the other uses who had the same problems but it would be worth getting the word out on this. Just tested its one of my old LB110 that has been in a box for awhile and was pleasantly surprised that it works no issues. Note:

1) The bulb has the same firmware that it did when I had problems with it.
2) The WIFI settings are the same as when the bulb disconnected.

 

[AntonK]

A vile update from Alpha2. All working perfectly.

 

[octopus]

I have just updated my two RT-AX86U and RT-AX58U with no problem.
Only icon on aimesh nod is still missing, wrong path.

GEThttps://nw-dlcdnet.asus.com/plugin/productIcons/RT-AX86U-2.png
[HTTP/2 404 Not Found 179ms]

https://nw-dlcdnet.asus.com/plugin/productIcons/RT-AX86U-2.png

Should be:

https://nw-dlcdnet.asus.com/plugin/productIcons/RT-AX86U.png

 

[RMerlin]

Only icon on aimesh nod is still missing, wrong path.

That's Asus, not mine.

 

[XIII]

Upgraded 386.5 Alpha 2 to 386.5 Beta (after only one day...) on my AC86U.

Noticed that the WAN IP is an internal 192.168.x.y address on the main page (instead of the external address), which makes sense, because I have a double NAT, since I recently upgraded to Fiber and need their modem in front of my ASUS router. I guess I did not notice this before (for example when installing Alpha 2 yesterday), since it somehow stuck out now... (Or has this changed?)

 

[heywire]

Upgraded 386.5 Alpha 2 to 386.5 Beta (after only one day...) on my AC86U.

Noticed that the WAN IP is an internal 192.168.x.y address on the main page (instead of the external address), which makes sense, because I have a double NAT, since I recently upgraded to Fiber and need their modem in front of my ASUS router. I guess I did not notice this before (for example when installing Alpha 2 yesterday), since it somehow stuck out now... (Or has this changed?)

Did you remember to set the Fiber modem in "Bridge Mode"?

 

[Smokey613]

Updated both AC86Us and so far working fine.

 

[Pergola Fabio]

I haven't experienced this issue, but I can confirm that the wireless driver for the RT-AC86U has not changed from 386.4 to any of the 386.5 versions.

We're there wireless issues on the 86u unit on the 386.4 release before with 2.4 , like many people complaining? Or was it specific to other models only?

 

[HorseCalledHorse]

We're there wireless issues on the 86u unit on the 386.4 release before with 2.4 , like many people complaining? Or was it specific to other models only?

I'm guessing it was the AX models only. I run an RT-AC86U and don't have any IoT devices so I didn't pay too much attention to those discussions. The only 2.4 device I have that's ever given me trouble (constant disconnects) is a Dolphin robotic pool cleaner and I always figured that was an issue with range rather than the router's wi-fi driver.