Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

[mekabe remain]

If you want to trial beta firmware, I would upload it to all nodes, reset all nodes, configure the router/root node from scratch, and add the remote nodes to build the AiMesh. Use the default router IP address or http://router.asus.com to login to the router/root node webUI.

Otherwise, upload the firmware of your choice and do similar.

OE

The problem is I am not able to upload any firmware because web UI does not respond.
I removed the Lyra mini from network (turned off) and main router (AC88U) still does not give access to web UI.
How can I upload previous firmware without Web UI ?

 

[OzarkEdge]

The problem is I am not able to upload any firmware because web UI does not respond.
I removed the Lyra mini from network (turned off) and main router (AC88U) still does not give access to web UI.
How can I upload previous firmware without Web UI ?

Did you try resetting the router to its factory defaults by pressing and holding the Reset Button until the power LED begins to flash?

OE

 

[mekabe remain]

I've managed to revert back with following method:

1.scp fw file to router
2.ssh
3. mtd-write2 firmware.trx linux && reboot

now it works as before.
but what's wrong with the RC7 ?

 

[jelome1989]

Installed the latest update a few hours ago and immediately ran into some problems.

Main: GT-AC5300
Node: GT-AC2900
(They are wired directly, no switches in between)

Problem:
Wireless clients can't see/connect to the node via the 5G-1 band when enabling Ethernet Backhaul Mode. 2.4g works fine. Tried to bind such clients to the node, no effect. It gets worse after that, when I try to connect back to the main router, I'm getting 'Incorrect Password' error. A workaround I found (for now), is to disable/enable Ethernet Backhaul Mode. Disabling it will immediately get the 5G-1 band to work again, and enabling it retains that status. Although sometimes it doesn't work, not sure why, and I remember at some point of the troubleshooting process I have to do a factory reset of both routers to get it to work again. What could I have done wrong?

Occurs:
Every reboot of the system (at least 3/3 in my case, will try rebooting again later)
After a factory reset of both routers, system works fine until I change settings of the 5G-1 band. Not sure which settings affect it though, don't want to find which exactly as of now, since I don't want to risk being forced to do another factory reset.

Other than that and overall, I like the new interface. Also the QoS upload limiter now works!

Hello everyone, an update -- I just rebooted my system. Again the clients can't see/connect to the node. Tried disabling/enabling Ethernet Backhaul, this time didn't work, and now including the 2.4G band.

Rebooted the system again, still can't connect, then again tried disabling/enabling Ethernet Backhaul Mode, and it worked.

Summary
1.) System working with Ethernet Backhaul mode; routers wired directly
2.) Reboot
3.) Clients can't see/connect to node, sometimes only to the 5G-1 band, sometimes both, binding doesn't work
4.) Disable/enable Ethernet Backhaul Mode; sometimes fixes the issue sometimes does not
5.) If system does not work in #4, then reboot and repeat #4 fixes the issue

This doesn't make sense. I haven't read all the pages, has there been an issue like mine?

Additional info:
1.) Smart connect is disabled
2.) Roaming assistant is disabled
3.) 5G SSID is hidden (whether I hide it or not, makes no effect)
4.) Clients are 5x+ smartphones (mix of iOS and Android, includes iPhone 6S Plus and 11); 1x Mac and 2x Windows Laptop (intel adapters)
5.) Channel bandwidth for all bands are fixed (2.4G - 20mhz; 5G-1 40mhz; 5G-2 80mhz)
6.) Control channels for all bands are fixed

 

[Vispen74]

Still on RC2-6 since a few weeks, works very well. The only things I've noticed is:
# Sometimes slow or interrupted network connection, re-connect client to WiFi solves it.
# Less coverage area of WiFi signal.
I will update to RC2-7 and see if any advantages.

 

[ginny]

Understood @ginny,
I have between router and node a Linksys SE2800 not because all the router port ar already used but because I have only one ethernet cable to 3rd floor and 2nd floor where is a linksys and only one cable from 2nd to 1st where is the node AC-88U...
what spec it must have the switch to work with AiMesh 2.0???

Hi PretorianADB

Sorry, regarding the spec for the switch i have no glue. As I saw somewhere in this tread, it has something with the VLAN handling to do. But it wasn't mentioned anything about the VLAN Id's.
In my case I squeezed a second Cat 6 cable towards the living room. Another possibility is to cascade the nodes. From the Routers LAN Port you connect to the WAN Port of one of your nodes. On that node, you take the LAN Port and connect it onto the WAN Port of the next node and so on.

Maybe this work in your case with only one LAN cable in your house wiring. On each node you can take it's LAN Ports to connect for other wired devices.

 

[bumpengrinder]

