Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0 (continued)

  • 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
Update on 2021/1/29

This version changed the DNSmasq version to 2.84 to fix CVE-2020-25681, CVE-2020-25682, CVE-2020-25683, CVE-2020-25687, CVE-2020-25684, CVE-2020-25685, CVE-2020-25686 aka DNSpooq

https://drive.google.com/drive/folders/1TW9JXxWpM-qmgGv2BixibkACVki-9g1Q?usp=sharing
The share link includes the following models

ZenWiFi XT8, XD4, CT8, CD6
GT series: GT-AX11000, GT-AC5300, GT-AC2900
RT series: RT-AX88U, RT-AX92U, RT-AX86U, RT-AX82U, RT-AX58U, TUF-AX3000, RT-AX56U, RT-AX55
RT series: RT-AC5300, RT-AC88U, RT-AC3100, RT-AC86U, RT-AC68U




----------------------------------------------------------------------------------------------------------------------------------
Update again on 2021/1/21
We are patching DNSmasq vulnerability disclosed by JSOF and will start to put beta firmware on ASUS support site for this issue.

---------------------------------------------------------------------------------------------------------------------------------
Status update on 2021/1/21

386 rc2 formal released models
GT-AX11000 3.0.0.4.386.41700
RT-AX88U 3.0.0.4.386.41700
RT-AX86U 3.0.0.4.386.41535
RT-AX82U 3.0.0.4.386.41700
RT-AC86U 3.0.0.4.386.41634
TUF-AX3000 3.0.0.4.386.41700

ZenWiFi XD4 3.0.0.4.386.41535
RT-AC88U 3.0.0.4.386.41700
RT-AC3100 3.0.0.4.386.41700
RT-AC68U 3.0.0.4.386.40558

Under testing models
ZenWiFi XT8
GT-AC2900
RT-AC86U (to solve high CPU utilization issue)
RT-AX92U
RT-AX58U
RT-AX55



--------------------------------------------------------------------------------------------------------------------------------
Update 2020/12/31 (9.0.0.4.386.41535)

This version includes
ZenWiFi XT8, XD4, CT8
GT series: GT-AX11000, GT-AC5300, GT-AC2900
RT series: RT-AX88U, RT-AX92U, RT-AX86U, RT-AX82U, RT-AX58U, TUF-AX3000, RT-AX56U, RT-AX55
RT series: RT-AC5300, RT-AC88U, RT-AC3100, RT-AC86U, RT-AC68U


Due to compile problem, not in this version
ZenWiFi CD6, Lyra, Lyra mini, Lyra trio


Change log
- Fixed Let's encrypt register issue.
- Fixed packet loop problem in ethernet backhaul.
- To improve security, RT-AC68U starts to encrypt the NVRAM from this version.
Known issue: RT-AC68U needs to be reset to default to resolve the login problem after upgrading to this beta version.
If you want to downgrade to the previous version, you need to do it with rescue mode.
We are looking for a solution to this problem if you worry about this known issue, please wait for a further version and not update to this version.

Happy new year!

------------------------------------------------------------------------------------------------------------------------
Update 2020/12/01(9.0.0.4.386.41157)
https://drive.google.com/drive/folders/1D4X3k9GXxkiRQkaO1huQGnCAsQeIvokC?usp=sharing

This version inclouds
ZenWiFi: XT8(RT-AX95Q), XD4(RT-AX56U_XD4), CD6(RT-AC59_CD6)
GT series: GT-AX11000, GT-AC5300, GT-AC2900
RT series: RT-AX88U, RT-AX92U, RT-AX86U, RT-AX82U, RT-AX58U, TUF-AX3000, RT-AX56U, RT-AX55
RT series: RT-AC5300, RT-AC88U, RT-AC3100, RT-AC86U, RT-AC68U

Change log
1. Fixed WAN LED bug.
2. Fixed WiFi onboarding issues.
3. Fixed mac filter issue bugs.
4. Fixed time schedule bugs.
5. Fixed RT-AC88U/3100 ethernet backhaual bugs.


