ASUS RT-AX88U Firmware v3.0.0.4.386_41249

[Spartan]

It's not available to download from the ASUS site but I just checked for firmware updates from the Router Admin page and was offered this firmwareL

 

[gpmc]

Just downloaded on my 2 RT-AX88U's in AiMesh. AiMesh menu has been added with advanced settings. Everything seems to be ok till now. I'd like anyway to see the changelog but not available yet from ASUS website.

 

[cyu6722]

Attached the change log from the Asus router app for my AX88u. Upgraded with an AiMesh setup with a AX58u node thats still on the old firmware. Hopefully no issues.

 

[juched]

Newer version than their current beta... hmm..

 

[dmtg]

You can download from Asus website https://dlcdnets.asus.com/pub/ASUS/wireless/RT-AX88U/FW_RT_AX88U_300438641249.zip

 

[LimJK]

Just appeared on ASUS Website

RT-AX88U｜WiFi Routers｜ASUS Singapore

ASUS gaming routers provide the very best gaming experience, with an arsenal of features and tools designed to improve online gaming performance and give you the competitive edge you need to win.

www.asus.com

Select "Drivers & Tools" -> "Mac OS"
I suppose it takes time to propagate to all locations.

Edit: Include the description here for easier reading:

Version 3.0.0.4.386.41249
2020/12/08 69.58 MBytes
ASUS RT-AX88U Firmware version 3.0.0.4.386.41249
1. AiMesh 2.0
- System optimization: one click in AiMesh to optimize the topology
- System Ethernet backhaul mode, all nodes will only connect by ethernet, all bands will be released for wireless clients.
- System factory default and reboot.
- Client device reconnect, make the device to offline and online again.
- Client device binding to specific AP.
- Guest WiFi on all Mesh nodes (all node need to upgrade to 3.0.0.4.386 firmware)
- Access nodes USB application.

Connection priority and Ethernet backhaul mode introduction

[AiMesh] What is Ethernet Backhaul Mode/Backhaul Connection Priority in AiMesh System and how to set up in different scenarios? | Official Support | ASUS Global

How to setup ASUS AiMesh or ZenWiFi Mesh Ethernet backhaul under different conditions

[AiMesh] How to set up ASUS AiMesh or ZenWiFi Mesh Ethernet backhaul under different conditions ? (Advanced setup with network switch) | Official Support | ASUS Global

2. New Family interface in ASUS router App.
ASUS Router App for iOS must greater or equal to iOS v1.0.0.5.75
Android version greater or equal to v1.0.0.5.74

3. The unit of the WiFi time scheduler goes to 1 minute.

4. 2.4 and 5G on the network map could be configured in the same tab.

5. Captcha for login can be disabled in administration -> system.

6. Printer server port can be disabled on the USB app page.

7. Clients which connect to the guest network can be viewed in the network map -->view list --> interface

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

 

[insekt]

Hi, I've just upgraded to v3.0.0.4.386_41249 and I cannot connect to network using PPPoE. After returning to previous release (3.0.0.4.384.9566) I can connect without any issues.

I get the following logs:

