Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

KingBravery

Regular Contributor
@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?
 

RMerlin

Asuswrt-Merlin dev
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?

View attachment 27057

OE
Run md5 hashes, you'll see.
 

OzarkEdge

Part of the Furniture
We had better hurry up here... released AC86U firmware is catching up with its beta testing:

RT-AC86U RC2-7 beta is 9.0.0.4.386.40577.
RT-AC86U release is 3.0.0.4.386.40451.

OE
 
Last edited:

bitsbytes

Regular Contributor
Hello asus people. Any input on the new official firmware for the ac86u ? It's a jump to the 386 branch. How far is it from the latest beta?
 

karma

Regular Contributor
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
nothing is open, that's good, no?

[edit, oh, i see what you mean, it would be better if it was stealthed. parsed your sentence wrongly]
 
Last edited:

wags1

Occasional Visitor
Moabdave,

This is normally what I do, as I like to do Factory Reset for each new Firmware I installed. I am lazy, I have about 40+ devices that I manually assign IP address. The assumption here is there is a Thumbdrive (with name "ASUS") plugged into one of the USB port of the AiMesh Router. I saved about 10 other NVRAM items. I normally take about 15-30 minutes to setup my AiMesh network from scratch, hope it is useful for you.

First item, saved the DHCP_staticlist, Second item saved the icons you assigned to each device. I think these are the 2 most time consuming items.

Code:
———————————————————————————————————————————-
Save values:
———————————————————————————————————————————-
nvram get dhcp_staticlist > /tmp/mnt/ASUS/dhcplist.txt
nvram get custom_clientlist > /tmp/mnt/ASUS/custom_clientlist.txt
cp -r /jffs/usericon /tmp/mnt/ASUS/

———————————————————————————————————————————-
Restore values:
———————————————————————————————————————————-
cd /mnt/ASUS
nvram set dhcp_staticlist="`cat /tmp/mnt/ASUS/dhcplist.txt`"
nvram set custom_clientlist="`cat /tmp/mnt/ASUS/custom_clientlist.txt`"
cp -r /tmp/mnt/ASUS/usericon /jffs/
nvram commit && reboot
Edit: I added "custom_clientlist" that maps USER DEFINE DEVICE NAME to MAC ADDRESS, whereas the "dhcp_staticlist" maps MAC ADDRESS to USER ASSIGNED IP ADDRESS.
This may be very helpful. Would it be possible to write everything to a device on the network instead of a USB drive attached to the router?

Thank you for this. All my devices have custom names and icons. Restoring that information is the biggest PITA when doing a factory reset.
 

OzarkEdge

Part of the Furniture
nothing is open, that's good, no?

[edit, oh, i see what you mean, it would be better if it was stealthed. parsed your sentence wrongly]
Yeah, it comes and goes... it's been just Closed for awhile now. I don't know if it's the router or the ISP or grc.com. I assume it's the router.

OE
 
Last edited:

OzarkEdge

Part of the Furniture
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 (?).
View attachment 27059
OE
It's the router... AiProtection\Network Protection specifically. If I disable Network Protection, grc.com ShieldsUp! WAN test reports all ports Stealth:
1603387555579.png


It would nice of @ASUSWRT_2020 to comment on this.

OE
 

Quan

Occasional Visitor
After the upgrade to RC-7, my wifi card Realtek RTL 8821CE 802.11ac PCIe adapter was no longer able to connect to the XT8.
 

Darren Rockach

Occasional Visitor
I have an AX11000 and two XT8 nodes. The dedicated ethernet backhaul still seems to break things on rc2-7. I set it and then one of the nodes disconnected. I had to re-pair but everytime I did this whilst dedicated ethernet backhaul was enabled one of the nodes would drop off. Once the setting was disabled everything paired successfully again.
 

det721

Part of the Furniture
I see no speed test with RC-7, AX58U. Also had strange issues with setting icons in the network map. That seems to have resolved after reboot. Not a issue on standard releases.
 

OzarkEdge

