Beta Beta 3004.386 AiMesh 2.0 for RT-AX89X and ZenWiFi CT8

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

ASUSWRT_2020

Regular Contributor

tgp

New Around Here
Hi there,

We recently have new build of RT-AX89X and ZenWiFi CT8, both are Qualcomm platform.
If you have these two, and would like to try, please download from here:
ZenWiFi CT8 (AiMesh 2.0)
https://www.asuswebstorage.com/navigate/a/#/s/BA6E66D7E5F14FEDB43B582697880651Y
RT-AX89X
https://www.asuswebstorage.com/navigate/a/#/s/23FB67AFA6ED4C48863C9814356F224B4

Please comment in this thread if any.

Thanks.
Great news, thank you. Is there a changelog available at all?
 

ASUSWRT_2020

Regular Contributor
list few major

AX89X
  • fix 11k RCPI
  • modify SFP+ controll
  • GUI fix
  • SFP could be fix 1G in switch control page
  • Fix ddns gui issue
  • Fix client on guest network abnormal behavior while under access control.
  • Fix guest network bandwidth limiter issue.
  • AiMesh 2.0 support.(802.11k/v, more Eth backhaul options, client bind ap, preferable path..etc)
CT8
- FragAttacks security patch
- AiMesh 2.0 support.(802.11k/v, more Eth backhaul options, client bind ap, preferable path..etc)
 

SomeWhereOverTheRainBow

Part of the Furniture
Hi there,

We recently have new build of RT-AX89X and ZenWiFi CT8, both are Qualcomm platform.
If you have these two, and would like to try, please download from here:
ZenWiFi CT8 (AiMesh 2.0)
https://www.asuswebstorage.com/navigate/a/#/s/BA6E66D7E5F14FEDB43B582697880651Y
RT-AX89X
https://www.asuswebstorage.com/navigate/a/#/s/23FB67AFA6ED4C48863C9814356F224B4

Please comment in this thread if any.

Thanks.
It would be nice if you could include the 87U in these "very exclusive" updates.
 

RMerlin

Asuswrt-Merlin dev
It would be nice if you could include the 87U in these "very exclusive" updates.
The RT-AC87U is officially EOL, and Quantenna themselves have dropped support for their chipset years ago. AiMesh cannot be implemented on that model either due to the Quantenna architecture.
 

tgp

New Around Here
list few major

AX89X
  • fix 11k RCPI
  • modify SFP+ controll
  • GUI fix
  • SFP could be fix 1G in switch control page
  • Fix ddns gui issue
  • Fix client on guest network abnormal behavior while under access control.
  • Fix guest network bandwidth limiter issue.
  • AiMesh 2.0 support.(802.11k/v, more Eth backhaul options, client bind ap, preferable path..etc)
CT8
- FragAttacks security patch
- AiMesh 2.0 support.(802.11k/v, more Eth backhaul options, client bind ap, preferable path..etc)
Thank you sir.
 

SomeWhereOverTheRainBow

Part of the Furniture
The RT-AC87U is officially EOL, and Quantenna themselves have dropped support for their chipset years ago. AiMesh cannot be implemented on that model either due to the Quantenna architecture.
I am surprise they couldn't take advantage of Quantenna’s boasted "Spartan Architecture" For adding mesh support to this model.
 

L&LD

Part of the Furniture
Quantenna themselves have dropped support for their chipset years ago.
 

NSNE

Regular Contributor
I upgraded my AX89X from9.0.0.4_386_44129. I've now got several WiFi devices that are able to connect to the router but cannot be accessed locally: two Sonos speakers, two KEiiD amps, and about six Meross devices. The fact that these are groups of devices that share brands/models points to a compatibility issue.

@ASUSWRT_2020, what changes were made between versions 44129 and 44323 that might be causing this issue? A changelog would help me troubleshoot.

EDIT: Never mind, just saw that the changelog was posted earlier.