On my Win10 PC, which is connected to my GT-AC2900 (running RC2-7) by ethernet, the name "ASUS_60" is shown for the network connection. Is it possible to change this in the router, like we can for SSID? I have trawled the GUI settings but cannot find "ASUS_60" anywhere. I thought either "Host Name" or "GT-AC2900's Domain Name" under LAN settings might do it, but no.

 

[KrispiL]

I've been running RC2-7 on a AX88U as the main router and AX92U as the AiMesh node using 5G wireless backhaul now for a few days and it's all been generally stable. I am using a 2.4Ghz and 5Ghz guest network with intranet isolation enabled pushed out to the mesh node.

However I noticed this morning that devices, even those right next to the mesh node weren't connecting to it, but rather were connecting back to the main router. I checked the interface and it only showed 2 devices connected, one was wired and the other was on the primary (non guest) network. I tried reconnecting a device to the node and it connected but quickly fell back to the main router. These were the log entries:

Oct 26 12:19:05 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:19:05 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted}, status: Successful (0)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind 90:B9:31:B9:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(510): wl1.1: Auth 90:B9:31:B9:[Redacted], status: Successful (0)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc 90:B9:31:B9:[Redacted], status: Successful (0)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)

I power cycled the main router and mesh node and devices are now connecting back to the main node fine.

I've noticed other postings about the 'Unspecified reason' message before, has anyone got to the bottom of what is causing it?

 

[OzarkEdge]

On my Win10 PC, which is connected to my GT-AC2900 (running RC2-7) by ethernet, the name "ASUS_60" is shown for the network connection. Is it possible to change this in the router, like we can for SSID? I have trawled the GUI settings but cannot find "ASUS_60" anywhere. I thought either "Host Name" or "GT-AC2900's Domain Name" under LAN settings might do it, but no.

I believe that is a Windows Registry thing that gets started by a SSID name. I used to edit the registry to make it mine, but it changes so I gave up on it.

OE

 

[OzarkEdge]

I've been running RC2-7 on a AX88U as the main router and AX92U as the AiMesh node using 5G wireless backhaul now for a few days and it's all been generally stable. I am using a 2.4Ghz and 5Ghz guest network with intranet isolation enabled pushed out to the mesh node.

However I noticed this morning that devices, even those right next to the mesh node weren't connecting to it, but rather were connecting back to the main router. I checked the interface and it only showed 2 devices connected, one was wired and the other was on the primary (non guest) network. I tried reconnecting a device to the node and it connected but quickly fell back to the main router. These were the log entries:

Oct 26 12:19:05 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:19:05 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted}, status: Successful (0)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind 90:B9:31:B9:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(510): wl1.1: Auth 90:B9:31:B9:[Redacted], status: Successful (0)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc 90:B9:31:B9:[Redacted], status: Successful (0)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)

I power cycled the main router and mesh node and devices are now connecting back to the main node fine.

I've noticed other postings about the 'Unspecified reason' message before, has anyone got to the bottom of what is causing it?

Are they 2.4 devices? If so, try raising the Roaming Assistant 2.4 RSSI threshold to say -62.

OE

 

[KrispiL]

Are they 2.4 devices? If so, try raising the Roaming Assistant 2.4 RSSI threshold to say -62.

OE

Thanks for the suggestion OE, but no, they are connecting over 5Ghz. I will try changing the threshold on the 5Ghz channel if it starts happening again, it's been OK so far since the reboot.

 

[bumpengrinder]

I believe that is a Windows Registry thing that gets started by a SSID name. I used to edit the registry to make it mine, but it changes so I gave up on it.

OE

I just read that elsewhere, good to have confirmation, thanks. Likewise, I think I'll live with it - can't be bothered playing that game of whack-a-mole.


GT-AC2900 router + RT-AC66U B1 node still up and stable since last night.

 

[OzarkEdge]

RC2-7 guest client observation...

I have a Wyze cam 192.168.101.43 connected to a remote node 2.4 guest WLAN1... my first and only IoT device isolation. I can ping the cam from a root node LAN PC 192.168.1.34. I can stream the cam to a root node 5.0 WLAN client app (I believe via the Internet). The cam is not listed anywhere in the router webUI... this is probably my only point.

OE

 

[DarkKnight75]

Has the network map issue acting up been fixed in latest beta firmware? Issue appears in latest .386 ac86u firmware.

 

[YCY]

I've been running RC2-7 on a AX88U as the main router and AX92U as the AiMesh node using 5G wireless backhaul now for a few days and it's all been generally stable. I am using a 2.4Ghz and 5Ghz guest network with intranet isolation enabled pushed out to the mesh node.

However I noticed this morning that devices, even those right next to the mesh node weren't connecting to it, but rather were connecting back to the main router. I checked the interface and it only showed 2 devices connected, one was wired and the other was on the primary (non guest) network. I tried reconnecting a device to the node and it connected but quickly fell back to the main router. These were the log entries:

Oct 26 12:19:05 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:19:05 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:21:37 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted}, status: Successful (0)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:23:08 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind 90:B9:31:B9:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(510): wl1.1: Auth 90:B9:31:B9:[Redacted], status: Successful (0)
Oct 26 12:24:08 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc 90:B9:31:B9:[Redacted], status: Successful (0)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(474): wl1.1: Deauth_ind AE:65:E1:E7:[Redacted], status: 0, reason: Unspecified reason (1)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(510): wl1.1: Auth AE:65:E1:E7:[Redacted], status: Successful (0)
Oct 26 12:24:09 wlceventd: wlceventd_proc_event(520): wl1.1: ReAssoc AE:65:E1:E7:[Redacted], status: Successful (0)

I power cycled the main router and mesh node and devices are now connecting back to the main node fine.

I've noticed other postings about the 'Unspecified reason' message before, has anyone got to the bottom of what is causing it?

@ASUSWRT_2020 I have the same situation. My main route is AX88U ,Node is tuf-ax3000. Tried reconnecting a device to the node and it connected but quickly fell back to the main router and the signal of the main route of the test point is very weak, so it can not be connected to the Internet

 

[afool622]

@ASUSWRT_2020 My sonos speakers are not connecting after RC-7. Going back to RC4.

 

[RMerlin]

@ASUSWRT_2020 My sonos speakers are not connecting after RC-7. Going back to RC4.

Is Airtime Fairness disabled?

 

[afool622]

Is Airtime Fairness disabled?

Yes it is disabled

 

[RMerlin]

I know Sonos can be picky at times with wifi. Tried reconfiguring the wifi on the Sonos? The recent changes to the firmware's wifi may perhaps require a client reconfiguration.

Sonos Support

support.sonos.com

 

[ifisher]

Update 2020/10/22 (9.0.0.4.386.40577)

386 rc2-7 - Google Drive

drive.google.com

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)

386 rc2-6 - Google Drive

drive.google.com

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

View attachment 26693





------------------------------------------------------------------------------------------------------------------------------------
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)
View attachment 26147



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:
View attachment 25411

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)
View attachment 25412




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


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

Update 2020/7/28

Here we have new 386 rc2 beta for public test(so the old links are removed).
link: https://drive.google.com/drive/folders/1wvyQ240bX1m2zoP7fFIetofNyh2zp9CF?usp=sharing

Change log:
1. Fixed GT-AC5300, RT-AX92U, RT-AC86U, RT-AC68U AiMesh on boarding issue.
2. Fixed WPA3 connection issue with iphone 11.
3. Fixed/modified GUI. web history page fix, 2/5G on network map could be configured together.
4. Captcha for login can be disabled in administration -> system.
5. Printer server port can be disabled in USB app page.
6. Add RT-AC3100
7. Fix GT-AC5300 5GHz bandwidth issue

Support models:
RT-AC5300
RT-AC86U
RT-AC68U -> your are right, this models, this old model, we still support it.
RT-AX88U
RT-AC3100
RT-AC88U
RT-AX92U
GT-AC2900
GT-AC5300
GT-AX11000
ZenWiFi XT8 (RT-AX95Q)
(ZenWiFi CT8 will be later due to platform debugging.)

Be noted(Please read this before you use):

1. Although these are release candidates, but still under testing, there might be some bugs will cause system unstable, if you are facing issues, please leave your comments in this thread.
2. By using 9.0.0.x beta, it will not get live update from official path, you need to flash to official 3.0.0.x release to get latest updates.
3. To use full function AiMesh 2.0, all AiMesh nodes should be update to the 386-rc2 beta. If some of them are not, the functions will not work properly or limited.
4. For updating firmware manually please refer to: https://www.asus.com/support/FAQ/1035199/

What's new in 386-RC2

1. Supports 802.11k/v (ZenWiFi already adopted before, this is for RT GT models.)
2. AiMesh 2.0
- System optimization: one click in AiMesh topology to let topology re-org.
- System Ethernet backhaul mode, which is EAP mode, all nodes will use Ethernet as connection only, all bands will be released for coverage.
- System factory default and reboot.
- Client device reconnect, make device to offline and online again.
- Client device binding to specific AP.
- Guest WiFi on all Mesh nodes (only works on 2GHz -1 and 5GHz -1 guest network). (we know you are all waiting for this)
- Access nodes USB application. (Each node will have their own USB application server, it's not synchronized with Primary)
3. WiFi time scheduler now the unit goes to 1 minute.

Bug fixes:
1. VPN fusion bug fixes.
2. Offline client clean bug fixes.

Any chance for the RT-AX89X to be added to the supported models?