What's new

Release Asus AC86U New Firmware - 3.0.0.4.386_40451-g30f1b6c

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I am having random crash issue on 384.19, with factory reset for multiple times and still same thing, then I suspect was my router issue and got RMAed with a new one a week ago. Still having random restart and crashlog 3 days ago.
Seriously I have no clue what went wrong, and I think I should give it a try for official 386.
There is people report for ac86u crashlog issue for 384.19 in merlin forum as well. So I guess it's not just my case?

I had issues with 384.19 too, hence why I went back to stock.
 
I had issues with 384.19 too, hence why I went back to stock.
I did just went back to stock 386 and factory reset everything, if its appears to be stable then it will be an old 384 fw issue.
The wait for merlin 386 is just far too long for me for now, lets see hows goin for the final 386.1.
 
Hello I am new member here.

Question for AC86U owner has the latest release installed.

 
Last edited:
@alex1236hk the RT-AC86U has been stable on all RMerlin firmware I have used on it for the last 18 months or so.

What did you do to correct any issues you faced?

I tried looking into your past posts, but I didn't come away with anything concrete while skimming them.

At the minimum, 384.19_0 is still very stable for many of my customers. Many have also jumped to the 386.1 Beta 3 without issues either though.

384.19_0 has been very stable for me as well on four AC86Us.

I think that Merlin's 386.1 release will have the latest ASUS 386 code. I'm waiting for beta4 which I expect will have it based on what Merlin has said in the last week.
 
Hello I am new member here.

Question for AC86U owner has the latest release installed.

I have run Asus 386_40451 and am now on Merlin 386.1 beta 3. Both run very well for me. I am on Merlin for the added features such as DoT, DNS filtering and expanded DDNS choices. Yes, the beta 3 has a couple of issues which can be ignored or overcome, such as CPU temperature rise.
If you are not experienced with fiddling with computer settings stick with Asus stock firmware and when a new version is released the router will upgrade itself.
 
I have run Asus 386_40451 and am now on Merlin 386.1 beta 3. Both run very well for me. I am on Merlin for the added features such as DoT, DNS filtering and expanded DDNS choices. Yes, the beta 3 has a couple of issues which can be ignored or overcome, such as CPU temperature rise.
If you are not experienced with fiddling with computer settings stick with Asus stock firmware and when a new version is released the router will upgrade itself.

Hi bbunge,
about the issues, I don't think that it's safe to ignore the CPU temperature: we're talking about an average of 15/20 degrees above the 386.40451 stock firmware temperature, with spikes (reported by many people in Merlin's beta firmware thread) of 100 degrees with CPU forced shutdown.

The issues of Traffic Analyzer Statistics, Traffic Monitor and QoS Bandwidth Monitor are annoying too. These tools don't work at all, reporting completely wrong data.

In my personal opinion, the stock 386.40451 is the more stable and the only fully functional 386 firmware out there. I like Merlin's firmwares very much, but for now I will stay on stock 386.40451 until all issues of the newer versions will be resolved (hoping that they will be resolved...).

With stock 386.40451 I have only one issue that is the flooding of the system log with messages like the one below:

Jan 9 17:02:00 conn_diag[1290]: CONNDIAG: <ETHINFO>C>myrouteripaddress>myroutermacaddress>BH>-1>-1>460445.1>5289501.3
Jan 9 17:02:00 conn_diag[1290]: CONNDIAG: Built the SQL file of conn_diag.

I've reported this issue to Asus but, in my opinion, it's more safe to ignore this issue than the issues of the newer beta releases.

Thank you.

Bye.
 
new firmware

ASUS RT-AC86U Firmware version 3.0.0.4.386.41634
- Fixed Lets encrypt not working properly.
- Added IPTV supports for specific region.
- Fixed parental control issues.
- Fixed pre-auth RCE chain vulnerability. Special thanks for Robert Chen.
 
Wake me up when we hit 386.2.
 
Installed the newest update stock firmware ASUS RT-AC86U Firmware version 3.0.0.4.386.41634


Uptime0 days 23 hour(s) 1 minute(s) 39 seconds

No problems so far. Heck the Traffic Analyzer even works now.
 
I have 2 AC86U running in aiMesh mode. All was good until Firmware auto updated to 3.0.0.4_386_40451 on 10/20/2020. The router crashed and began auto cycling on-off. All traffic (wifi and ethernet) is disconnected and then reconnected in approx 2 minute cycles. Ultimately, I diagnosed that HP printers connecting to wifi were triggering the crashes. Connecting the HP printers via ethernet operates correctly. I disabled the aiMesh mode, factory reset, spoke with Asus tech support, etc. The router crash occurs regardless of assigning static IP or using DHCP with the HP printers in WIFI mode.

Printers are HP9018 (both new in past 3 months) and HP8600 (both from 2012). Any single or combination of these 4 printers causes network fail). HP8600 connect on 2g and HP9018 have been connected on 2g and 5 g with same issues.

