ASUS RT-AC86U firmware release 3.0.0.4.384.45713

[Latzz]

I was hoping to get someone to clearly let me know if the the dcd crashes stopped or are continuing to happen with this firmware 45713. There have been entries of logs being clear but I cannot determine if those people were getting the dcd crashes prior. I was trying to get this answer to know if it would be worth while to perform a factory reset.

AiProtection, QOS, Game Boost turned ON. Logs are clean with minimal entries. Network map and traffic reports are working as intended (finally). Performed factory reset after installing the firmware.

 

[WET]

AiProtection, QOS, Game Boost turned ON. Logs are clean with minimal entries. Network map and traffic reports are working as intended (finally). Performed factory reset after installing the firmware.

Thanks for posting. I flashed RMerlin's 384.11 beta, dcd crashes continued, kept playing with settings, if I turn off AI Protection and Adaptive QOS, dcd crashes stop but as I stated earlier I would rather have them on. Changed log posting levels that makes no difference. Then with AI Protection & Adaptive QOS on, my router setup as it usually is, for a day I had no dcd crashes but during this day I would time out on a dns lookup (I assume) to restricted websites rather than get a security warning popup immediately returned. So I performed a factory reset, reloaded everything from scratch all went back to normal operation, however, the dcd crashes came back.

Looks like it is something unique to my setup. Hopefully I'll stumble over

FYI, I do run AMTM, Diverson & Pixelserve. When I did the factory reset I went thru L&LD's suggested procedure on formatting jump drive loading AMTM, swap file, disk check, etc.

I do appreciate the posts people are making to let me know that their logs are clean / no longer getting the dcd crashes.

Edit: I changed log level to info once again & rebooted. I still received crashes but the first line of the crash identifying it as a dcd crash was not gone, all other lines of the crash there. Switching log level back to debug first line of crash reappears.

Log level at info:
May 1 20:53:13 kernel: pgd = ffffffc008f1d000
May 1 20:53:13 kernel: [00000000] *pgd=00000000080b4003, *pud=00000000080b4003, *pmd=0000000008183003, *pte=0000000000000000
May 1 20:53:13 kernel: CPU: 1 PID: 19370 Comm: dcd Tainted: P O 4.1.27 #2
May 1 20:53:13 kernel: Hardware name: Broadcom-v8A (DT)
May 1 20:53:13 kernel: task: ffffffc014ba6a80 ti: ffffffc008104000 task.ti: ffffffc008104000
May 1 20:53:13 kernel: PC is at 0xf720af44
May 1 20:53:13 kernel: LR is at 0x1dc74
May 1 20:53:13 kernel: pc : [<00000000f720af44>] lr : [<000000000001dc74>] pstate: 600e0010
May 1 20:53:13 kernel: sp : 00000000ffbbee48
May 1 20:53:13 kernel: x12: 000000000009ff08
May 1 20:53:13 kernel: x11: 00000000f64ff024 x10: 00000000000a02ac
May 1 20:53:13 kernel: x9 : 00000000f64ff8a4 x8 : 00000000000a0764
May 1 20:53:13 kernel: x7 : 00000000f64ff8dc x6 : 00000000000a075e
May 1 20:53:13 kernel: x5 : 0000000000000000 x4 : 00000000f64ff888
May 1 20:53:13 kernel: x3 : 0000000000000000 x2 : 00000000ffbbee24
May 1 20:53:13 kernel: x1 : 000000000007c66c x0 : 0000000000000000