------------------------------------------------------------------------------------------------------------------------
Update 2020/11/12 (9.0.0.4.386.40947)
https://drive.google.com/drive/folders/1UHZwR1buG-nei8fne9d9OktOS2gZy6Hs?usp=sharing

This version includes 19 models:
ZenWiFi: XT8(RT-AX95Q), XD4(RT-AX56U_XD4), CD6(RT-AC59_CD6)
GT series: GT-AX11000,GT-AC5300, GT-AC2900
RT series: RT-AX88U, RT-AX92U, RT-AX86U, RT-AX82U, RT-AX58U, TUF-AX3000, RT-AX56U, RT-AX55
RT series: RT-AC5300, RT-AC88U, RT-AC3100, RT-AC86U, RT-AC68U

Change log
  1. Fixed Ethernet backhaul through switch issue
  2. RT-AX86 and GT-AX11000 support 2.5G port as ethernet backhaul
  3. Fixed RT-AX55 firmware update issue.
  4. Fixed speedtest issue for android app.
  5. Fixed mesh node guest network internet connection issue.
  6. Fixed ap mode guest network issue.
  7. Added security patch
  8. Fixed repeater mode UI bug.


------------------------------------------------------------------------------------------------------------------------
Update 2020/10/22 (9.0.0.4.386.40577)

This version includes 18 models:
ZenWiFi: XT8(RT-AX95Q), XD4(RT-AX56U_XD4)
GT series: GT-AX11000,GT-AC5300, GT-AC2900
RT series: RT-AX88U, RT-AX92U, RT-AX86U, RT-AX82U, RT-AX58U, TUF-AX3000, RT-AX56U, RT-AX55
RT series: RT-AC5300, RT-AC88U, RT-AC3100, RT-AC86U, RT-AC68U

Change log
1. Changed SDK and support more AX models.
2. You can see the speed test at the router app with firmware 386.40477 and the latest app on the app store/google play. Speed test page is at router app Settings tab --> QoS --> Internet Speed
3. Fixed Speedtest UI bugs
4. Enhance backhaul optimization algorithm


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 2020/10/08
If you want to test the new feature, Instant Guard.
Please check this thread https://www.snbforums.com/threads/asus-instant-guard-ios-public-beta.66814/

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 2020/10/06 386 rc2-6 (9.0.0.4_386_40322)

This version includes GT-AX11000, RT-AX92U, RT-AX88U, GT-AC5300, RT-AC5300, RT-AC88U, RT-AC3100, RT-AC86U, GT-AC2900, RT-AC86U, and RT-AC68U

Because of the SDK integration issue, this version does not include ZenWiFi XT8, ZenWiFi XD4, RT-AX86U, RT-AX82U, RT-AX58U, TUF-AX3000, RT-AX56U

Change logs:

- Fixed wireless backhaul retry issue after set the ethernet backhaul mode.
- Fixed slow web UI problem.
- Fixed UI problem in network map --> view list --> interface --> guest network
- Adjusted prefer AP connection mechanism.
- Fixed stack overflow vulnerability.

New Family interface in ASUS router App.
router firmware greater or equal to 9.0.0.4_386_40322
ASUS Router App greater or equal to iOS v1.0.0.5.75
Android greater or equal to v1.0.0.5.74

IMG_2279.PNG






------------------------------------------------------------------------------------------------------------------------------------
Update 2020/09/11 386 rc2-5 (9.0.0.4_386_40018)
https://drive.google.com/drive/folders/1Sqzva4uK7DTrp7oV93__LR6FZoDOckrN?usp=sharing

Change logs:
1. Add important patches for AiMesh backhaul and there are two FAQs for ethernet backhaul
What is Ethernet Backhaul Mode/connection priority in AiMesh system and how to set up in different scenarios?
[Wireless] How to setup ASUS AiMesh or ZenWiFi Mesh Ethernet backhaul under different conditions (Advanced setup with network switch)?