Asus recommend rolling back to firmware 3.0.0.4_384_81992 (July 9/2020) ... while that worked fine , the firmware auto updates that night , so that is not a workable solution.

Attached is this morning's system log file

HELP
 

Attachments

  • syslog 21-01-21 1013 am.txt
    318 KB · Views: 100
Asus recommend rolling back to firmware 3.0.0.4_384_81992 (July 9/2020) ... while that worked fine , the firmware auto updates that night , so that is not a workable solution.

I'm running 3.0.0.4.384_82072, which doesn't auto-update
 
I'm running 3.0.0.4.384_82072, which doesn't auto-update

Alan, thanks for the feedback. Unfortunately, 3.0.0.4.384_82072 was released Oct 22, 2020 and causes the same behaviour as 3.0.0.4_384_81992 ( released July 9/2020)

Also My router auto-updates and I have found no settings to disable auto-update.
 
Last edited:
Alan, thanks for the feedback. My router auto-updates and I have found no settings to disable auto-update.

I believe it's written into the firmware without any user option.
some versions auto-update, some don't. 82072 doesn't.
 
I have 2 AC86U running in aiMesh mode. All was good until Firmware auto updated to 3.0.0.4_386_40451 on 10/20/2020. The router crashed and began auto cycling on-off. All traffic (wifi and ethernet) is disconnected and then reconnected in approx 2 minute cycles. Ultimately, I diagnosed that HP printers connecting to wifi were triggering the crashes. Connecting the HP printers via ethernet operates correctly. I disabled the aiMesh mode, factory reset, spoke with Asus tech support, etc. The router crash occurs regardless of assigning static IP or using DHCP with the HP printers in WIFI mode.

Printers are HP9018 (both new in past 3 months) and HP8600 (both from 2012). Any single or combination of these 4 printers causes network fail). HP8600 connect on 2g and HP9018 have been connected on 2g and 5 g with same issues.

Asus recommend rolling back to firmware 3.0.0.4_384_81992 (July 9/2020) ... while that worked fine , the firmware auto updates that night , so that is not a workable solution.

Attached is this morning's system log file

HELP

Have you tried the current release 41634?

OE
 
Yes, current release 3.0.0.4_386_41634 , released on Jan 11, 2021 causes the same behavior as described in my original post
 
Yes, current release 3.0.0.4_386_41634 , released on Jan 11, 2021 causes the same behavior as described in my original post

I'd wire the printers and wait. Maybe there's an HP update for them.

OE
 
I have 2 AC86U running in aiMesh mode. All was good until Firmware auto updated to 3.0.0.4_386_40451 on 10/20/2020. The router crashed and began auto cycling on-off. All traffic (wifi and ethernet) is disconnected and then reconnected in approx 2 minute cycles. Ultimately, I diagnosed that HP printers connecting to wifi were triggering the crashes. Connecting the HP printers via ethernet operates correctly. I disabled the aiMesh mode, factory reset, spoke with Asus tech support, etc. The router crash occurs regardless of assigning static IP or using DHCP with the HP printers in WIFI mode.

Printers are HP9018 (both new in past 3 months) and HP8600 (both from 2012). Any single or combination of these 4 printers causes network fail). HP8600 connect on 2g and HP9018 have been connected on 2g and 5 g with same issues.

Asus recommend rolling back to firmware 3.0.0.4_384_81992 (July 9/2020) ... while that worked fine , the firmware auto updates that night , so that is not a workable solution.

Attached is this morning's system log file

HELP
Just a thought, but check the WiFi direct settings in the HP gui for each printer. Best practice is for that to be disabled.
 
I have 2 AC86U running in aiMesh mode. All was good until Firmware auto updated to 3.0.0.4_386_40451 on 10/20/2020. The router crashed and began auto cycling on-off. All traffic (wifi and ethernet) is disconnected and then reconnected in approx 2 minute cycles. Ultimately, I diagnosed that HP printers connecting to wifi were triggering the crashes. Connecting the HP printers via ethernet operates correctly. I disabled the aiMesh mode, factory reset, spoke with Asus tech support, etc. The router crash occurs regardless of assigning static IP or using DHCP with the HP printers in WIFI mode.

Printers are HP9018 (both new in past 3 months) and HP8600 (both from 2012). Any single or combination of these 4 printers causes network fail). HP8600 connect on 2g and HP9018 have been connected on 2g and 5 g with same issues.

Asus recommend rolling back to firmware 3.0.0.4_384_81992 (July 9/2020) ... while that worked fine , the firmware auto updates that night , so that is not a workable solution.

Attached is this morning's system log file

HELP
well, my oj 6978 runs fine wirelessly with a static ip. will hold off moving up to this current rel for now though.
. . . certainly appreciate the post
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top