EDIT #2: Never mind for a second time. A full system reboot (router, all nodes) appears to have solved things.
 
Last edited:

Stach

Regular Contributor
I loaded this new beta firmware on my CT8 yesterday and I've had zero issues so far. It's nice to see the new Backhaul options, among other things!
 

jonjon

New Around Here
I just upgraded by AX89X with this beta firmware 9.0.0.4_386_44323 as my main Mesh router and the Asus ZenWifi AX (XT8) x 2 running the public release 3.0.0.4.386.43181 as my Mesh nodes and sofar everything is working perfectly. I really like that the AX89X now supports Instant Guard VPN and has an Optimization button for AiMesh networks. I had seen the Optimization in my previous GT-AC5300 and on my AX88U that my parents are using but did not see it on the AX89X until now with this beta. I can't wait for this beta to go public...hopefully soon.

However, I still don't see the "Let's Encrypt Authorizing" error resolved yet that I had previously posted about at: https://www.snbforums.com/threads/asus-rt-ax89-x-release-firmware-3-0-0-4-386-22790-issues.69674/

I have not done a factory reset after this beta version but have done many previous factory resets to no avail regarding that "Let's Encrypt Authorizing" error.

Please advise.

Thanks
 

Webtank

New Around Here
Hi there,

We recently have new build of RT-AX89X and ZenWiFi CT8, both are Qualcomm platform.
If you have these two, and would like to try, please download from here:
ZenWiFi CT8 (AiMesh 2.0)
https://www.asuswebstorage.com/navigate/a/#/s/BA6E66D7E5F14FEDB43B582697880651Y
RT-AX89X
https://www.asuswebstorage.com/navigate/a/#/s/23FB67AFA6ED4C48863C9814356F224B4

Please comment in this thread if any.

Thanks.
Hello.
First of all, I am grateful to you for your work and for new firmware :)
But on this firmware (RT-AX89U_9.0.0.4_386_44323-gbd69172) there was a problem: the sfp + onu gpon module cannot be started. Even if I select 1Gbps in manual mode (Switch Control - SFP + port maximum link speed - 1Gbps), it still tries to start at 10Gbps and even in some kind of "65535". Tried a clean install of a new firmware and a factory reset. There were no problems with this on firmware 3.0.0.4.386.23012 and on beta RT-AX89U_9.0.0.4_386_44150-g49dbf3e_sfp+_ui_wo_fnf_patches , this sfp stick worked wonderfully, the logs said "PHY Link up speed: 1000" (1gbps)
Part of the log is attached below (problematic part).

