Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

[BeeJayVee]

Well, although I really like some of the new features of RC2-6, I'm going to have to revert back to the released firmware for now. I'm getting too many instances of laptop and phone clients both getting dropped, and I also found that even though I manually set the channels for all bands, one time I found that the 2.4 band and the 5G-1 band either had some nodes (5G-1) or all nodes (2.4G) on the wrong channel (don't know if that is related to the clients being dropped). In addition, it's hard to change settings in the GUI, because in many cases a settings change causes the GUI to crash, requiring a main router reboot, so it takes forever to set up the network the way I want to.

But when the next build is made available I'll consider trying it. The new features are too good not to try.

 

[ASUSWRT_2020]

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

 

[Jayce Ooi]

Yeah... Love the binding feature. My laptop with Intel AX200 can finally get max speed by connected to AX88U only instead of AC86U sometime.

 

[RMerlin]

@ASUSWRT_2020 When you will fix Adaptive QoS because that garbage is broken and you need to use the script FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS to fix it and also update to fq_codel or Cake, stop being lazy and do things right.

Please keep it polite and civilized. Public insults are not tolerated.

 

[KingBravery]

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

For speedtest section, is it possible to add server search function or can scroll a bit more results?

 

[ligeza]

@ASUSWRT_2020 I Have still problem with nodes. Ac68u and ac86u are connected to switch, second ac86u as router also connected to the same switch. When I add or reboot aimesh node, both nodes are disconnected. If only one is connected there is no problem, RC2-7 and everything was formatted and set up from again. The same situation as RC2-6. I'm using ethernet backhaul mode. It helps if I disconnect ethernet cable from one node for about 10 second, and then both nodes are online until I reboot one of this nodes. I have also connected lira trio the same way and there is no problem with it.

I tried replace switch, but it didn't helped.

 

[ASUSWRT_2020]

@ASUSWRT_2020 I Have still problem with nodes. Ac68u and ac86u are connected to switch, second ac86u as router also connected to the same switch. When I add or reboot aimesh node, both nodes are disconnected. If only one is connected there is no problem, RC2-7 and everything was formatted and set up from again. The same situation as RC2-6. I'm using ethernet backhaul mode. It helps if I disconnect ethernet cable from one node for about 10 second, and then both nodes are online until I reboot one of this nodes. I have also connected lira trio the same way and there is no problem with it.

I tried replace switch, but it didn't helped.

Please provide me the switch model name. If we have a similar product, we can try to duplicate the problem.
Is your topology as follow?

 

[karma]

XT8 - AP mode - dirty flashed over latest production release

issue:
- guest wlan still stuck at obtaining IP address (patiently waiting for your internal AP mode round of testing/fixes, just thought I'd check )

fixed/positive:
- node binding: once the dedicated wireless backhaul is established devices seem to move the the bound node immediately

thanks for the release!

[edit, - client reconnect button doesn't seem to do anything.. client doesn't connect to preferred node. after an ai-mesh -> systems settings -> system reboot it connects to the preferred node]

[edit, takes a while for some clients to appear in the client list even though they are connected]

 

[ligeza]

Please provide me the switch model name. If we have a similar product, we can try to duplicate the problem.
Is your topology as follow?

I'm using TL-SG116E but I also tried GS108GE. Problem started if I good remember from RC2-5 installed on nodes. There is no problem with lyra trio. I can install older firmware on nodes and check latest working firmware if you need that information.

 

[Cheesehead]

I'm using TL-SG116E but I also tried GS108GE. Problem started if I good remember from RC2-5 installed on nodes. There is no problem with lyra trio. I can install older firmware on nodes and check latest working firmware if you need that information.

View attachment 27052

I have the same issue on a TP-Link TL-SG2424

 

[ASUSWRT_2020]

@ligeza and @Cheesehead
Let us exclude the cabling issue first. Do the network cables connect to nodes' WAN port?

 

[Cheesehead]

@ligeza and @Cheesehead
Let us exclude the cabling issue first. Do the network cables connect to nodes' WAN port?

yes for me — running on 4 XT8

 

[ligeza]

@ligeza and @Cheesehead
Let us exclude the cabling issue first. Do the network cables connect to nodes' WAN port?

Yes, all nodes connected to WAN port.
If I reboot one node the second one also disappear from aimesh.

 

[rickygao]

When upgrade from 9.0.0.4_386_39485 to 40577, my client devices start dropping from the node within 2 seconds, and then reconnect, drop, reconnect, drop into loop.
This happened to 40018 firmware as well, on both dirty upgrade and factory reset, included leave everything default settings
I was hoping this version can fix the issue, however I need to roll back to 39485 again, I have sent my feedbacks in the GUI.

below is my logs after a factory reset and default settings
Oct 22 22:29:57 wlceventd: wlceventd_proc_event(510): eth7: Auth xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:29:57 wlceventd: wlceventd_proc_event(539): eth7: Assoc xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:07 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Unspecified reason (1)
Oct 22 22:30:07 wlceventd: wlceventd_proc_event(510): eth7: Auth xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:07 wlceventd: wlceventd_proc_event(520): eth7: ReAssoc xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:17 wlceventd: wlceventd_proc_event(491): eth7: Disassoc xx:xx:71:0C:17:AF, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 22:30:17 wlceventd: wlceventd_proc_event(491): eth7: Disassoc xx:xx:71:0C:17:AF, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 22:30:18 wlceventd: wlceventd_proc_event(510): eth7: Auth xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:18 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Unspecified reason (1)
Oct 22 22:30:18 wlceventd: wlceventd_proc_event(510): eth7: Auth xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:18 wlceventd: wlceventd_proc_event(539): eth7: Assoc xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:36 roamast: [EXAP]Deauth old sta in 1 0: xx:xx:71:0C:17:AF
Oct 22 22:30:36 roamast: eth7: disconnect weak signal strength station [xx:xx:71:0c:17:af]
Oct 22 22:30:36 roamast: eth7: remove client [xx:xx:71:0c:17:af] from monitor list
Oct 22 22:30:36 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Oct 22 22:30:37 wlceventd: wlceventd_proc_event(491): eth7: Disassoc xx:xx:71:0C:17:AF, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 22:30:39 wlceventd: wlceventd_proc_event(510): eth7: Auth xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:39 wlceventd: wlceventd_proc_event(520): eth7: ReAssoc xx:xx:71:0C:17:AF, status: Successful (0)
Oct 22 22:30:48 roamast: [EXAP]Deauth old sta in 1 0: xx:xx:71:0C:17:AF
Oct 22 22:30:48 roamast: eth7: disconnect weak signal strength station [xx:xx:71:0c:17:af]
Oct 22 22:30:48 roamast: eth7: remove client [xx:xx:71:0c:17:af] from monitor list
Oct 22 22:30:48 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:49 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Class 3 frame received from nonassociated station (7)
Oct 22 22:30:55 wlceventd: wlceventd_proc_event(474): eth7: Deauth_ind xx:xx:71:0C:17:AF, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)

 

[gfondeur]

@ASUSWRT_2020 When you will fix Adaptive QoS because that garbage is broken and you need to use the script FlexQoS - Flexible QoS Enhancement Script for Adaptive QoS to fix it and also update to fq_codel or Cake, stop being lazy and do things right.

Damn, entitled much?

 

[LimJK]

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

Reporting on my RC2-7 Firmware Update exercise in my environment and my devices

My Configuration:
ISP: 1Gbps Fibre to Huawei ONT ->

• AiMesh Router: RT-AX88U (Year 2019) FW: 9.0.0.4_386_40577
• AiMesh Nodes (x2): RT-AC86U (Year 2020) FW: 9.0.0.4_386_40577
• Cat 7 Cables connecting AiMesh Router -> Linksys LGS108 Gigabit Switch -> both AiMesh Nodes

Observation:

• Fixed: Guest IP ADDRESS ASSIGNMENT displayed correctly in a different subnet from my Home Network (eg. 192.168.102.88) for MAC Address of devices that has been defined in the DHCP list (in network map --> view list --> interface --> guest network)
• Setup is very smooth in my environment (thanks), took 15 minutes to setup AiMesh Network from scratch
• Appeared to have slightly stronger 5GHz Band Signal strength of about 5-10 db , based on WiFi Explorer on MacBookPro measured from the same position since I started 386 RC betas.
• Have been running the last 4+ hours with no known issues for now.

Manually flashing new FW on AiMesh Nodes and AiMesh Router. Followed by Factory Reset of AiMesh Router / Nodes via GUI (AiMesh -> System Settings -> System Reset to Factory Default).

I use FW defaulted NVRAM values except the followings (all seems good):

• AiProtection “Enabled” for the following:
  • Malicious sites blocking
  • Vulnerability Prevention
  • Infected Device Prevention and Blocking
• USB Application “OFF” for the following, I use Synology NAS DS918+:
  • iTunes Server
  • UPnP Media Server
  • Samba Share
  • FTP
• WiFi: all default values, except:
  • My SSID / WPA Pre-Shared Key
• LAN: all default values, except:
  • DHCP Server: Enabled (with about 40 Manually Assigned IPs)
• WAN:
  • Asus DDNS (with Let's Encrypt),
• VPN Server: IPsecVPN Server: Enable, working with
  • MacBookPro 15” (macOS Catalina 10.15.7)
  • iPhoneXsMax (iOS 14.1)
• AiMesh 2.0 Backhaul Connection Priority -> Auto

Thank You!

 

[YCY]

@ASUSWRT_2020
MAIN: RT-AX88U-9.0.0.4.386.40577
NODE: TUF-AX3000-9.0.0.4.386.40577
Wireless Backhaul

After updating 40577，Node tuf-ax3000 cannot connect to any clients (iphone,ipad)

 

[OzarkEdge]

I notice that RT-AC86U RC2-2,3,4 are the exact same file size 67.6 MB (70,909,972 bytes), and RC2-5,6,7 are the exact same file size 68.0 MB (71,303,188 bytes). Hmmm... am I wasting my time?

OE

 

[OzarkEdge]

Now testing RC2-7... node backhaul drooped to 2.4 and log showed VLAN issues until system reboot. System reboot after clean install is advisable, imo.

Port 0 still only Closed on grc.com ShieldsUp! WAN test (?).

OE

 

[KingBravery]

@ASUSWRT_2020
MAIN: RT-AX88U-9.0.0.4.386.40577
NODE: TUF-AX3000-9.0.0.4.386.40577
Wireless Backhaul

After updating 40577，Node tuf-ax3000 cannot connect to any clients (iphone,ipad)

Have you done factory reset?