Release Asuswrt-Merlin 386.5 is now available

[beastobadness]

I had this problem sense the firmware got bigger on my ac68u, I think it’s because ram is too low to accept the file as every time I tried it with my ram low it would do that (even if I had swap file)

so if I factory reset my router , clearing all scripts and things it would then take the new firmware

this is only my findings. I’m far from a professional like some of the others on here. But I think it’s what’s happening

Think I am going to have to try this also.

Just had major issues on my RT-AC68U coming from 386.4, flash failed which killed my internet connection and usb but was still left on 386.4. Run a reboot which brought it back, then tried again, this time the firmware update failed and router went into bootloop/rescue mode... power light began to flash constantly. Tried a hard reset (using WPS button method) and full reset (using the reset button method) which did not work.

In the end I was forced to download the Asus restoration tool and flash directly via ethernet after placing the router in recovery mode, tried recovering with 386.5 first and it failed again!, then tried with 386.4 and the restore worked first time.

@RMerlin could the size of the new firmware file (>90 MB) be causing the flash to fail, especially with the meagre resources the AC68U and such have?

 

[BreakingDad]

Known issues:

• Internet reported as disconnected
  Your Internet monitoring configuration is most likely incorrect. Reset it to its default settings by running these over SSH:
  
  

nvram set dns_probe_content="131.107.255.255 112.4.20.71 fd3e:4f5a:5b81::1"
nvram set dns_probe_host="dns.msftncsi.com"
nvram commit


Can someone explain what this dns probe thing is and why ping doesn't work now for checking the internet connection? @dave14305 @RMerlin ? Thank you for your help.

 

[kakaiba]

On a New Years day 386.4 was released.
I upgraded my AC86u with it and after a few days downgraded back to 386.3.2 because of a faulty WiFi driver - constant line drops on 2.4 GHz.
As you noticed, WiFi driver in 386.5 cause the same problems. Looks like the problem is not solved. Wonder if driver is the same.
Looking forward to hear from other users here to confirm/deny this statement.
Would be very happy, when other users confirm a 100% working WiFi with 386.5 on AC86U. Else I'll stay on 386.3.2 until this failure is solved.

I had it the other way around. 2.4 GHz connections became more stable (Google Nest Mini, IP Cameras, Smart Plugs) and overall RAM usage was lower.

@zd59 Try checking for any interferences and/or change to less crowded channels.

Additionally, try to change the Tx power adjustment to Good instead of Performance in Wireless > Professional.

 

[technofox01]

Anyone else having problems with 2.4 Ghz and 5 Ghz bands on the RT-AX58U?

My WiFi literally cuts out every few minutes. I switch back to 386.4 and now everything is stable again.

 

[John Fitzgerald]

Anyone else having problems with 2.4 Ghz and 5 Ghz bands on the RT-AX58U?

My WiFi literally cuts out every few minutes. I switch back to 386.4 and now everything is stable again.

Rock solid, no issues.

 

[underdose]

Upgraded my AX58U from alpha2 to stable right away without applying any known best-practices (a.k.a. dirty upgrade) and no issues so far (~30 hours uptime): all scripts in my signature work as expected, no unusual entries in the syslog, all devices (iPhones, iPad, MacBooks Amazon FireTV Stick, Android TV, air conditioner) work flawlessly.

 

[technofox01]

Upgraded my AX58U from alpha2 to stable right away without applying any known best-practices (a.k.a. dirty upgrade) and no issues so far (~30 hours uptime): all scripts in my signature work as expected, no unusual entries in the syslog, all devices (iPhones, iPad, MacBooks Amazon FireTV Stick, Android TV, air conditioner) work flawlessly

I wonder what could be the cause then. Are you using AImesh?

I wonder if that could be the issue.

 

[RMerlin]

@RMerlin could the size of the new firmware file (>90 MB) be causing the flash to fail, especially with the meagre resources the AC68U and such have?

Asus' implementation specifically only stores the model-specific portion in /tmp, so it doesn't require more RAM than before to upgrade. That's why I ultimately accepted to also go with a combined firmware image.

Can someone explain what this dns probe thing is and why ping doesn't work now for checking the internet connection? @dave14305 @RMerlin ?

As the message reflects, this probe is used by the router to determine if there is a working Internet connection. Windows uses the exact same method, with the same server to do the same.

Doing a lookup is more reliable than a ping, because a ping can get filtered along the way if a firewall or something drops ICMP packets. DNS lookups on the other end is an essential service, so it will not get filtered.

 

[BreakingDad]

As the message reflects, this probe is used by the router to determine if there is a working Internet connection. Windows uses the exact same method, with the same server to do the same.

Doing a lookup is more reliable than a ping, because a ping can get filtered along the way if a firewall or something drops ICMP packets. DNS lookups on the other end is an essential service, so it will not get filtered.

Hi Eric,

Thank you for your reply, I was a bit concerned over the IP's - the first one is Microsoft, however the 2nd one is to "China Mobile" and unsure of the 3rd one.

Am I worrying about nothing?

Thank you.

Matt

 

[technofox01]

Rock solid, no issues.

I appreciate your response. I just upgraded via the web interface. Did you have to factory reset the router first or just upload the new firmware and let it fly?

Also, are you using AImesh?


I am wondering if that is the cause of the issue.

 

[dave14305]

Am I worrying about nothing?

Yes, because all it does is resolve the name. No connections are made to the IPs returned. If you were in China, you might receive the Chinese IP, so the router has to account for that possibility.

 

[BreakingDad]

