What's new

Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Cool! Does this need a DEDICATED wireless backhaul or will a wireless backhaul that clients can connect to also works?
As drabisan said, it is dedicated for Tri-Band Routers and shared with Dual-Band. I just wanted to add that you can still opt to share with Tri-Band Routers too. I do that for a few devices, and see no decrease in performance or range. No other side effects either. I just wanted try and load it to the rim either.
 
With RC 6 on rt-ac86u, there is two Google home devices that refuse to connect to wifi, no matter what band. I just tried to factory reset one of the home-units without any luck.
Anyone else?
 
With RC 6 on rt-ac86u, there is two Google home devices that refuse to connect to wifi, no matter what band. I just tried to factory reset one of the home-units without any luck.
Anyone else?

So, they worked before RC2-6?

OE
 
I have an RT-AC68U in AP mode connected to the Verizon router using the WAN port as the main AiMesh router.
Another RT-AC68U is connected via its WAN port to the same Verizon router and added as AiMesh node. Both have latest RC6 installed..
When trying to set “Connection Priority” on the AiMesh node, it shows “Auto” and “1G WAN first”. There is no “Ethernet first” in the drop down. It was present in the 385 release FW. I assume this is because Ethernet backhaul is connected to the WAN port and not to a LAN port on the main AiMesh router. Indeed switching to “1G WAN first” seems to use the Ethernet connection as backhaul (connection icon changes to the Ethernet icon).
Just mentioning the slightly confusing change in the drop down in case anyone else has a similar setup.
 
I have an RT-AC68U in AP mode connected to the Verizon router using the WAN port as the main AiMesh router.
Another RT-AC68U is connected via its WAN port to the same Verizon router and added as AiMesh node. Both have latest RC6 installed..
When trying to set “Connection Priority” on the AiMesh node, it shows “Auto” and “1G WAN first”. There is no “Ethernet first” in the drop down. It was present in the 385 release FW. I assume this is because Ethernet backhaul is connected to the WAN port and not to a LAN port on the main AiMesh router. Indeed switching to “1G WAN first” seems to use the Ethernet connection as backhaul (connection icon changes to the Ethernet icon).
Just mentioning the slightly confusing change in the drop down in case anyone else has a similar setup.

I would not expect your AiMesh to work as described.

I would think it should be connected as such:

Verizon router <wired> AC68U in AP Mode/AiMesh root node <wired/wireless> AC68U AiMesh remote node

OE
 
So, they worked before RC2-6?

OE
Yes, without any problems for a year or longer on the routers official firmware. This started directly after flashing RC2-6 yesterday. I have four Google home units that continues to work, while two of them just refuse to, whatever I do... Strange.
One of the not connecting units is actually JBL Link Portable, and the other is a Google home mini. Same on both, getting error "This type of network isn't supported" during the setup after factory reset of both units.
 
Last edited:
Yes, without any problems for a year or longer on the routers official firmware. This started directly after flashing RC2-6 yesterday. I have four Google home units that continues to work, while two of them just refuse to, whatever I do... Strange.
One of the not connecting units is actually JBL Link Portable, and the other is a Google home mini. Same on both, getting error "This type of network isn't supported" during the setup after factory reset of both units.

I assume you already have done a factory reset with the initialize box ticket, and a new manual config (not read in some old backup...) after you installed the latest fw. So the router is in a good state...
 
I assume you already have done a factory reset with the initialize box ticket, and a new manual config (not read in some old backup...) after you installed the latest fw. So the router is in a good state...
No, I havn´t done any reset of main router, but I guess I have to just to exclude that it has something to do with it.

Edit: Guess what? The factory reset did solve the problem, great! I never thought it would... :)
 
Last edited:
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

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.


This looks great, I would love I proper guest networks on AiMesh nodes.

I wonder, has anyone has tried this on a RT-AC66U B1? This router is not listed as compatible but I ask because it works with the AsusWRT-Merlin firmware for the RT-AC68U (which is listed).

Something not clear to me - is this a beta for an upcoming official Asus release or is it unofficial? I'm not too bothered either way, but I am wondering whether or not to wait for a final release.
 
This looks great, I would love I proper guest networks on AiMesh nodes.

I wonder, has anyone has tried this on a RT-AC66U B1? This router is not listed as compatible but I ask because it works with the AsusWRT-Merlin firmware for the RT-AC68U (which is listed).