Dec  9 10:55:13 rc_service: ntp 1645:notify_rc restart_diskmon
Dec  9 10:55:13 disk_monitor: Finish
Dec  9 10:55:13 disk monitor: be idle
Dec  9 10:55:14 kernel: random: nonblocking pool is initialized
Dec  9 10:55:14 httpd: Succeed to init SSL certificate...80
Dec  9 10:55:16 cfg_server:  event: wl_chanspec_changed_action
Dec  9 10:55:16 cfg_server: skip event due no re
Dec  9 10:55:17 kernel: SHN Release Version: 2.0.1 4b635f32
Dec  9 10:55:17 kernel: UDB Core Version: 0.2.18
Dec  9 10:55:17 kernel: sizeof forward pkt param = 280
Dec  9 10:55:17 BWDPI: fun bitmap = 47f
Dec  9 10:55:17 cfg_server:  event: wl_chanspec_changed_action
Dec  9 10:55:17 cfg_server: current chansp(unit0) is 1808
Dec  9 10:55:17 cfg_server: current chansp(unit1) is e832
Dec  9 10:55:17 cfg_server: dump exclchans:
Dec  9 10:55:17 cfg_server: old wl0_acs_excl_chans:0x100c,0x190a,0x100d,0x190b,0x100e,0x190c
Dec  9 10:55:17 cfg_server: new wl0_acs_excl_chans:0x100c,0x190a,0x100d,0x190b,0x100e,0x190c
Dec  9 10:55:17 cfg_server: old wl1_acs_excl_chans:0xd034,0xd038,0xd03c,0xd040,0xd936,0xd93e,0xd836,0xd83e,0xe03a,0xe13a,0xe23a,0xe33a,0xec32,0xed32,0xee32,0xef32,0xd064,0xd068,0xd06c,0xd070,0xd074,0xd078,0xd07c,0xd080,0xd084,0xd088,0xd08c,0xd966,0xd96e,0xd976,0xd97e,0xd986,0xd866,0xd86e,0xd876,0xd87e,0xd886,0xe06a,0xe07a,0xe16a,0xe17a,0xe26a,0xe27a,0xe36a,0xe37a,0xe872,0xe972,0xea72,0xeb72,0xec72,0xed72,0xee72,0xef72
Dec  9 10:55:17 cfg_server: new wl1_acs_excl_chans:0xd034,0xd038,0xd03c,0xd040,0xd936,0xd93e,0xd836,0xd83e,0xe03a,0xe13a,0xe23a,0xe33a,0xec32,0xed32,0xee32,0xef32,0xd024,0xd028,0xd02c,0xd030,0xd926,0xd92e,0xd826,0xd82e,0xe02a,0xe12a,0xe22a,0xe32a,0xe832,0xe932,0xea32,0xeb32
Dec  9 10:55:17 cfg_server:   wl_chanspec_changed_action: Need to restart wireless due current 5G chanspec is un-available
Dec  9 10:55:17 rc_service: cfg_server 1448:notify_rc restart_wireless
Dec  9 10:55:19 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 0
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device eth6.501^[[0m
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,652: Failed to delete VLAN device eth7.501^[[0m
Dec  9 10:55:19 pppd[1400]: Modem hangup
Dec  9 10:55:19 zcip: iface br1 is down
Dec  9 10:55:19 avahi-daemon[1268]: IP_DROP_MEMBERSHIP failed: No such device
Dec  9 10:55:19 pppd[1400]: Connection terminated.
Dec  9 10:55:19 pppd[1400]: Failed to disconnect PPPoE socket: 114 Operation already in progress
Dec  9 10:55:19 pppd[1400]: send (sendPacket): No such device or address
Dec  9 10:55:19 kernel: wfd_registerdevice Successfully registered dev wl0.1 ifidx 1 wfd_idx 0
Dec  9 10:55:19 kernel: Register interface [wl0.1]  MAC: 04:d4:c4:4f:6c:61
Dec  9 10:55:19 kernel: IGMP Query send failed
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:19 kernel: netdev path : eth6.0 -> eth6
Dec  9 10:55:19 kernel: BCMVLAN : eth6 mode was set to RG
Dec  9 10:55:19 kernel: netdev path : eth6.501 -> eth6
Dec  9 10:55:19 kernel: BCMVLAN : eth6 mode was set to RG
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:19 kernel: netdev path : eth7.0 -> eth7
Dec  9 10:55:19 kernel: BCMVLAN : eth7 mode was set to RG
Dec  9 10:55:19 kernel: netdev path : eth7.501 -> eth7
Dec  9 10:55:19 kernel: BCMVLAN : eth7 mode was set to RG
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:19 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:20 kernel: HTB: quantum of class 20010 is big. Consider r2q change.
Dec  9 10:55:20 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:20 kernel: HTB: quantum of class 20040 is big. Consider r2q change.
Dec  9 10:55:20 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:20 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:20 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:20 WAN Connection: Fail to connect with some issues.
Dec  9 10:55:21 acsd: eth6: Selecting 2g band ACS policy
Dec  9 10:55:21 wlceventd: wlceventd Start...
Dec  9 10:55:21 acsd: acsd_main_loop(1107): sync_id: 35210, status:1, misc.error/abort
Dec  9 10:55:21 acsd: eth6: selected channel spec: 0x1808 (6l)
Dec  9 10:55:21 acsd: eth6: Adjusted channel spec: 0x1808 (6l)
Dec  9 10:55:21 acsd: eth6: selected channel spec: 0x1808 (6l)
Dec  9 10:55:21 acsd: acs_set_chspec: 0x1808 (6l) for reason APCS_INIT
Dec  9 10:55:21 acsd: eth7: Selecting 5g band ACS policy
Dec  9 10:55:26 crond[1250]: time disparity of 1366850 minutes detected
Dec  9 10:55:28 wlceventd: wlceventd_proc_event(510): eth6: Auth 70:2C:1F:79:6F:8B, status: Successful (0)
Dec  9 10:55:28 wlceventd: wlceventd_proc_event(539): eth6: Assoc 70:2C:1F:79:6F:8B, status: Successful (0)
Dec  9 10:55:31 roamast: ROAMING Start...
Dec  9 10:55:32 acsd: eth7: NONACSD channel switching to channel spec: 0xd024 (36)
Dec  9 10:55:40 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:55:52 wlceventd: wlceventd_proc_event(510): wl0.1: Auth 58:B1:0F:8B:66:96, status: Successful (0)
Dec  9 10:55:52 wlceventd: wlceventd_proc_event(539): wl0.1: Assoc 58:B1:0F:8B:66:96, status: Successful (0)
Dec  9 10:55:54 kernel: bcm_i2c: bus 0: Failed to detect SFP: 100 retries exhausted
Dec  9 10:55:56 wlceventd: wlceventd_proc_event(474): wl0.1: Deauth_ind 58:B1:0F:8B:66:96, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec  9 10:55:57 wlceventd: wlceventd_proc_event(510): eth6: Auth 58:B1:0F:8B:66:96, status: Successful (0)
Dec  9 10:55:57 wlceventd: wlceventd_proc_event(539): eth6: Assoc 58:B1:0F:8B:66:96, status: Successful (0)
Dec  9 10:55:59 wlceventd: wlceventd_proc_event(491): eth6: Disassoc 58:B1:0F:8B:66:96, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec  9 10:55:59 wlceventd: wlceventd_proc_event(491): eth6: Disassoc 58:B1:0F:8B:66:96, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec  9 10:56:00 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:56:01 wlceventd: wlceventd_proc_event(510): eth6: Auth 58:B1:0F:8B:66:96, status: Successful (0)
Dec  9 10:56:01 wlceventd: wlceventd_proc_event(520): eth6: ReAssoc 58:B1:0F:8B:66:96, status: Successful (0)
Dec  9 10:56:01 kernel: br0: received packet on eth6.0 with own address as source address
Dec  9 10:56:04 pppd[1400]: Timeout waiting for PADO packets
Dec  9 10:56:08 wlceventd: wlceventd_proc_event(510): eth6: Auth 80:C5:F2:BC:8C:21, status: Successful (0)
Dec  9 10:56:08 wlceventd: wlceventd_proc_event(539): eth6: Assoc 80:C5:F2:BC:8C:21, status: Successful (0)
Dec  9 10:56:20 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:56:34 hour monitor: ntp sync fail, will retry after 120 sec
Dec  9 10:56:40 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:57:00 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:57:04 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7035)]periodic_check AM 2:46
Dec  9 10:57:19 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7099)]could not retrieve firmware information: webs_state_update = 1, webs_state_error = 1, webs_state_dl_error = 0, webs_state_info.len = 0
Dec  9 10:57:19 pppd[1400]: Timeout waiting for PADO packets
Dec  9 10:57:20 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m
Dec  9 10:57:40 kernel: ^[[0;33;41m[ERROR mcast] bcm_mcast_netlink_process_snoop_cfg,884: interface 33 could not be found^[[0m

Can you please guide me how can I solve this problem?

 

[Ultima]

I've just upgraded and no issues found here. Hope you get it sorted.

 

[bigcid10]

Just flashed it myself
let's encrypt stuck on authorizing,did factory default
same issue

 

[LimJK]

Just flashed it myself
let's encrypt stuck on authorizing,did factory default
same issue

I have the same Let's Encrypt issue, everything else seem to be working well for me. By the way are you using RT-AC88U as per your signature or RT-AX88U as per title of this thread

 

[Smack Boy]

I am using RT-AX88U (3.0.0.4.386_41249) as the router and 2 AiMesh nodes are ZenWifi AX XT8 a.k.a. RT-AX95Q (3.0.0.4.386_25790).

I set the guest network Sync to AiMesh Node to "All" but the guest network does not broadcast from the nodes. It only broadcasts from the router.

Does anybody else have the same problem? Has anybody successfully propagated the guest network to a node running 386 FW?

 

[bigcid10]

I have the same Let's Encrypt issue, everything else seem to be working well for me. By the way are you using RT-AC88U as per your signature or RT-AX88U as per title of this thread

RT-AX88U

 

[liqiang2020]

how i can use the port 80 to access the 192.168.50.1? not use http://192.168.50.1:81,please help me, thank you!

 

[OzarkEdge]

how i can use the port 80 to access the 192.168.50.1? not use http://192.168.50.1:81,please help me, thank you!

Simply browse to 192.168.50.1 (?).

GRC | Port Authority, for Internet Port 80

OE

 

[cyu6722]

I've noticed the binding options on the ai mesh page doesn't stick. I have my main pc that connects to the main router but it always changes to the node even though the signal is good. The option is always reverted when I click on the binding button again.

 

[KrispiL]

I am using RT-AX88U (3.0.0.4.386_41249) as the router and 2 AiMesh nodes are ZenWifi AX XT8 a.k.a. RT-AX95Q (3.0.0.4.386_25790).

I set the guest network Sync to AiMesh Node to "All" but the guest network does not broadcast from the nodes. It only broadcasts from the router.

Does anybody else have the same problem? Has anybody successfully propagated the guest network to a node running 386 FW?

I have guest networks working fine on remote mesh nodes, including having intranet isolation enabled.

I think 3.0.0.4.386_25790 may be too early to have AiMesh 2.0 enabled on it, the earliest version in the AiMesh 2.0 public beta thread was 3.0.0.4.386_39179, so unless they have released a later version of this on the ASUS site for the XT8 you will probably need to use the firmware published on the beta thread.

 

[LimJK]

I would like to report:

I have been running smoothly with Stock 3.0.0.4_386_41249 for about 2.5 days, my configuration includes using only AiMesh 2.0 DEFAULT settings:

• Solid Ethernet Backhaul
• Excellent Wifi (AiMesh Roaming/Steering)
• Good Performance (Upload/Download: Wifi (ac) about 400mbps, Wired about 930mbps)

Hope that it can be a useful comparison for others with similar configuration.

My Configuration:

• AiMesh Router: AX88U 3.0.0.4_386_41249-g66dde88 + 2 x AiMesh Nodes: AC86U 9.0.0.4_386_41157-gd618756
• Backhaul (Priority:"Auto", Type:"Wired"), Asus GX-U1051 5-Port Gigabit Switch from Router to Nodes, ISP: 1 Gbps Fibre

My steps to Upgrade from Merlin 386.1_beta1 -> Stock 3.0.0.4_386_41249:

(1) Upgrade AiMesh Nodes:

• Administration -> Upgrade Firmware ->
  • Select and Upgrade AiMesh Node (One Node at a time)
• AiMesh -> Topology -> Select AiMesh Node ->
  • Remove Node (One Node at a time to Factory Reset Node)
• Note that I use Beta FW AC86U 9.0.0.4_386_41157-gd618756

(2) Upgrade AiMesh Router:

• Administration -> System
  • Format JFFS partition at next boot: Yes
  • Enable JFFS custom scripts and configs: Yes
• Reboot: GUI or Physical with WPS button
• Disconnect LAN Cable from MacBookPro (to get a new IP address)
• Administration -> Upgrade Firmware -> Select and Upgrade
• Factory Reset with GUI -> ie. Restore with the (X) Initialize option
• Configure from scratch
• Reboot : GUI or Physical with WPS button

(3) After Full Factory Reset of AiMesh Router / Nodes, I tried to leave NVRAM using Stock FW default values, except with the following changes:

• Enabled AiProtection: ON
  • Malicious Sites Blocking: ON
  • Two-Way IPS: ON
  • Infected Device Prevention and Blocking: ON
• USB Application
  • UPnP Media Server: OFF
  • Samba Share: OFF
• Wireless:
  • 2.4 GHz: Fixed Channel Bandwidth 20MHz, Fixed Control Channel: 11, Explicit / Universal Beamforming: Disable
  • 5.0 GHz: Fixed Channel Bandwidth 80MHz, Fixed Control Channel: 149
• WAN DDNS:
  • Using Asus DDNS Service with Let’s Encrypt (Let’s Encrypt appeared to be not working lately, Workaround: so I turn HTTPS/SSL Certificate to NONE and just use HTTP to access my router)
• IPv6: Enable
  • Native (Understand that VPN Servers on ASUS does not support IPv6; therefore, DNS Leaks (OK for me, as I only occasion use it to remotely manage Router for a short while when I am outside))
• VPN Servers (Connecting one at a time from the following clients):
  • OpenVPN works with MacBookPro Tunnelblick 3.8.5beta0, iPhoneXsMax iOS OpenVPN Connect 3.2.2
  • IPSec works with MacBookPro & iPhoneXsMax Native Configurations
  • Instant Guard works with iPhoneXsMax iOS Instant Guard 1.0.9

(5) Add AiMesh Nodes

(6) Reboot AiMesh Network (for a clean AiMesh Restart )

• AiMesh -> System Settings -> Reboot (AiMesh Router & Nodes)

 

[liqiang2020]

Simply browse to 192.168.50.1 (?).

GRC | Port Authority, for Internet Port 80

OE

i can't find where to config my ax88u，how to modify the port 81 to 80 in the router when i access it from wifi?

 

[OzarkEdge]

i can't find where to config my ax88u，how to modify the port 81 to 80 in the router when i access it from wifi?

Browse to the router IP address or router.asus.com.

OE

 

[liqiang2020]

it's not work use the port 80, i must add the port 81 to open the site,