RT-AC86U .20287?

[mogulman]

Not on the website, but I used the check button and the firmware upgrade button. Both my RT-AC86u and rt-ac1900p upgraded to 20308 at the same time. It was a miracle!

 

[Odkrys]

Version 3.0.0.4.384.20308

ASUS RT-AC86U Firmware version 3.0.0.4.384.20308
Security fixed
- Fixed Smart Sync Stored XSS vulnerabilities. Thanks fo Guy Arazi's contribution.
- Fixed CVE-2018-5721 Stack-based buffer overflow

Bug fixed
- Fixed PPPoE NAT throughput issue.
- Fixed client icon modification issue when client name includes special characters.
- Fixed error for new firmware available notification.
- Fixed AiMesh onboarding issue for Korea SKU
- Fixed AiMesh node shows offline in the GUI even it still connect to AiMesh router.
- Increased OpenVPN server throughput.
- Fixed 5GHz downlink throughput drop problem.
- Fixed dual wan related issues.


Please unzip the firmware file first then check the MD5 code.
MD5: d3edbb6ce2274ea99ee219f232d2c12d

http://dlcdnet.asus.com/pub/ASUS/wireless/RT-AC86U/FW_RT_AC86U_300438420308.ZIP

 

[Volfi]

You can download it manually here: http://dlcdnet.asus.com/pub/ASUS/wireless/RT-AC86U/FW_RT_AC86U_300438420308.ZIP

It did not show for me, even not for autoupdate.

 

[Locoblade]

I've updated my 86U and it has indeed fixed the AiMesh issue with my 66U-B1 not connecting so I'm a happy bunny. I've also updated the 66U-B1 to the same revision but now when checking the firmware tab it automatically shows the firmware update progress bar although I don't think it's actually updating (isn't this the issue they're claiming is fixed compared to 20287?)

 

[Broken Hope]

Looks like it fixes an issue I've been seeing on my iPhone where the max link would drop from 866 to 433 for no reason.

 

[128bit]

my 86u network map still has bugs. perhaps maybe even a new one as at least 2 devices on the 2.4 band are now displayed as wired. one seems to have a problem "dnsmasq-dhcp[793]: not giving name localhost. . .", the other connects fine. both are on a guest network.

 

[Locoblade]

Do you find the network map in the sidebar sometimes crashes you out of the whole admin console if you try to edit a device to change the icon etc? I had it happen a few times on 10007 and still get it on 20308

 

[silluine]

i updated yesterday but there are some problems. After each reboot it is loosing QoS mode(web-media etc) and also wireless schedule settings. Need to set both again and again.. Anybody have these problems?

 

[128bit]

Do you find the network map in the sidebar sometimes crashes you out of the whole admin console if you try to edit a device to change the icon etc? I had it happen a few times on 10007 and still get it on 20308

i've not experienced any crash per se, just inaccuracy. i also have that problem with "dnsmasq-dhcp[792] / localhost" that's been reported. the device this time is a samsung vacuum. while i've read about the remedy, this device doesn't allow me that kind of edit to exact a fix.

 

[maxbraketorque]

Not much discussion about 20308. It must be working well for everyone.

 

[Gingernut]

i updated yesterday but there are some problems. After each reboot it is loosing QoS mode(web-media etc) and also wireless schedule settings. Need to set both again and again.. Anybody have these problems?

Yes, this also happens to me.

 

[Datalink]

Yes, it looks like a reboot will wipe out both 2.4 and 5 Ghz wifi time settings. As a result, both networks are available at all times.

One other problem that I haven't checked on is the MAC address manual entry located in the WAN .... Internet Connection tab. I used this on the 68U to change the MAC address with the 380.xxxx firmware versions loaded. That would run a check and indicate whether or not the MAC address was valid. On an 86U with 384.1007 loaded, the clone address would work, but the MAC address manual entry would not. It would look like it worked, but, after a reboot, you couldn't get back into the modem to change anything. I ended up having to run a factory reset to get back into the modem. I haven't checked this on 384.20308 but its on my list of things to do. You can get around this by changing a pc/laptop's MAC address and then cloning that address, but, it was much simpler before the firmware change to the .384 versions.