Something not clear to me - is this a beta for an upcoming official Asus release or is it unofficial? I'm not too bothered either way, but I am wondering whether or not to wait for a final release.

If you read this thread, it's clear that the AC68U firmware works on the AC66U B1. That question is answered several times... four now. And, that this is a beta test of Release Candidate firmware. I would assume they will release it if the test is successful. Meanwhile, it's running fine here... with guest WLANs... but I have not had any guests lately.

OE
 
Last edited:
Edit: Guess what? The factory reset did solve the problem, great! I never thought it would... :)

Yeah, that 'damned if you do, damned if you don't' factory default reset is so frustrating. Be sure to read about it.

I'm about to stop using 192.168.1.* and use the default 192.168.50.1 just so I have one less setting to configure.

OE
 
@ASUSWRT_2020

My main RT-AC86U is showing Tainted amas_lib when I use the beta firmware. Any suggestions? This has happened for the current and past versions of the beta RC. I thought it was fixed in the current one after a complete factory reset, but it is back. Shows in the log every few mintues. I have 3 RT-AC1900P AiMesh 2.0 nodes connected via Ethernet.

Oct 13 08:49:42 kernel: pgd = ffffffc006629000
Oct 13 08:49:42 kernel: [f7322b10] *pgd=0000000006e7b003, *pud=0000000006e7b003, *pmd=0000000006e33003, *pte=0000000000000000
Oct 13 08:49:42 kernel: CPU: 0 PID: 28555 Comm: amas_lib Tainted: P O 4.1.27 #2
Oct 13 08:49:42 kernel: Hardware name: Broadcom-v8A (DT)
Oct 13 08:49:42 kernel: task: ffffffc01dac5540 ti: ffffffc0075d0000 task.ti: ffffffc0075d0000
Oct 13 08:49:42 kernel: PC is at 0xf7299798
Oct 13 08:49:42 kernel: LR is at 0xf72d7a6c
Oct 13 08:49:42 kernel: pc : [<00000000f7299798>] lr : [<00000000f72d7a6c>] pstate: 20060010
Oct 13 08:49:42 kernel: sp : 00000000f7322b10
Oct 13 08:49:42 kernel: x12: 00000000f72e7f2c
Oct 13 08:49:42 kernel: x11: 0000000000000000 x10: 00000000001b78f8
Oct 13 08:49:42 kernel: x9 : 00000000f7324cf4 x8 : 0000000000000000
Oct 13 08:49:42 kernel: x7 : 00000000f72a75da x6 : 00000000f7322b1c
Oct 13 08:49:42 kernel: x5 : 00000000f732ece0 x4 : 00000000f732ece0
Oct 13 08:49:42 kernel: x3 : 00000000f72a75da x2 : 0000000000006efe
Oct 13 08:49:42 kernel: x1 : 0000000000001000 x0 : 00000000001901f2
 
Hi,
I was playing with IPSec VPN Configuration. On the iOS 14.0.1 VPN settings, there is a VPN Type option: IKEv2
May I know what is "Remote ID" annotated in the screen shot below, and Local ID too. I observe that "Remote ID" field appeared in the Windows 10 setup instruction. Thanks.

IMG_2990.PNG
 
No, I havn´t done any reset of main router, but I guess I have to just to exclude that it has something to do with it.

Edit: Guess what? The factory reset did solve the problem, great! I never thought it would... :)

You be surprised, just how many things can be fixed by factory reset.
 
If you read this thread, it's clear that the AC68U firmware works on the AC66U B1. That question is answered several times... four now. And, that this is a beta test of Release Candidate firmware. I would assume they will release it if the test is successful. Meanwhile, it's running fine here... with guest WLANs... but I have not had any guests lately.

OE

Hmm, sorry about that - I did search for the thread for AC66U first but there were no results, so thought I was clear to post. Good to hear your setup works, many thanks, that encourages me to take the plunge with this sooner (it means buying another compatible router, hence I am being careful to get it right).

I also need it to support VPN "Rules for routing client traffic through the tunnel" like Merlin does. Finding this out is my next quest but, again, I am not having much luck with the thread search (I have tried several permutations). I don't suppose there is a list of all features somewhere? If not, I will read through the thread. Thanks.
 
I also need it to support VPN "Rules for routing client traffic through the tunnel" like Merlin does.

'Like Merlin does' could be a stretch for stock beta-ware. :)

OE
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top