Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

[OzarkEdge]

@ASUSWRT_2020, Again on the guest accounts, I have noticed that if you select remove account, the account is removed, but when clicking on "enable" again, the same account that was removed is returning. So it would seem the remove button, is actually not removing the account, it's in fact, picking up the account that was removed again. The removal process and enabling process was done without a reboot of the main router in between each step.

I recall seeing this on non-RC firmware.

OE

 

[OzarkEdge]

@ASUSWRT_2020 Another update, created a guest account only on the 2ghz band, can connect to it, shared it across Aimesh nodes, but getting no internet activity from the Guest account...

View attachment 25195

I wonder why the setting 'Sync [guest network] to AiMesh Node' exists.

OE

 

[joltdude]

Installed it last night, rebooted the routers, and let it go until this AM, everything seems to be coming back up and working mostly as expected... Sent a post update log from the overnight... Still taking it for a spin..... having devices try to switch on/off the guest network when using the workaround was starting to be grating (had regrets).. Thanks for the quick update and fix for the major issue..

Thanks
-J

 

[Dan Ljungberg]

@ASUSWRT_2020

Further update, I have noticed on a reboot of main, there is a Kernel crash: If my memory serves me right, its related to Trend Macro applications for which I have none/zero enabled.

Does anyone else have this issue without using any Trend macro applications for the same router?

ug 6 15:39:16 kernel: pgd = ffffffc014d43000
Aug 6 15:39:16 kernel: [00b5cc90] *pgd=0000000014c3c003, *pud=0000000014c3c003, *pmd=0000000000000000
Aug 6 15:39:16 kernel: CPU: 1 PID: 1409 Comm: conn_diag Tainted: P O 4.1.27 #2
Aug 6 15:39:16 kernel: Hardware name: Broadcom-v8A (DT)
Aug 6 15:39:16 kernel: task: ffffffc0171f4a80 ti: ffffffc014ddc000 task.ti: ffffffc014ddc000
Aug 6 15:39:16 kernel: PC is at 0xf67a016e
Aug 6 15:39:16 kernel: LR is at 0xf676b7fc
Aug 6 15:39:16 kernel: pc : [<00000000f67a016e>] lr : [<00000000f676b7fc>] pstate: 20030030
Aug 6 15:39:16 kernel: sp : 00000000ffb5c608
Aug 6 15:39:16 kernel: x12: 00000000ffffffff
Aug 6 15:39:16 kernel: x11: 00000000ffb5cb04 x10: 000000000000004a
Aug 6 15:39:16 kernel: x9 : 00000000ffffffff x8 : 0000000000b5cc94
Aug 6 15:39:16 kernel: x7 : 0000000000000000 x6 : 00000000ffb5cb18
Aug 6 15:39:16 kernel: x5 : 0000000000000073 x4 : 0000000000000004
Aug 6 15:39:16 kernel: x3 : 0000000000000000 x2 : 0000000000000001
Aug 6 15:39:16 kernel: x1 : 0000000000b5cc90 x0 : 0000000000b5cc94

Yes, I see the same after a reboot, and no Trend Micro applications running.

 

[ThaProZac]

Uh nice fast upd, but none for my ax92s that needed it. Waiting in exitement

 

[MadGoat]

Uh nice fast upd, but none for my ax92s that needed it. Waiting in exitement

I myself am looking forward to testing the AX92u update. I have a mesh that works great with these routers over 400ft to an out building. Living in the sticks I'm hoping "Spoof TTL" can work on the wan port (maybe be able to set TTL value? LTE is my only option up here) or at least look forward to a merlin release in the future! Awesome work to everyone, I look forward to providing some useful feedback!

 

[OzarkEdge]

I'm tapping out of AiMesh... my second 2018 China 86U just died with the same half-lit LAN 4 LED that my first 2018 China 86U died with earlier this year. Both lived on a UPS. Unfortunately, ASUS Support will not replace it out-of-warranty.

I've resurrected my 2012 N66U (Dark Knight rising) as a 2.4 media bridge (-69dBm and 216 Mbps at 77') to hook up my garage SIP phone. Good enough.

OE

 

[L&LD]

@OzarkEdge does swapping AC power adaptors get it going again? A UPS can't help/fix a power supply issue.

It's time to get an RT-AX58U instead? They can be found cheaper than the RT-AC86U many times during a month.

 

[OzarkEdge]

@OzarkEdge does swapping AC power adaptors get it going again? A UPS can't help/fix a power supply issue.

