What's new

ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

ASUSWRT_2020

Occasional Visitor
Hi There,
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


POWERPNT_ZlJp9OLYK4.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

POWERPNT_vf3my7Tm5n.png


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


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

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.
 
Last edited:

jsbeddow

Senior Member
Pretty cool developments, can't wait to finally try these long awaited 386 versions once they are finalized as a general release in the form of an @RMerlin firmware (once some more time goes by waiting for the GPL of course).:):cool:
 

RMerlin

Asuswrt-Merlin dev
Pretty cool developments, can't wait to finally try these long awaited 386 versions once they are finalized as a general release in the form of an @RMerlin firmware (once some more time goes by waiting for the GPL of course).:):cool:
Keep in mind that it will take a fair amount of time, as I have to merge roughly 1 year of code changes on top of my own code. Last time with the 380 -> 382 jump I ended up restarting the project from scratch. I'll need to evaluate things once I get my hands on the GPL (Asus and I are already discussing it, so no need to poke at them about it).

For now, I strongly recommend people test these Asus betas, and help track down any issue so they have them resolved. Make sure you make a backup of your config BEFORE flashing these, so if you decide to go back, you will be able to recover your configuration.
 

Sanna1967

Senior Member
Flashed and so far this fw is running very well . The new Aimesh Section is nice
 

jsbeddow

Senior Member
Keep in mind that it will take a fair amount of time, as I have to merge roughly 1 year of code changes on top of my own code. Last time with the 380 -> 382 jump I ended up restarting the project from scratch. I'll need to evaluate things once I get my hands on the GPL (Asus and I are already discussing it, so no need to poke at them about it).

For now, I strongly recommend people test these Asus betas, and help track down any issue so they have them resolved. Make sure you make a backup of your config BEFORE flashing these, so if you decide to go back, you will be able to recover your configuration.
Yes, I wasn't expecting a release from you in the short term (or near future?), but I do have my fingers crossed for sometime before this miserable year is over :eek::rolleyes::).
Stay safe everyone.
Edit: While I am strongly tempted to try out the new features in this public Beta, I am not sure I can do without the extras provided by @RMerlin for now, so I will likely have to sit on the sidelines.
 

RMerlin

Asuswrt-Merlin dev
Edit: While I am strongly tempted to try out the new features in this public Beta, I am not sure I can do without the extras provided by @RMerlin for now, so I will likely have to sit on the sidelines.
You could temporarily turn your AiMesh node into an AP or even a router (in double NAT) just to give it a spin.
 

jsbeddow

Senior Member
You could temporarily turn your AiMesh node into an AP or even a router (in double NAT) just to give it a spin.
Hmm...intriguing idea, but isn't it explicitly stated in the original post that both AiMesh units (the router and node) have to be running the new 386 code to benefit from most (or nearly all) of the new enhancements (I'm thinking of 802.11k/v in particular)?

Edit: Nevermind: I just re-read the original post now, it would appear that the primary loss from not running on both units would be some missing AiMesh 2.0 features. More to think about....
 
Last edited:

Smokindog

Senior Member
Perhaps I missed it in the discussion but is there a published list of models that will eventually be supported or is the Beta list in the OP that list? Specifically I don't see the RT-AC3100 listed.

TIA
 

RMerlin

Asuswrt-Merlin dev
Hmm...intriguing idea, but isn't it explicitly stated in the original post that both AiMesh units (the router and node) have to be running the new 386 code to benefit from most (or nearly all) of the new enhancements (I'm thinking of 802.11k/v in particular)?
The idea is to temporarily use it as an AP or a router instead of an Aimesh node, just to do some basic testing with the new firmware, without affecting your primary router. APs don't need to use any specific firmware version to connect to the main router.

The new roaming capabilities will indeed need all nodes to support 802.11k/v.
 

RMerlin

Asuswrt-Merlin dev
no AC88U ?
I think I saw a beta build on their Onedrive folder, have a look.

Also keep in mind these are betas. They might not necessarily have the time to provide builds for every single models, so they probably focus on a few that cover the different platforms.
 

lilstone87

Senior Member
I'm curious to try the build for the AX88U. As I wonder if Asus fixed upstream wifi traffic being processed by Adaptive QoS. As Adaptive QoS is pretty useless right now, when wifi devices can max out upstream bandwidth. Because this traffic oddly bypasses Adaptive QoS.
 

Matthew Patrick

Senior Member
Is it possible for SmartConnect to adopt 802.11 k/v?? That would be awesome to have on SmartConnect..

Also what models support the k/v standards??
 

Matthew Patrick

Senior Member
All models with 386 rc2 firmware support the k/v standards. 802.11 v is for SmartConnect. 802.11k helps devices search quickly for nodes.
Oh nice!!

So that means this V/K support will benefit us without AIMesh yeah? So that means this will benefit SmartConnect feature on its own with it steering clients to 5ghz and back to 2.4? Thank you

Also I've noticed on the last few version. That we can change manual channel for SmartConnect. Is it gonna be staying or ? Since it's a very good feature
 

brummygit

Senior Member
I'd be interested in testing on my RT-AX88U however I use RT-AX56U AiMesh nodes. I'm reading that it needs the nodes also running 386 beta and that the RT-AX56U beta isn't yet available (I'm hoping it will receive 386 at some point)?

Is there any further information available on changes included in 386 - I'm interested if traffic queueing or Adaptive QoS has been improved / changed?
 

VANT

Very Senior Member

HellDiver

Occasional Visitor
I'd be interested in testing on my RT-AX88U however I use RT-AX56U AiMesh nodes. I'm reading that it needs the nodes also running 386 beta and that the RT-AX56U beta isn't yet available (I'm hoping it will receive 386 at some point)?
Amen to that - the 56U is a brilliant device for the price.
 

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