Part of the Furniture
With RC2-7, my 2.4 mobile started acting up while streaming TuneIn outside my 2xAC86U AiMesh. I tried various things like disabling Smart Connect, deleting the TuneIn app data, and restarting my mobile. No joy. Then I recalled users recently mentioning stronger WiFi signals and raising the Roaming Assistant 2.4 RSSI threshold from the default of -70 to -62 (default used to be -55). So I did that and the issue stopped. So, I will try to come up with a rule for optimizing this setting for a given AiMesh geometry and signals.

However, I am still logging stuff like this:
Oct 22 15:36:38 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 90:C7:D8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 15:36:38 wlceventd: wlceventd_proc_event(510): eth5: Auth 90:C7:D8:90:85:59, status: Successful (0)
Oct 22 15:36:38 wlceventd: wlceventd_proc_event(539): eth5: Assoc 90:C7:D8:90:85:59, status: Successful (0)
Oct 22 15:36:39 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:36:39 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:37:12 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 90:C7:D8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 15:37:12 wlceventd: wlceventd_proc_event(491): eth5: Disassoc 90:C7:D8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:39:58 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 22 15:44:53 wlceventd: wlceventd_proc_event(510): eth5: Auth 90:C7:D

But that 2.4 client is working ok now.

OE
 

TXbreees

Occasional Visitor
Yay for updates! Feedback I sent through the feedback UI on the router:

"Thank your for letting the public do beta testing! Issues I've noticed with RC7: On the home screen, viewing connected clients then grouping by interface causes the interface to freeze for 10 to 30 seconds. This has been an issue for the last several releases. Throughput on the new AIMesh screen is still 0 kbps all the time. Attaching all logs for future release improvement!"
 

YCY

New Around Here
Last edited:

vanic

Regular Contributor
Hi OzarkEdge,

Thanks for your remind, actually, we have found the symptom in amas_lib. This issue has fixed in new beta firmware 386-40577. You could verify, thanks!

I have not enjoyed the same level of connection stability for my 2.4 mobile client while working around the property, now and before I switched to using Smart Connect. TuneIn regularly stops streaming with a connection error when normally it does not. If feels like RC2-6 has a connection management issue.

Here's an abbreviated snip from the General Log:

Oct 18 12:06:15 kernel: D8:D4:3C:0A:7A:A4 not mesh client, can't update it's ip
Oct 18 12:06:15 kernel: pgd = ffffffc011703000
Oct 18 12:06:15 kernel: [f6953510] *pgd=0000000011758003, *pud=0000000011758003, *pmd=00000000153c1003, *pte=0000000000000000
Oct 18 12:06:15 kernel: CPU: 0 PID: 31262 Comm: amas_lib Tainted: P O 4.1.27 #2
Oct 18 12:06:15 kernel: Hardware name: Broadcom-v8A (DT)
Oct 18 12:06:15 kernel: task: ffffffc01e86a080 ti: ffffffc013ef0000 task.ti: ffffffc013ef0000
Oct 18 12:06:15 kernel: PC is at 0xf6998a58
Oct 18 12:06:15 kernel: LR is at 0xf6996728
Oct 18 12:06:15 kernel: pc : [<00000000f6998a58>] lr : [<00000000f6996728>] pstate: 600f0010
Oct 18 12:06:15 kernel: sp : 00000000f69534f8
Oct 18 12:06:15 kernel: x12: 0000000000000000
Oct 18 12:06:15 kernel: x11: 00000000f6955ad4 x10: 0000000000000002
Oct 18 12:06:15 kernel: x9 : 00000000f6d82c92 x8 : 00000000f6a91000
Oct 18 12:06:15 kernel: x7 : 00000000f6955b20 x6 : 00000000f6a91cc0
Oct 18 12:06:15 kernel: x5 : 00000000f6a91cc0 x4 : 00000000f69535c0
Oct 18 12:06:15 kernel: x3 : 00000000000f7db0 x2 : 00000000f6955ae8
Oct 18 12:06:15 kernel: x1 : 00000000f6d82c92 x0 : 00000000fbad8004

