ASUS RT-AC88U Firmware version 3.0.0.4.384.45149

[Squall Leonhart]

Version 3.0.0.4.384.45149 2018/12/05
45.88 MBytes

AiMesh
- Improved AiMesh stability
- Lyra, Lyra Mini, and Lyra Trio can be added as AiMesh node into RT-AC88U network.
Please refer to https://www.asus.com/support/FAQ/1038071 for more detail.

Security
- Fixed CVE-2018-14710, CVE-2018-14711, CVE-2018-14712, CVE-2018-14713, CVE-2018-14714. Thanks for Rick Ramgattie's contribution.
- Fixed AiCloud/ Samba account vulnerability. Thanks for Matthew Cundari's contribution.
- Fixed DoS vulnerability. Thanks for Ruikai Liu's contribution.
- Fixed CVE-2018-17020, CVE-2018-17021, CVE-2018-17022.
- Fixed stored XSS vulnerability. Thanks for Duda Przemyslaw's contribution.
- Updated OpenSSL library.

New Alexa skill and IFTTT actions
- Add Alexa skill “ ask ASUS ROUTER to report security status”
- Add Alexa skill “ ask ASUS ROUTER how many devices are online”
- Add IFTTT actions : Wake on LAN
- Add IFTTT actions : check new firmware available and upgrade
[Note] You have to upgrade the firmware version up to 3.0.0.4.384_45149 if you want to use these new Alexa skills and IFTTT actions.

Bug fixes and improvement
- Improved wireless stability.
- Modified “Dual Wan” user interface.
- Modified “Port Forwarding” user interface.
- Modified “Restore” user interface.
- Fixed GUI bugs on user feedback page.
- Fixed “Adaptive QoS” bugs.

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

https://dlcdnets.asus.com/pub/ASUS/wireless/RT-AC88U/FW_RT_AC88U_300438445149.zip

 

[Ryu Connor]

This release finally works right for configuration of media bridge mode. For nearly a year the initial configurator after a factory reset would not properly ask for a username and password during media bridge configuration, resulting in the device becoming stuck in a boot loop.

This release does have a UI bug. In media bridge mode, the device reports that the 2.4GHz radio is connected to ASUS_C0_2G along side the name of the real connected 5GHz network. The 2.4GHz radio isn't even enabled in my configuration, I'm connected to a 5GHz network that is properly listed and named.

The last good firmware I could use, 382 (and even older) did not exhibit this harmless quirk of bad information.

 

[Squall Leonhart]

This firmware is allowing devices to receive a dhcp address before they have even authenticated.

 

[Gregory Phillips]

I just installed it and will report back if anything weird happens to me.

 

[Shonk]

i think netbios is broken on this its hard to be 100% as i also just installed a second rt-ac88u in ap mode
both happened the same time (yesteday)

ever since the network browser is dead on all pc's in the lan

LANscanner v1.68 - ScottiesTech.Info

Scanning LAN...
A remote API error occurred.

More help is available by typing NET HELPMSG 2127.



Press any key to exit...

 

[Ryu Connor]

This firmware release is unsuitable to be used in media bridge mode. It has an IPv6 regression that breaks DHCPv6. Clients behind the bridge will only receive a stateless IPv6 address for a short period of time before it randomly is dropped and never renewed. Manual renewal of the DHCPv6 address via ipconfig /renew6 results in the same behavior, only a temporary retainment of the address before it is dropped.

Reverting to 3.0.0.4_382_15850-g7402e99 resolves the DHCPv6 issues.

 

[Squall Leonhart]

Log spam occuring, multiple times over the last few days.
WLCEVENTD: eth1: Assoc
WLCEVENTD: eth1: Disassoc

 

[Grisu]

RT-AC68U
firmware:3.0.0.4.384_45149
After the installation of the restored factory settings. No icon to access the downloadmaster, not always can be applied to change the name of the client.

Please dont spam all threads with this same issue (3rd identical I read now). Especially as I updated my 68U thread in first posting regarding to this.

 

[Gregory Phillips]

I'm also seeing some log spamming too.

 

[SystemF]

Guys what about dual wan is it working finally well in load balancing mode? Someone tested?

 

[roadPilot]

Version 3.0.0.4.384.45149 2018/12/05
45.88 MBytes

AiMesh
- Improved AiMesh stability

LOL.

New (less than two weeks old) RT-AC86U (master) and new (same) RT-AC88U (node) were working find in AiMesh.

As soon as I upgraded both to 45149, the RT-AC88U node refused to stay connected (offline).

TWICE I completely removed it, did a factory reset, and added it back.

No change.

 

[AntonK]

Hi,

Does anyone know what these repetitive log entries mean?

Dec 11 03:36:01 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 03:36:02 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 03:36:04 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 03:45:53 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 03:47:50 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 03:55:39 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 03:56:02 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 04:09:04 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 04:09:40 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 04:10:45 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 04:12:50 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 04:23:15 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 04:23:38 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 04:32:55 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 04:32:58 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 04:38:11 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 05:24:56 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 06:05:16 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 06:44:52 WLCEVENTD: eth2: Disassoc 24:5B:A7:28:07A
Dec 11 07:50:05 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 07:50:05 WLCEVENTD: eth2: Assoc 88:19:08:23:0A:09
Dec 11 07:51:58 WLCEVENTD: eth2: Disassoc 88:19:08:23:0A:09
Dec 11 10:41:34 WLCEVENTD: eth1: Disassoc 44:1C:A8:4A:3E:99
Dec 11 10:41:40 WLCEVENTD: eth1: Assoc 44:1C:A8:4A:3E:99
Dec 11 18:00:38 WLCEVENTD: eth1: Assoc 24:5B:A7:28:07A​

Thanks for any thoughts,
Anton

 

[RMerlin]

Does anyone know what these repetitive log entries mean?

They're clients disconnecting/reconnecting to the wifi.

 

[Squall Leonhart]

yeah, but its blatant log spam, asus needs to give us control over the verbosity.

 

[AntonK]

They're clients disconnecting/reconnecting to the wifi.

Thanks RMerlin!

 

[SystemF]

IPsec sever still disconnect me after 3 hours exact with shrew soft and with android just internet stops after 3 hours, imho Asus shall remove ipsec or add ivev2 aka agressive mode and some other usefull futures in ipsec, iptv still don't work with manual custom vlans too.

 

[infatality]

Since updated to the latest firmware.. The following log spam keep spamming which previous firmware don't have such log spam.


Sent from my iPad using Tapatalk

 

[Ryu Connor]

This firmware release is unsuitable to be used in media bridge mode. It has an IPv6 regression that breaks DHCPv6. Clients behind the bridge will only receive a stateless IPv6 address for a short period of time before it randomly is dropped and never renewed. Manual renewal of the DHCPv6 address via ipconfig /renew6 results in the same behavior, only a temporary retainment of the address before it is dropped.

Reverting to 3.0.0.4_382_15850-g7402e99 resolves the DHCPv6 issues.

I need to make a correction here. I didn't correctly name all the guilty actors. Further testing revealed that the problem with DHCPv6 did not lie exclusively with Media Bridge mode. My second AC88U running in Router mode with firmware 3.0.0.4.384.45149 also has DHCPv6 issues. Rolling back the Router firmware to 3.0.0.4.384_21045 fixed the problem.

I'd like to be able to do a diff on the IPv6 code between these two versions, but I wouldn't even know where to begin to look in the source.

 

[SystemF]

Guys some light on the new future in administration panel:
Network Monitoring:
DNS Query vs Ping (its clear for what its use) what about DNS Query?