Log level at debug:
May 2 07:01:11 kernel: dcd[16945]: unhandled level 3 translation fault (11) at 0x00000000, esr 0x92000007
May 2 07:01:11 kernel: pgd = ffffffc017724000
May 2 07:01:11 kernel: [00000000] *pgd=00000000082ce003, *pud=00000000082ce003, *pmd=00000000170a6003, *pte=0000000000000000
May 2 07:01:11 kernel: CPU: 1 PID: 16945 Comm: dcd Tainted: P O 4.1.27 #2
May 2 07:01:11 kernel: Hardware name: Broadcom-v8A (DT)
May 2 07:01:11 kernel: task: ffffffc014a481c0 ti: ffffffc00593c000 task.ti: ffffffc00593c000
May 2 07:01:11 kernel: PC is at 0xf7322f44
May 2 07:01:11 kernel: LR is at 0x1dc74
May 2 07:01:11 kernel: pc : [<00000000f7322f44>] lr : [<000000000001dc74>] pstate: 600e0010
May 2 07:01:11 kernel: sp : 00000000ff9595c8
May 2 07:01:11 kernel: x12: 000000000009ff08
May 2 07:01:11 kernel: x11: 00000000f65ff024 x10: 00000000000a02ac
May 2 07:01:11 kernel: x9 : 00000000f65ff8a4 x8 : 00000000000a0764
May 2 07:01:11 kernel: x7 : 00000000f65ff8dc x6 : 00000000000a075e
May 2 07:01:11 kernel: x5 : 0000000000000000 x4 : 00000000f65ff888
May 2 07:01:11 kernel: x3 : 0000000000000000 x2 : 00000000ff9595a4
May 2 07:01:11 kernel: x1 : 000000000007c66c x0 : 0000000000000000
what it is.

 

[rromeroa]

Hi,

in this release, udpxy is not starting at boot time in my AC86U. I have Movistar IPTV profile with udpxy at 4022 port but udpxy daemon is not starting.

 

[L&LD]

Hi,

in this release, udpxy is not starting at boot time in my AC86U. I have Movistar IPTV profile with udpxy at 4022 port but udpxy daemon is not starting.

Known issue.

 

[monaro-ds]

strange problem, 86u is wireless node , after update to 45713 devises connected to it (over WiFi) can not see internet... restart helps for couple of days

 

[OzarkEdge]

strange problem, 86u is wireless node , after update to 45713 devises connected to it (over WiFi) can not see internet... restart helps for couple of days

Strange problems suggest a need to reset and reconfigure from scratch.

OE

 

[follower]

strange problem, 86u is wireless node , after update to 45713 devises connected to it (over WiFi) can not see internet... restart helps for couple of days

Same here. Firmware 45713 has AiMesh issue. I don't know what ASUS is doing.

https://www.snbforums.com/threads/asus-rt-ac68u-firmware-version-3-0-0-4-384-45713.56052/page-2

 

[Latzz]

Update from my last post#81

Firmware 384.45713 ran for 16 days without issues, except for the 2-way-IPS page had no entries, which seemed strange. For the first time, network devices were displayed properly. Also had ipv6, AiProtection and QOS etc enabled.

However, a day back was configuring OpenVPN clients and testing out stuff. For some reasons, the system log was showing a start service vpnclient1 every minute, even after all the VPN entries were deleted. Decided to reboot the router as a fix.

After reboot, lost wifi on both the 2.4Ghz and 5Ghz radios and the WAN led light was off. Seemed exactly what happened earlier when I updated the router to 45713.

WPS factory reset > simple configure > WPS factory reset > simple configure > upload a new copy of 45713 firmware > simple configure > WPS factory reset

and a full production system configuration after that. Everything now seems to be working normally.

My questions and concerns are either,
1. Possibility of a failing hardware (router is just over a year old), or
2. Something weird with 45713

Would be grateful if anyone can clue in to what is happening.

 

[bitmonster]

Update from my last post#81

Firmware 384.45713 ran for 16 days without issues, except for the 2-way-IPS page had no entries, which seemed strange. For the first time, network devices were displayed properly. Also had ipv6, AiProtection and QOS etc enabled.

However, a day back was configuring OpenVPN clients and testing out stuff. For some reasons, the system log was showing a start service vpnclient1 every minute, even after all the VPN entries were deleted. Decided to reboot the router as a fix.

After reboot, lost wifi on both the 2.4Ghz and 5Ghz radios and the WAN led light was off. Seemed exactly what happened earlier when I updated the router to 45713.

WPS factory reset > simple configure > WPS factory reset > simple configure > upload a new copy of 45713 firmware > simple configure > WPS factory reset

and a full production system configuration after that. Everything now seems to be working normally.

My questions and concerns are either,
1. Possibility of a failing hardware (router is just over a year old), or
2. Something weird with 45713