May 5 08:05:35 kernel: [ 47.065508] eth4: PHY Link up speed: 65535
May 5 08:05:37 kernel: [ 49.065670] eth4: PHY Link is down
May 5 08:05:45 kernel: [ 57.065932] eth4: PHY Link up speed: 65535
May 5 08:05:47 kernel: [ 59.065949] eth4: PHY Link is down
May 5 08:05:49 APSTATS: band 0: beacon success: 210
May 5 08:05:49 APSTATS: band 1: beacon success: 166
May 5 08:05:49 THERMAL: CPU: 49, 2G: 50, 5G: 48, 10G: 54, FAN:1754. (C:0/0, U:0/50, F:0, D:4, P:68 T:296960)
May 5 08:06:15 kernel: [ 87.065512] eth4: PHY Link up speed: 65535
May 5 08:06:17 WAN Connection: ISP's DHCP did not function properly.
May 5 08:06:19 kernel: [ 91.065499] eth4: PHY Link is down
May 5 08:06:26 kernel: [ 97.653710] wlan: [0:I:ANY] son_bs_stats_update_cb: 1993: son_bs_stats_update_cb ctrl peer is null
May 5 08:06:27 WAN Connection: WAN(0) link down.
May 5 08:06:31 kernel: [ 103.065487] eth4: PHY Link up speed: 10000
May 5 08:06:33 kernel: [ 105.065474] eth4: PHY Link is down
May 5 08:06:39 rc_service: httpd 1406:notify_rc email_info
May 5 08:06:46 kernel: [ 118.065478] eth4: PHY Link up speed: 10000
May 5 08:06:48 kernel: [ 120.065480] eth4: PHY Link is down
May 5 08:06:49 kernel: [ 121.065488] eth4: PHY Link up speed: 65535
May 5 08:06:51 kernel: [ 123.065471] eth4: PHY Link is down
May 5 08:07:41 kernel: [ 173.065511] eth4: PHY Link up speed: 65535
May 5 08:07:43 kernel: [ 175.065477] eth4: PHY Link is down
May 5 08:07:53 kernel: [ 185.065478] eth4: PHY Link up speed: 65535
May 5 08:07:55 kernel: [ 187.065474] eth4: PHY Link is down
May 5 08:07:59 kernel: [ 191.065479] eth4: PHY Link up speed: 65535
May 5 08:08:01 kernel: [ 193.065479] eth4: PHY Link is down
May 5 08:08:22 kernel: [ 214.065480] eth4: PHY Link up speed: 65535
May 5 08:08:24 kernel: [ 216.065480] eth4: PHY Link is down
May 5 08:08:25 LBD: [ath1]: try to steer 5C:CB:99:C9:5F:99 by BTM
May 5 08:08:32 kernel: [ 224.065487] eth4: PHY Link up speed: 65535
May 5 08:08:34 kernel: [ 226.065477] eth4: PHY Link is down
May 5 08:08:35 kernel: [ 227.065493] eth4: PHY Link up speed: 10000
May 5 08:08:37 kernel: [ 229.065476] eth4: PHY Link is down
May 5 08:08:38 kernel: [ 230.065481] eth4: PHY Link up speed: 65535
May 5 08:08:40 kernel: [ 232.065478] eth4: PHY Link is down
May 5 08:08:59 kernel: [ 251.065489] eth4: PHY Link up speed: 10000
May 5 08:09:01 kernel: [ 253.065473] eth4: PHY Link is down
May 5 08:09:04 mcastds: MCSD interface: Error:No such file or directory
May 5 08:09:08 kernel: [ 260.065481] eth4: PHY Link up speed: 10000
May 5 08:09:10 kernel: [ 262.065473] eth4: PHY Link is down
May 5 08:09:13 kernel: [ 265.065480] eth4: PHY Link up speed: 10000
May 5 08:09:15 kernel: [ 267.065476] eth4: PHY Link is down
May 5 08:09:43 kernel: [ 295.065496] eth4: PHY Link up speed: 10000
May 5 08:09:48 kernel: [ 300.065477] eth4: PHY Link is down
May 5 08:09:57 kernel: [ 309.065482] eth4: PHY Link up speed: 65535
May 5 08:10:00 kernel: [ 312.065477] eth4: PHY Link is down
May 5 08:10:25 kernel: [ 337.065501] eth4: PHY Link up speed: 65535
May 5 08:10:27 kernel: [ 339.065481] eth4: PHY Link is down
May 5 08:10:34 kernel: [ 346.065480] eth4: PHY Link up speed: 10000
May 5 08:10:36 kernel: [ 348.065477] eth4: PHY Link is down
May 5 08:10:45 kernel: [ 357.065497] eth4: PHY Link up speed: 10000
May 5 08:10:47 kernel: [ 359.065483] eth4: PHY Link is down
May 5 08:11:02 kernel: [ 374.065485] eth4: PHY Link up speed: 65535
May 5 08:11:06 kernel: [ 378.065482] eth4: PHY Link is down
May 5 08:11:22 kernel: [ 393.826525] wlan: [0:E:NSS] [nss-wifili]: Could not set astenty active for hw_idx = 1804
May 5 08:11:47 kernel: [ 419.065484] eth4: PHY Link up speed: 65535
May 5 08:11:49 kernel: [ 421.065477] eth4: PHY Link is down
May 5 08:11:52 kernel: [ 424.065489] eth4: PHY Link up speed: 65535
May 5 08:11:54 kernel: [ 426.065484] eth4: PHY Link is down
May 5 08:12:04 kernel: [ 436.065482] eth4: PHY Link up speed: 10000
May 5 08:12:06 kernel: [ 438.065495] eth4: PHY Link is down
May 5 08:12:08 kernel: [ 440.065481] eth4: PHY Link up speed: 10000
May 5 08:12:10 kernel: [ 442.065478] eth4: PHY Link is down
May 5 08:12:34 kernel: [ 466.065501] eth4: PHY Link up speed: 65535
May 5 08:12:36 kernel: [ 468.065478] eth4: PHY Link is down
May 5 08:12:37 kernel: [ 469.065488] eth4: PHY Link up speed: 10000
May 5 08:12:37 WAN Connection: WAN(0) link up.
May 5 08:12:37 rc_service: wanduck 1321:notify_rc restart_wan_if 0
May 5 08:12:39 kernel: [ 471.065494] eth4: PHY Link is down
May 5 08:12:42 WAN Connection: ISP's DHCP did not function properly.
 