It's time to get an RT-AX58U instead? They can be found cheaper than the RT-AC86U many times during a month.

No, the power adapter works fine with my other 86U.

The UPS comment was to convey that my two dead 86Us never experienced bad power. They died internally on their own.

I'll hold on to my money for now. And my time. I hung in there for over two years with AiMesh 1.0. It won't hurt me to miss AiMesh 2.0 until WiFi6e ships.

OE

 

[L&LD]

And does the other 'AC86U's power adaptor work on the 'dead' one?

 

[OzarkEdge]

And does the other 'AC86U's power adaptor work on the 'dead' one?

Nope... the 'dead' one is dead. I was expecting it and it delivered.

I'd consider another 86U, if I see one on sale. But I'm not going to pay $190 just to test AiMesh 2.0.

OE

 

[Kiwipaul]

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

Will you support DSL-AC68U ? Looking to buy some as nodes.

 

[jsbeddow]

Will you support DSL-AC68U ? Looking to buy some as nodes.

Huh? Why buy the DSL variant only to use them as nodes? Wouldn't you just use normal RT-AC68U units (or your choice of several other models)?

 

[VANT]

Huh? Why buy the DSL variant only to use them as nodes? Wouldn't you just use normal RT-AC68U units (or your choice of several other models)?

especially as the price is higher than the RT-AC68u model

 

[Domdus]

@ASUSWRT_2020: Can you tell if the RP-AC55 - the only AiMesh supporting socket repeater (afaik) will receive AiMesh 2.0 and features at some point?

I would highly appreciate to have 802.11k/v support and coverage throughout my whole wifi build on two RP-AC55 and two RT-AC68U.

@Kiwipaul: Depends on your needs, the RP-AC55 might be an option for you if the price is important.

 

[Kiwipaul]

especially as the price is higher than the RT-AC68u model

Here in New Zealand nearly everyone has moved to a fibre connection so DSL is viewed as old fashioned. For this reason DSL - 68U's are readily available second hand at 2/3rds the price of a RT-68U.

So, before I go out and get another one to act as a node, will it be supported in Aimesh 2.0?

 

[karma]

XT8 - wireless backhaul will not connect or take a very long time with certain settings

this was already the case before the beta but I thought I would mention it here:
on 5GHz-2 backhaul if I enable 160Mhz and manually set the control channel to 100 it will take quite some time to connect the node via backhaul. This is the first time I was actually patient enough to wait and finally it connected and surprisingly at 160Mhz which it almost never does. Before I assumed it wasn't connecting at all since when I set the control channel to auto and Auto select channel including DFS channels enabled it connects after a couple of seconds but almost never at 160Mhz and only usually only the first 4 channels are NOT RADAR Sensitive, Passive.

feedback sent via router

[edit, out of curiosity I did an AI mesh system reboot, it took about 10 minutes for the wireless backhaul to connect and this time not at 160Mhz. It's strange that within such a short period of time the channel statuses would completely change. for some reason the setting reverted to autocontrol channel and dfs. sending feedback via router.]

 

[rickygao]

XT8 - wireless backhaul will not connect or take a very long time with certain settings

this was already the case before the beta but I thought I would mention it here:
on 5GHz-2 backhaul if I enable 160Mhz and manually set the control channel to 100 it will take quite some time to connect the node via backhaul. This is the first time I was actually patient enough to wait and finally it connected and surprisingly at 160Mhz which it almost never does. Before I assumed it wasn't connecting at all since when I set the control channel to auto and Auto select channel including DFS channels enabled it connects after a couple of seconds but almost never at 160Mhz and only usually only the first 4 channels are NOT RADAR Sensitive, Passive.

feedback sent via router

[edit, out of curiosity I did an AI mesh system reboot, it took about 10 minutes for the wireless backhaul to connect and this time not at 160Mhz. It's strange that within such a short period of time the channel statuses would completely change. for some reason the setting reverted to autocontrol channel and dfs. sending feedback via router.]

I had the same issue on manual channel selection

 

[Dan Ljungberg]

Still with full reset (WPS) and with factory default settings on both Router and Node.
No internet for clients connected with 5 GHz and 2.4 GHz to the Node, without 5 GHz Guest Network enabled.
All clients connected to Router works fine.
Sent Feedback.

 

[Compmaster1231]

Hi There,

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.

Am I missing something or is the RT-AC1900P not supported Thank you!