Would be grateful if anyone can clue in to what is happening.

Thanks, so you think it may be related to my existing issue - oh I hope it's not a hardware issue! How do I factory reset it? Will that wipe all logs and traffic stats? Do I need to reinstall firmware after that or is a factory reset and go through settings ok to do..

https://www.snbforums.com/threads/rt-ac86u-not-booting-stuck-on-wlan-power-lights.56557/

 

[Latzz]

Looked at your post linked. In my case, the power, 2.4Ghz and 5Ghz led lights were on (just no WAN led light).

Factory reset. Unplug the power jack at the back of the router. While holding the WPS button plug back the power jack and do not release for 30 seconds. All the led lights will be off. Then switch off and on back the router power and it will be in factory state.

 

[bitmonster]

Looked at your post linked. In my case, the power, 2.4Ghz and 5Ghz led lights were on (just no WAN led light).

Factory reset. Unplug the power jack at the back of the router. While holding the WPS button plug back the power jack and do not release for 30 seconds. All the led lights will be off. Then switch off and on back the router power and it will be in factory state.

Thanks. Did you lose traffic stats or just needed to reconfigure? If that's the case that's no biggie. Probably due for a settings spring clean anyway although I imagine I'd have to set up VPN etc again. Beats hardware issues though.

 

[Latzz]

Factory reset kept the traffic stats etc. It just clean out the settings.

From my experiences dealing with ASUS support, they had always after consulting with level 2 support, if the standard diagnostics and fixes do not work, is to ask that you re-update the firmware and if this fails, they will suggest sending in the router for inspection and warranty replacement.

 

[L&LD]

Factory reset kept the traffic stats etc. It just clean out the settings.

From my experiences dealing with ASUS support, they had always after consulting with level 2 support, if the standard diagnostics and fixes do not work, is to ask that you re-update the firmware and if this fails, they will suggest sending in the router for inspection and warranty replacement.

Was that with the GUI reset method? Was the 'Initialize all settings..." checkbox checked?

Or, was the NVRAM erase process used in your case?

 

[WhiteDogBe]

Here is a download link for new firmware 3.0.0.4.384.45717.

 

[XIII]

Download link for new firmware 3.0.0.4.384.45717.

Are you sure? The filename ends with 713, not 717.

EDIT: Changing the 3 into a 7 in the URL seems to help (now; not when I posted my reply).

 

[WhiteDogBe]

Are you sure? The filename ends with 713, not 717.

EDIT: Changing the 3 into a 7 in the URL seems to help (now; not when I posted my reply).

Yeah sorry about that, edited the link. It's not on the ASUS site yet. Have it running for a few hours now as part of an AiMesh group, no issue so far. I'll assume the update contains the same security fixes as for the other models it was released for today.

 

[fastoy]

Here is a download link for new firmware 3.0.0.4.384.45717.

Since this is a ASUS RT-AC86U thread, does this firmware apply to ASUS RT-AC86U?

 

[OzarkEdge]

Since this is a ASUS RT-AC86U thread, does this firmware apply to ASUS RT-AC86U?

Notice the '86U' in the linked URL and filename.

OE

 

[Smokindog]

I tried to apply that linked firmware to my 86U and it refused it as "wrong firmware for device" or something to that effect.

I did pull the 45717 firmware for the RT-AC3100 from the ASUS site and it installed without a hitch on both my RT-AC3100 routers. I'll wait until I see it listed on the RT-AC86U support page which still shows 45713 as the most recent for that specific device.

https://www.asus.com/us/Networking/RTAC68U/HelpDesk_BIOS/

 

[dave14305]

I tried to apply that linked firmware to my 86U and it refused it as "wrong firmware for device" or something to that effect.

I did pull the 45717 firmware for the RT-AC3100 from the ASUS site and it installed without a hitch on both my RT-AC3100 routers. I'll wait until I see it listed on the RT-AC86U support page which still shows 45713 as the most recent for that specific device.

https://www.asus.com/us/Networking/RTAC68U/HelpDesk_BIOS/

That’s the AC68U page, not 86U. Common mistake.