<snip>
Oct 18 12:07:08 rc_service: amas_lib 31300:notify_rc restart_firewall
Oct 18 12:58:03 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Oct 18 12:58:06 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Oct 18 13:15:09 roamast: determine candidate node [D4:5D:64:7B:5F:61](rssi: -52dbm) for client [90:C7:D8:90:85:59](rssi: -68dbm) to roam
Oct 18 13:15:09 roamast: Roam a client [90:C7:D8:90:85:59], status [0]
Oct 18 13:15:10 wlceventd: wlceventd_proc_event(469): eth5: Deauth_ind 90:C7:D8:90:85:59, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Oct 18 13:15:10 wlceventd: wlceventd_proc_event(486): eth5: Disassoc 90:C7:D8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 18 13:23:31 wlceventd: wlceventd_proc_event(505): eth5: Auth 90:C7:D8:90:85:59, status: Successful (0)
Oct 18 13:23:31 wlceventd: wlceventd_proc_event(534): eth5: Assoc 90:C7:D8:90:85:59, status: Successful (0)
Oct 18 13:26:48 wlceventd: wlceventd_proc_event(486): eth5: Disassoc 90:C7:D8:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 18 13:26:48 wlceventd: wlceventd_proc_event(505): eth5: Auth 90:C7:D8:90:85:59, status: Successful (0)
Oct 18 13:26:48 wlceventd: wlceventd_proc_event(534): eth5: Assoc 90:C7:D8:90:85:59, status: Successful (0)
Oct 18 13:26:48 kernel: 90:C7:D8:90:85:59 not mesh client, can't update it's ip
Oct 18 13:26:48 kernel: pgd = ffffffc0117a6000
Oct 18 13:26:48 kernel: [f77cf510] *pgd=0000000009e0d003, *pud=0000000009e0d003, *pmd=000000001163b003, *pte=0000000000000000
Oct 18 13:26:48 kernel: CPU: 0 PID: 18021 Comm: amas_lib Tainted: P O 4.1.27 #2
Oct 18 13:26:48 kernel: Hardware name: Broadcom-v8A (DT)
Oct 18 13:26:48 kernel: task: ffffffc017671480 ti: ffffffc010d4c000 task.ti: ffffffc010d4c000
Oct 18 13:26:48 kernel: PC is at 0xf6f2ca58
Oct 18 13:26:48 kernel: LR is at 0xf6f2a728
Oct 18 13:26:48 kernel: pc : [<00000000f6f2ca58>] lr : [<00000000f6f2a728>] pstate: 600f0010
Oct 18 13:26:48 kernel: sp : 00000000f77cf4f8
Oct 18 13:26:48 kernel: x12: 0000000000000000
Oct 18 13:26:48 kernel: x11: 00000000f77d1ad4 x10: 0000000000000002
Oct 18 13:26:48 kernel: x9 : 00000000f7316c92 x8 : 00000000f7025000
Oct 18 13:26:48 kernel: x7 : 00000000f77d1b20 x6 : 00000000f7025cc0
Oct 18 13:26:48 kernel: x5 : 00000000f7025cc0 x4 : 00000000f77cf5c0
Oct 18 13:26:48 kernel: x3 : 00000000000f7db0 x2 : 00000000f77d1ae8
Oct 18 13:26:48 kernel: x1 : 00000000f7316c92 x0 : 00000000fbad8004

<snip>
Oct 18 13:54:01 rc_service: amas_lib 18035:notify_rc restart_firewall

I've made bold some suspicious entries... the first D8:D4:3C:0A:7A:A4 is a SONY AVR wired to the root node... the second 90:C7:D8:90:85:59 is my 2.4 mobile client. There is only one weak 2.4 ch9 20MHz WiFi signal overlapping my ch11 signals.

OE
 

CrashXRu

Occasional Visitor
not found util iperf3
 

YCY

New Around Here
@ASUSWRT_2020 After resetting many times and testing N times, the node tuf-ax3000 still can't connect to any client and has to go back to the version 3.0.0.4.384.9923
 
Last edited:

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