What's new

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

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

There are some settings for the RT-AX88U latest firmware which are missing for the RT-AX89X. I would like to see them added.

For the RT-AX88U, Dual-Band Smart Connect allows setting the Channel bandwidth and Control Channel separately for 2.4 GHz and 5 GHz, as well as configuring the Smart Connect Rule. Also there is a setting for WiFi Agile Multiband.
 
Problem i have found with the beta firmware:

The time scheduling/ internet blocking is not working for me

Update: it seems to only block apple app store downloads.
 
Last edited:
Does this by any chance fix the Let's Encrypt certificate renew problem?

My certificate is about to be expired in 26 days.
I thought it'll be renew every 60 days, it should never get below 30 days mark.

Searching the forum about this, I only see that every new FW of the other model listed this version with `Fix Lets encrypt not working properly.`
So, I wanted to know if I need to use this FW to get my cert.

1626698641238.png


1626698677503.png
 
Does this by any chance fix the Let's Encrypt certificate renew problem?

My certificate is about to be expired in 26 days.
I thought it'll be renew every 60 days, it should never get below 30 days mark.

Searching the forum about this, I only see that every new FW of the other model listed this version with `Fix Lets encrypt not working properly.`
So, I wanted to know if I need to use this FW to get my cert.

View attachment 35106

View attachment 35107
A few days later, I quite sure that it's not going to update, so I do it myself like this.

Bash:
rm -rf /jffs/.le
service restart_letsencrypt

The log
1626805137509.png


Just in case anyone with the same router faces the same problem.
Credit goes here
 
Anyone with the 89X having issues with RAM usage being really high (around 97%) followed by the router crashing on this firmware? I essentially have to reboot every two days to prevent the thing from running out of RAM.
 
Coming from firmware 41994 on the CT8. I have 2.4 and 5 Ghz on separate SSIDs. This worked fine on 41994, but now, 2.4 SSID will not connect from the node. Only the 5GHz works @ the node.

I switched only the node from 44366 back to 41994 and the 2.4 band came back right away from the node.

Thanks for updating though! Been looking forward to a new firmware for the CT8!
 
Last edited:
A few days later, I quite sure that it's not going to update, so I do it myself like this.

Bash:
rm -rf /jffs/.le
service restart_letsencrypt

The log
View attachment 35129

Just in case anyone with the same router faces the same problem.
Credit goes here
The following command actually resolved my Let's Encrypt Authorizing issue that I was having since day 1 I had my Asus RT-AX89X:

rm -rf /jffs/.le
service restart_letsencrypt

==

Thank you so much for this find and sharing.

Jon
 
The following command actually resolved my Let's Encrypt Authorizing issue that I was having since day 1 I had my Asus RT-AX89X:

rm -rf /jffs/.le
service restart_letsencrypt

==

Thank you so much for this find and sharing.

Jon
do you have syslog on this issue?
 
do you have syslog on this issue?
Here's a snippet of the syslog that have references to this issue:

===
Code:
Jul 19 12:30:00 rc_service: service 1731:notify_rc restart_letsencrypt
Jul 19 12:30:01 kernel: [54511.681323] [Mon Jul 19 12:30:01 DST 2021]
Jul 19 12:30:01 kernel: [54511.684931] Standalone mode.
Jul 19 12:30:02 kernel: [54511.958841] unable to load Private Key
Jul 19 12:30:02 kernel: [54511.958927] 1996259328:error:0909006C:lib(9):func(144):reason(108):NA:0:Expecting: ANY PRIVATE KEY
Jul 19 12:30:02 kernel: [54512.009230] unable to load Private Key
Jul 19 12:30:02 kernel: [54512.009310] 1996107776:error:0909006C:lib(9):func(144):reason(108):NA:0:Expecting: ANY PRIVATE KEY
Jul 19 12:30:02 kernel: [54512.072395] [Mon Jul 19 12:30:02 DST 2021]
Jul 19 12:30:02 kernel: [54512.075247] Registering account
Jul 19 12:30:02 kernel: [54512.623772] unable to load key file
Jul 19 12:30:02 kernel: [54512.623897] 1995788288:error:0909006C:lib(9):func(144):reason(108):NA:0:Expecting: ANY PRIVATE KEY
Jul 19 12:30:03 kernel: [54513.117361] [Mon Jul 19 12:30:03 DST 2021]
Jul 19 12:30:03 kernel: [54513.122884] Register account Error: {
Jul 19 12:30:03 kernel: [54513.122884]   "type": "urn:ietfarams:acme:error:malformed",
Jul 19 12:30:03 kernel: [54513.122884]   "detail": "Parse error reading JWS",
Jul 19 12:30:03 kernel: [54513.122884]   "status": 400
Jul 19 12:30:03 kernel: [54513.122884] }
Jul 19 12:30:03 kernel: [54513.159153] [Mon Jul 19 12:30:03 DST 2021]
Jul 19 12:30:03 kernel: [54513.164546] Please add '--debug' or '--log' to check more details.
Jul 19 12:30:03 kernel: [54513.179780] [Mon Jul 19 12:30:03 DST 2021]
===