2. Clients which connect to the guest network can be viewed in the network map -->view list --> interface
Most of the routers have three sets of guest network and each set has 2.4G and 5G-1 (triband model has 5G-2)
POWERPNT_25Vf0tf9oD.png




3. Support IPSec IKE v1 and IKE v2, and you can use Windows 10 native VPN client program to connect to the router's IPSec VPN server.
The Windows 10 new FAQ is in https://www.asus.com/support/FAQ/1033576



4. Fixed stack overflow, File Traversal, XSS vulnerabilities.

Support models:
GT-AX11000
GT-AC5300
GT-AC2900
RT-AX92U
RT-AX88U
RT-AC86U
RT-AC68U
RT-AC3100
ZenWiFi XT8 (RT-AX95Q)

RT-AC5300 and RT-AC88U had some errors and we are going to fix it. The firmware will upload to the same link after fixed the problem





======================================================================================


Update 2020/08/14
https://drive.google.com/drive/folders/1twgcnXo_ywSZG2GU67V6Zl_T0RAyiBvb

Change logs:
1. Fix AiMesh page Tx/Rx 0 issue.
2. Add more wifi stability patches.
3. Apply new backhaul optimization mechanism.
4. Apply new client device recognize rules.

Now node which supports team port (link aggregation) can be enabled here:
teaming port.PNG