Attachments

  • ax.jpg
    ax.jpg
    63.5 KB · Views: 96

Portan

New Around Here
list few major

AX89X
  • fix 11k RCPI
  • modify SFP+ controll
  • GUI fix
  • SFP could be fix 1G in switch control page
  • Fix ddns gui issue
  • Fix client on guest network abnormal behavior while under access control.
  • Fix guest network bandwidth limiter issue.
  • AiMesh 2.0 support.(802.11k/v, more Eth backhaul options, client bind ap, preferable path..etc)
CT8
- FragAttacks security patch
- AiMesh 2.0 support.(802.11k/v, more Eth backhaul options, client bind ap, preferable path..etc)
Hello, does it mean that the 2 Ax89x routers can use aimesh feature using wired 10G ports as bachaul? Previously, it's not possible to establish wired 10G backhaul mesh.
 
Last edited:

Shadowxaero

New Around Here
Hello, does it mean that the 2 Ax89x routers can use aimesh feature using wired 10G ports as bachaul? Previously, it's not possible to establish wired 10G backhaul mesh.

I was able to establish a 2.5Gbe backhaul from the 89x to an 86u (which I could not do previously). I am going from 89x to 10Gbe (support 2.5 and 5Gbe as well) switch via SPF+ DAC cable, and from switch to the 86u. I image if that works then a 10Gbe backhual to another 89x will work.
 

lishan89

Occasional Visitor
Hmmm it seems aimesh node binding doesn't really bind. if it thinks it is better off connecting to 1 node over the other it will override the binding. then whats the point? LOL however giving me the option to disconnect a device is very useful. with regarding to ethernet backhaul has anyone trying Link aggregation?
 

nadias-jp

New Around Here
@ASUSWRT_2020
Thanks for providing the new firmware.
I am also encountering the problem with onu gpon.
May 5 14:05:17 kernel: [ 13.915860] sfp_phy_interface_get_mode_status[330]:INFO:Unsupported sfp_speed 1300, limit 100

It was working fine until the following version.
RT-AX89U_9.0.0.4_386_43381-ga0042bf_always_enable_sfp+.trx
RT-AX89X_3.0.0.4_386_23012-ge09afa2_202102031726.trx

The specification is as follows (P7)

Please support it again.
 

Attachments

  • スクリーンショット 2021-07-14 6.49.49.png
    スクリーンショット 2021-07-14 6.49.49.png
    597.3 KB · Views: 73

doc octopus

Senior Member
As previously reported to have problems with Xbox Series X when connected to the 5 GHz band: the console does not connect using the DFS channels, or connect and then disconnects and using channels 36-48 the accessible speed is approximately 100 Mbit and with package loss (with RT-AX86U I reach 170 Mbit without loss packages)
 

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