It seems to loop with similar log entries...the common issue is "unable to load key file" which deleting the invisible .le directory and it's contents and then restarting the Let's Encrypt service resolved by recreating the files in question.
 
Last edited:
@ASUSWRT_2020
Thanks for providing the new firmware.
I am also encountering the problem with onu gpon.


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.
Where did this firmware come from
RT-AX89U_9.0.0.4_386_43381-ga0042bf_always_enable_sfp+.trx
 
CT8 or ax89x?
Ax89x also not sure if this log mean anything but this is from after i turn off the internet of my phone but i was still watching videos and searching google. I take it has something to do with ipv6? Not sure, I am new to this.
Code:
Jul 25 02:37:33 miniupnpd[2464]: recv (state0): Connection reset by peer
Jul 25 02:39:20 rc_service: httpd 1431:notify_rc restart_firewall
Jul 25 02:39:20 syslog: module ip6t_ROUTE not found in modules.dep
Jul 25 02:39:20 syslog: module ip6t_LOG not found in modules.dep
Jul 25 02:39:59 rc_service: httpd 1431:notify_rc restart_firewall
Jul 25 02:39:59 syslog: module ip6t_ROUTE not found in modules.dep
Jul 25 02:39:59 syslog: module ip6t_LOG not found in modules.dep
 
Had 4 CT8's in AiMesh configuration with 5Ghz 2 as the backhaul, connections where still pretty unstable even with this firmware.
Issue is something with the frequent dropping of WiFi nodes, priority seemed to work but router still did it's random drops..
Changed the CT8's to 1 router, 1 repeater and 2 media bridges with endpoints on both, everything is stable and much faster now, seems like AiMesh with a WiFi backhaul just isn't up for the task.
On a side note, the media bridge explanation on the routers admin page are a bit misleading, you can actually have media bridges configurated for the devices end only.
 
Last edited:
Where did this firmware come from
RT-AX89U_9.0.0.4_386_43381-ga0042bf_always_enable_sfp+.trx

That version was provided by Japanese support desk.
It was contingent on feedback from MAP-E(Japan's peculiar specifications) and XT8.

I have not received any response to the feedback since then, so I don't know the result.
However, I believe that the problem has been fixed in this version, and I would like to try it, but I have not been able to test it due to the GPON problem.

So, I don't think there is any need to try the older version.
 
I seem to have another issue that started recently. The web interface would stop working. the router would drop some of the clients and the ram usage would be over 90%. Below is the logs, although I don't know if it helps

Edit: not 100% sure but roamast roaming start... events in syslog seem to increase memory usage. I will report back again with more logs if it crashes again. It is working fine after a system reboot. I have an AiMesh with 3 routers ax89x(main), gt-5300, , rp-ac1900
 

Attachments

  • syslog (1).txt
    817.1 KB · Views: 99
Last edited:
Update to my ram management issue Shortly after i have ran into the issue again below is the log, it has not gotten to the point where the web interface crash yet however it is getting there. Please help.
chrome_gNtAvOlu7K.png
 

Attachments

  • syslog (2).txt
    328.4 KB · Views: 252
324MB free RAM is not close to crashing the router. :)

Are you leaving the GUI open? Or are you just spot-checking it?
 
No, this is normal and efficient router operation and memory usage. Here is my example work and uptime. No problem...
 

Attachments

  • 2.jpg
    2.jpg
    63 KB · Views: 110
  • 1.jpg
    1.jpg
    42.9 KB · Views: 110
No, this is normal and efficient router operation and memory usage. Here is my example work and uptime. No problem...
I don't know how many devices you are running or how your network is set up however that is not normal for me. On top of that my web UI crashed with me unable to log on before and some devices get disconnected. This morning after the crash I decided to reupload the firmware and it seem to have fixed it for now. I will report back with crashed Web UI if it happens again. That said below is my normal operating stats after a few hours. side note: anyone know what this is?
Code:
Jul 26 19:06:59 miniupnpd[26208]: accept(http): Too many open files
 

Attachments

  • chrome_hw75I75pDC.png
    chrome_hw75I75pDC.png
    176.9 KB · Views: 133
  • chrome_LnKcGAqVx8.png
    chrome_LnKcGAqVx8.png
    581.2 KB · Views: 99

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