In AiMesh client list, click the "chain" icon, you will be able to select a preferable AP for this device. (* note: it's prefer ap, not bind)
bind 1.PNG





Update 2020/08/06

386 rc2-3 firmware is in this link
https://drive.google.com/drive/folders/154vHdrYh_rGP_qFooHgAkzXSJchge7Ue?usp=sharing

Change log:
1. Fixed node 5G connection problem (lots of complaints about this bug)
2. Improved IoT compatibility


known issues
1. Tx and Rx rate is still 0 in AiMesh Network fronthaul/backhaul information. We will fix this in the next build.
2. No RT-AX88U and RT-AX92U in this release. We are going to fix the build error problem.
3. Firmware extension numbers are different for different models. The range is from 386_39339 to 386_39348

Current Support models:
GT-AX11000
GT-AC5300
GT-AC2900
ZenWiFi XT8 (RT-AX95Q)
RT-AC5300
RT-AC88U
RT-AC3100
RT-AC86U
RT-AC68U
 
Last edited:

cc666

Senior Member
Since you cannot replies to posts on the original thread here is a continuation.

Why Asus has not released an updated beta firmware by now is puzzling. There are numerous
major problems with the latest release.

CC
 

massaquah

Occasional Visitor
I am only one small step away from replacing my XT8 with the Orbi6.
I came from the Orbi5 and never had such issues I am observing now....
 

Darren Rockach

Regular Contributor
All is quite stable for me now. Running RC2-9 on my AX11000 and RC2-10 on my two XT8 nodes.
I'm not aware of any problems with my current setup, all seems to be working better than it ever has. Even my wife's work laptop now connects to the WiFi without dropping every few minutes, that's something it's never done before so she is happy too.
 

sanke1

Senior Member
I am only one small step away from replacing my XT8 with the Orbi6.
I came from the Orbi5 and never had such issues I am observing now....
What issues are you having? The only issues I had were related to sucky Asus DDNS service. As soon as I started using No-IP service, all my instability issues vanished into thin air. Now I am running RC2-10 since 10 days with zero issues on AI mesh or anything.

 

massaquah

Occasional Visitor
What issues are you having? The only issues I had were related to sucky Asus DDNS service. As soon as I started using No-IP service, all my instability issues vanished into thin air. Now I am running RC2-10 since 10 days with zero issues on AI mesh or anything.

It's mainly a roaming issue.
My OnePlus 8 doesn't roam between my XT8 nodes but not from the start. After I reset the system (either with latest official firmware or RC) roaming is working and after a while it stops and the phone gets "sticky".
 

iAmNo0ne

New Around Here
I am only one small step away from replacing my XT8 with the Orbi6.
I came from the Orbi5 and never had such issues I am observing now....

I hear you. I’m waiting for Ubiquiti to release their UniFi WiFi 6 Mesh Points in Canada. Once that happens, I’m buying a UniFi Dream Machine Pro plus four WiFi 6 Mesh Points.

The issues with my XT8s is way too annoying now. Constant disconnects. Multiple times per day. It’s getting in the way of my evening university classes and my day job.

It was running okay for about a week after installing this latest beta, but then all the issues started to come back.
 

sanke1

Senior Member
It's mainly a roaming issue.
My OnePlus 8 doesn't roam between my XT8 nodes but not from the start. After I reset the system (either with latest official firmware or RC) roaming is working and after a while it stops and the phone gets "sticky".
I am having OnePlus 7 and no roaming issues between 2 RT-AX88Us.
 

The PyroPath

Occasional Visitor
Would you please tell me your settings for
- agile multiband
- smart connect
- roaming assistant
- channels
- beamforming?

Note from my side: I've observed erratic behavior with "smart connect" on since moving form my no longer supported RT-AC3200+2x different brand AP's to the AX88U+2x XT8 combo. This would result in the "sticky" connections he mentions. Almost as if the AImesh system doesn't know how to work the combination of a dual-band and a tri-band system. I ended up giving all 2.4 and 5 GHz networks the same SSID and enabling roaming assist. Played around a bit with the dB values for RA and now this works great. Smart Connect is a weird feature which is poorly documented and as far as I'm concerned shouldn't be enabled unless it works as advertised...
 

schumich

New Around Here
Hi,

i recently implemented AImesh with rt-ax88u as Router on 9.0.0.4.386.41157
Nodes:
1x rt-AC86u on 9.0.0.4.386.41157
1x rt-AC68u on 9.0.0.4.386.41157
1x rt-AC68u on 3.0.0.4.386.40558

I have massive problems (ping drops, 3-5 Mbit/s) with both AC68u on 2.4 and 5g when Guest-Wifi is enabled (not on Guest Network but the normal Wifi), no Problem on ac86u.
SmartConnect is disabled. Different SSID for 24 and 5.

Also, bandwidth limit on Guest-Wifi only workes on the main router none of the nodes, could anybody else replicate this issue?
 
Last edited:

sanke1

Senior Member
New day.. New Asus problem. @ASUSWRT_2020 why is my RT-AX88U trying to update ddns every 30 mins from no-ip.com ? It kicks me out of multiplayer game (Forza Horizon 4) when it is doing so.

Code:
Jan 14 20:58:47 ddns update: connected to dynupdate.no-ip.com (158.247.7.204) on port 443.
Jan 14 20:58:48 ddns update: request successful
Jan 14 20:58:48 ddns update: asusddns_update: 0
Jan 14 20:58:48 ddns: ddns update ok
Jan 14 20:58:48 ddns update: exit_main
Jan 14 21:16:52 wlceventd: wlceventd_proc_event(526): eth7: Auth E4:9A:DC:A3:D3:87, status: Successful (0), rssi:0
Jan 14 21:16:52 wlceventd: wlceventd_proc_event(536): eth7: ReAssoc E4:9A:DC:A3:D3:87, status: Successful (0), rssi:0
Jan 14 21:28:46 rc_service: dhcp6c 13937:notify_rc restart_ddns
Jan 14 21:28:46 start_ddns: update WWW.NO-IP.COM noip, wan_unit 0
Jan 14 21:28:46 ddns update: ez-ipupdate: starting...
Jan 14 21:28:47 ddns update: connected to dynupdate.no-ip.com (158.247.7.204) on port 443.
Jan 14 21:28:48 ddns update: request successful
Jan 14 21:28:48 ddns update: asusddns_update: 0
Jan 14 21:28:48 ddns: ddns update ok
Jan 14 21:28:48 ddns update: exit_main
Jan 14 21:58:46 rc_service: dhcp6c 17662:notify_rc restart_ddns
Jan 14 21:58:46 start_ddns: update WWW.NO-IP.COM noip, wan_unit 0
Jan 14 21:58:46 ddns update: ez-ipupdate: starting...
Jan 14 21:58:47 ddns update: connected to dynupdate.no-ip.com (158.247.7.204) on port 443.
Jan 14 21:58:49 ddns update: request successful
Jan 14 21:58:49 ddns update: asusddns_update: 0
Jan 14 21:58:49 ddns: ddns update ok
Jan 14 21:58:49 ddns update: exit_main
Jan 14 22:28:46 rc_service: dhcp6c 21418:notify_rc restart_ddns
Jan 14 22:28:46 start_ddns: update WWW.NO-IP.COM noip, wan_unit 0
Jan 14 22:28:46 ddns update: ez-ipupdate: starting...
Jan 14 22:28:47 ddns update: connected to dynupdate.no-ip.com (158.247.7.204) on port 443.
Jan 14 22:28:48 ddns update: request successful
Jan 14 22:28:48 ddns update: asusddns_update: 0
Jan 14 22:28:48 ddns: ddns update ok
Jan 14 22:28:48 ddns update: exit_main
Jan 14 22:30:04 wlceventd: wlceventd_proc_event(490): eth6: Deauth_ind 00:05:CD:F7:62:32, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 14 22:30:13 wlceventd: wlceventd_proc_event(490): eth7: Deauth_ind 30:A9:DE:DD:59:7C, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Jan 14 22:30:38 roamast: determine candidate node [04:D9:F5:FB:16:34](rssi: -44dbm) for client [E4:9A:DC:A3:D3:87](rssi: -69dbm) to roam
Jan 14 22:30:38 roamast: Roam a client [E4:9A:DC:A3:D3:87], status [0]
Jan 14 22:30:38 wlceventd: wlceventd_proc_event(507): eth7: Disassoc E4:9A:DC:A3:D3:87, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 14 22:30:38 wlceventd: wlceventd_proc_event(507): eth7: Disassoc E4:9A:DC:A3:D3:87, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 14 22:58:46 rc_service: dhcp6c 25225:notify_rc restart_ddns
Jan 14 22:58:46 start_ddns: update WWW.NO-IP.COM noip, wan_unit 0
Jan 14 22:58:46 ddns update: ez-ipupdate: starting...
Jan 14 22:58:47 ddns update: connected to dynupdate.no-ip.com (158.247.7.204) on port 443.
Jan 14 22:58:48 ddns update: request successful
Jan 14 22:58:48 ddns update: asusddns_update: 0
Jan 14 22:58:48 ddns: ddns update ok
Jan 14 22:58:48 ddns update: exit_main
Jan 14 23:28:46 rc_service: dhcp6c 29060:notify_rc restart_ddns
Jan 14 23:28:46 start_ddns: update WWW.NO-IP.COM noip, wan_unit 0
Jan 14 23:28:46 ddns update: ez-ipupdate: starting...
Jan 14 23:28:47 ddns update: connected to dynupdate.no-ip.com (158.247.7.204) on port 443.
Jan 14 23:28:48 ddns update: request successful
Jan 14 23:28:48 ddns update: asusddns_update: 0
Jan 14 23:28:48 ddns: ddns update ok
Jan 14 23:28:48 ddns update: exit_main
 

jstewart0131

New Around Here
I am running the following setup:
2x RT-AC5300 on 9.0.0.4.386_41535
Running AiMesh using ethernet backhaul
home details - Single story 3,2000sqft home

I am having two issues at the moment which have been going on with the last several beta builds.

Issue #1 I am having an issue with the 5Ghz-1 channel that seems to just stop transmitting data at random for any client that joins to the 5Ghz-1 channel. I do not seem to have issues with clients on 5Ghz-2 or the 2.4Ghz channels. If I switch to wireless backhaul and give the 5Ghz-2 channel back to the router for backhaul purposes, the issue with the 5Ghz-1 channel persists.

Issue #2 One just one of RT-AC5300's the WAN port seems to have died. The particular 5300 was being used as an Mesh node and suddenly I lost the wired backhaul. The node reported that the WAN connection was disconnected. I tried multiple known good working ethernet cables and multiple known good working devices and could not get a connection to be recognized on the WAN port. I then reset the configuration and then added the node back to the AiMesh setup and it again failed to see a connection on the WAN port. I next did a complete factory reset and then re-applied the latest beta to no avail. My current work around is that I swapped the two routers. The bad WAN port 5300 I moved to be the AiMesh Router and moved the previous router to be my wired backhaul node. I enabled dual wan and set the primary WAN to Ethernet port 1 and I was able to get my network up and running.


As far as timing of these two issues,issue #1 began and persisted before any issues with the WAN port failing in issue #2. Issue #2 may just bea run of the mill hardware failure.
 

RMerlin

Asuswrt-Merlin dev
Jan 14 21:58:46 rc_service: dhcp6c 17662:notify_rc restart_ddns

Because it seems your IPv6 lease changes every 30 minutes.

The DDNS update certainly isn't causing you to get disconnected. That IPv6 renewal is more likely the cause.
 

massaquah

Occasional Visitor
It's mainly a roaming issue.
My OnePlus 8 doesn't roam between my XT8 nodes but not from the start. After I reset the system (either with latest official firmware or RC) roaming is working and after a while it stops and the phone gets "sticky".

So for one second I thought I solved it.
After changing from WPA3 or WPA3/2 mixed to WPA2 only, the transition from the router to the "slave" node in the living room is working flawlessly at an RSSI level of around -62.
But not the other way round.
If the OP8 is connected to the slave and I am moving back to the router, the transition is only made after the RSSI is below -85 and I get a hard disconnect.

This is driving me nuts. Anyone else with an OP8 who can share his experience to pinpoint the issue and check if this is an XT8 or an OP8 problem?
 

KingBravery

Senior Member
So for one second I thought I solved it.
After changing from WPA3 or WPA3/2 mixed to WPA2 only, the transition from the router to the "slave" node in the living room is working flawlessly at an RSSI level of around -62.
But not the other way round.
If the OP8 is connected to the slave and I am moving back to the router, the transition is only made after the RSSI is below -85 and I get a hard disconnect.

This is driving me nuts. Anyone else with an OP8 who can share his experience to pinpoint the issue and check if this is an XT8 or an OP8 problem?
Please just use WPA2 only and avoid mixed or WPA3 alone. The WPA3 still not stable. That's the reason why many problem arise.
 

OzarkEdge

Part of the Furniture
So for one second I thought I solved it.
After changing from WPA3 or WPA3/2 mixed to WPA2 only, the transition from the router to the "slave" node in the living room is working flawlessly at an RSSI level of around -62.
But not the other way round.
If the OP8 is connected to the slave and I am moving back to the router, the transition is only made after the RSSI is below -85 and I get a hard disconnect.

This is driving me nuts. Anyone else with an OP8 who can share his experience to pinpoint the issue and check if this is an XT8 or an OP8 problem?

How far apart are your nodes?

OE
 

drabisan

Very Senior Member
How far apart are your nodes?

OE
Another idea from here: https://www.smallnetbuilder.com/wir...3200-smart-connect-the-missing-manual?start=1
My settings in Smart Connect are:
Window Time: 60 seconds
Counts: 2
Dwell Time: 180 seconds

My read is: a client can move between router-node only 2 times in 1 minute.
If it tries to move the 3rd time, it will not be able to do that smoothly.

I noticed that if I am moving through the house repeatedly in a short time window, roaming doesn't take place anymore. But I have no need to move that often other than for testing.

What you are describing may be due to this feature.
 

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