Yes, because all it does is resolve the name. No connections are made to the IPs returned. If you were in China, you might receive the Chinese IP, so the router has to account for that possibility.

Thank's Dave / Eric , appreciate the help as always.

 

[Wolfclaw]

RT-AX86U dirty flash from 386.5 Beta no issues

 

[Incubus32]

Okay have to report that my previous problem went back after installing 386.5 on my ASUS RT-AX86U Random internal packet loss.

This issue was so persistent using firmware versions 386.4 386.5 B1 and B2.

But I somehow managed to fix it by turning off all TM stuff.

Now the issue is back with 386.5 official release.

Can someone link me the 386.5 beta 2 please? I have already deleted it and it wasn't in the one drive that Erick uploaded couple of days ago.

Many thanks!

 

[Incubus32]

Asuswrt-Merlin 386.5 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 to this release). This also merges with Asus's 386_46065 GPL code, and fixes a few issues.

The highlights of this release:

• 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).
• Fixes issues related to the Trend Micro BWDPI engine on the RT-AX68U and RT-AX86U.
• 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.
• 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

Please keep discussions in this thread on this specific release. General support requests should be posted in a separate thread.

This thread will be locked once the post-release feedback has quieted down.


Downloads are here.
Changelog is here.

Hi Erick, is this changed from the 386.5 beta 2 to the official 386.5 release?

Experiencing random internal packet loss after installing the official release. Looks like TM stuff is still gathering data even it's already off

Is there any chance you could send me the Beta 2 please? Thank you!

 

[ColDen]

Tell me what is your AC86U temperature on the new firmware 386.5 ? I have a high temperature of 85 degrees at 386.4! On earlier firmware, the temperature did not exceed 72 degrees.

53°C - 57°C - 72°C
My router do not have any fan and is in an open cabinet in a room at 21°C.

 

[KOSU]

Configuration : RT-AC68U
I upgraded from 386.3_2 to 386.5

I have a VPN Server - OpenVPN serwer 1 configured. It is working fine but till the router restart. When the router needs to be restarted, using Reboot Scheduler or after a power failure, an OpenVPN won't startup.

It hangs on the step: Export OpenVPN configuration file.

It saying to wait when the file will be ready, but it never is. The way to run OpenVPN again is to turn it OFF and again ON manually.

no issue on 386.3_2.

Do I need to do some adjustments onw my router, or I need to wait for the next FW release ?

 

[zd59]

I had it the other way around. 2.4 GHz connections became more stable (Google Nest Mini, IP Cameras, Smart Plugs) and overall RAM usage was lower.

@zd59 Try checking for any interferences and/or change to less crowded channels.

Additionally, try to change the Tx power adjustment to Good instead of Performance in Wireless > Professional.

Sorry kakaiba, but your suggestion is proven useless on previous 386.4 FW. Countless posts here points to faulty WiFi FW.
Is I stated earlier, 386.3.2 works excellent in my environment and no adjustments are needed.
Looks like 386.5 FW inherited that faulty WiFi FW from 386.4.

Again I kindly ask owners of AC86U to report the state of 2.4 GHz WiFi with 386.5 - working or faulty as in previous FW.

 

[Shonk]

I compiled a build last night
anyone else getting this on rt-ac88u

Firmware Version	386.5
Firmware Build	Fri Mar 4 01:23:18 UTC 2022 shonk@f3ffaee

Mar  4 01:41:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 01:51:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 02:01:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 02:11:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 02:21:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 02:31:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 02:41:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 02:51:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 03:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 03:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 03:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 03:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 03:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 03:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 04:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 04:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 04:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 04:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 04:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 04:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 05:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 05:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 05:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 05:31:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 05:41:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 05:51:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 06:01:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 06:11:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 06:20:50 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 06:20:50 miniupnpd[1706]: addnatrule() : chain MINIUPNPD not found
Mar  4 06:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 06:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 06:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 06:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 07:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 07:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 07:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 07:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 07:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 07:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 08:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 08:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 08:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 08:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 08:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 08:51:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 09:01:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 09:11:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 09:21:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 09:31:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 09:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 09:51:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 10:01:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 10:11:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 10:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 10:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 10:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 10:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 11:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 11:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 11:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 11:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 11:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 11:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 12:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 12:11:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 12:21:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 12:31:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 12:41:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 12:51:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 13:01:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 13:11:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 13:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 13:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 13:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 13:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 14:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 14:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 14:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 14:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 14:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 14:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 15:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 15:11:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 15:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 15:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 15:41:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 15:51:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 16:01:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 16:11:55 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 16:21:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 16:31:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 16:41:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 16:51:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:01:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:09:54 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:09:56 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:10:18 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:10:18 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:10:18 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:10:18 miniupnpd[1706]: addnatrule() : chain MINIUPNPD not found
Mar  4 17:10:26 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:11:03 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:11:03 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:11:03 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:11:03 miniupnpd[1706]: addnatrule() : chain MINIUPNPD not found
Mar  4 17:11:10 miniupnpd[1706]: chain MINIUPNPD not found
Mar  4 17:11:56 miniupnpd[1706]: chain MINIUPNPD not found

 

[RMerlin]

Hi Erick, is this changed from the 386.5 beta 2 to the official 386.5 release?

One webui change, and the documentation was updated. Your issue lies elsewhere.

f3ffaee039 (HEAD -> master, tag: 386.5, origin/master) Bumped version to 386.5 final
7a94360354 Updated documentation
d4de8f8d9e webui: restart ftpd + firewall when toggling FTP WAN access