Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

[ginny]

Main Router LED can be changed on/off in the iOS app, but doesn’t show up in web interface like nodes

I deactivated the LED's using my way. The /jffs folder is nonvolatile and the data within /jffs survives are reboot or a power cylce. The steps below have only to be repeated after a factory reset.

telnet router.asus.com or ssh router.asus.com using putty (telnet works as well from a command prompt window)
enter the login credentials as used for the web GUI

nvram set script_usbmount="/jffs/LED-off.sh"
nvram commit

cd /jffs

Script LED-off.sh within /jffs

touch LED-off.sh
chmod 755 LED-off.sh

vi LED-off.sh
( push <esc> i
insert the lines below using the right mouse button

#!/bin/sh

# Deactivate LED's after 5 Minutes so I can see what happening after boot
sleep 300

nvram set AllLED=0
# I don't commit the nvram so the LED's are activated after a restart for 5 minutes

service restart_leds

push <esc> wq sto save and leave vi

After the next restart of the node or router the LED's are deactivated after 5 minutes

 

[bumpengrinder]

Smart Connect is not supported on AC1900/AC68/AC66 B1.

OE

Would this affect these models if employed as nodes, or is it only when they are acting as main router?

 

[rlj2]

Can understand your concern. I don't use it outside my network. There are a number of things different on the iOS app vs. web browser. I like how the iOS app shows which devices are connected to which node, which band, and current network traffic speeds. It presents Family management of device management cleaner than web, so I can hit one button to block access to a misbehaving child Time Scheduling and Content Block are grouped on the app vs. different places in web. A different app button can block all devices. Reboots of nodes have been possible for a while though iOS, but that's now in web version too. When not testing beta versions, firmware updates have been super simple.

semigator, I think we might have the same households. We deal with same client/mesh issues.. And half of my router issues is dealing with misbaving children , i have my sons ps4 ALWAYS classified as gaming (even if its streaming not so nice stuff) and thats at the bottom of the list

 

[OzarkEdge]

Would this affect these models if employed as nodes, or is it only when they are acting as main router?

I believe Smart Connect originates with the WiFi hardware and is then utilized by the OEM to affect band steering for a discrete router/AP... not for an entire mesh system. If a router/AP's hardware does not support SC, then there is no band steering for that node.

OE

 

[Srikanth]

ASUS,

I have 2 AC86U and both of them allow region change to a different country using web UI. When these 2 are connected in mesh, if I change the region on main router and select a 5g channel from that region, node is not able to connect because node still uses the default region. Shouldn't the node also change to the same region as main router ?

 

[L&LD]

#98 (snbforums.com)

 

[SoulSlayer]

I have RC8 with one AX88 and two XT8 nodes. Wifi6 is not available. Even with ethernet backhaul. Why? If i remove the two XT8 nodes i can connected with WiFi 6 to the AX88.

 

[bumpengrinder]

I believe Smart Connect originates with the WiFi hardware and is then utilized by the OEM to affect band steering for a discrete router/AP... not for an entire mesh system. If a router/AP's hardware does not support SC, then there is no band steering for that node.

OE

Thanks @OzarkEdge

 

[SasaSLO]

Asus rt-ax55 missing adaptive qos
Traditional qos max 250 Mb/s using 1 core
Bandwight limitter 300 Mb/s
My line is 600/60 Mb/s
Same on all firmwares

 

[1a1b1k]

ax86u failed to add a mesh node ac86u or tuf-ax3000 (wireless backhaul)，I will post the failed log later
ac86u sucees to add the same node tuf-ax3000 (wireless backhaul)
@ASUSWRT_2020


All of them run the lasete firmware 40947

 

[1a1b1k]

Fail log 1 ax86+ ac86u node:
Nov 22 15:01:09 rc_service: cfg_server 1593:notify_rc restart_obd_monitor
Nov 22 15:01:19 rc_service: cfg_server 1593:notify_rc stop_bsd
Nov 22 15:01:19 rc_service: cfg_server 1593:notify_rc start_wps_method
Nov 22 15:01:19 rc_service: waitting "stop_bsd" via cfg_server ...
Nov 22 15:01:48 wlceventd: wlceventd_proc_event(510): eth6: Auth 00:12:31:70:18:1B, status: Successful (0)
Nov 22 15:01:48 wlceventd: wlceventd_proc_event(539): eth6: Assoc 00:12:31:70:18:1B, status: Successful (0)
Nov 22 15:03:25 rc_service: cfg_server 1593:notify_rc start_bsd
Nov 22 15:03:53 WATCHDOG: [FAUPGRADE][auto_firmware_check7038)]retrieve firmware information
Nov 22 15:03:53 WATCHDOG: [FAUPGRADE][auto_firmware_check7041)]user in use

 

[1a1b1k]

fail log 2 ax86+ tuf-ax3000 node
Nov 22 15:04:27 rc_service: cfg_server 1593:notify_rc restart_obd_monitor
Nov 22 15:04:32 rc_service: cfg_server 1593:notify_rc stop_bsd
Nov 22 15:04:32 rc_service: cfg_server 1593:notify_rc start_wps_method
Nov 22 15:04:32 rc_service: waitting "stop_bsd" via cfg_server ...
Nov 22 15:04:35 wlceventd: wlceventd_proc_event(510): eth7: Auth 56A3:5B:E3:05, status: Successful (0)
Nov 22 15:04:35 wlceventd: wlceventd_proc_event(539): eth7: Assoc 56A3:5B:E3:05, status: Successful (0)
Nov 22 15:04:35 kernel: CONSOLE: 147896.508 wlc_ap_authresp: status 0
Nov 22 15:04:35 kernel: CONSOLE: 147896.510 wlc_ap_process_assocreq_done status 0
Nov 22 15:04:35 kernel: CONSOLE: 147896.514 iov:SCB_DEAUTH
Nov 22 15:04:35 kernel: CONSOLE: 147896.515 txrep:802.1x
Nov 22 15:04:36 kernel: CONSOLE: 147896.530 wl1.0: wlc_send_bar: for 56:da:d3:5b:e3:05 seq 0x1 tid 5
Nov 22 15:04:36 kernel: CONSOLE: 147896.532 txrep:802.1x
Nov 22 15:04:36 kernel: CONSOLE: 147896.537 iov:SCB_AUTH
Nov 22 15:04:36 kernel: CONSOLE: 147896.632 wl1.0: wlc_send_bar: for 56:da:d3:5b:e3:05 seq 0x1 tid 6
Nov 22 15:04:36 kernel: CONSOLE: 147896.729 wl1.0: wlc_send_bar: for 56:da:d3:5b:e3:05 seq 0x1 tid 0
Nov 22 15:06:00 kernel: CONSOLE: 147980.323 wl1: r0hole: tx_exp_seq 0x90, seq 0x91
Nov 22 15:06:38 rc_service: cfg_server 1593:notify_rc start_bsd

 

[Sjekke]

Installed the latest beta on my AX11000.

First impression:

• LAN LED light show up
• Speedtest works but speed is lower then expected
• iperf3 between Ipad Pro and NAS is unstable and slower then with ASUS software. Normally I get around 950Mbit

 

[Darren Rockach]

Installed the latest beta on my AX11000.

First impression:

• LAN LED light show up
• Speedtest works but speed is lower then expected
• iperf3 between Ipad Pro and NAS is unstable and slower then with ASUS software. Normally I get around 950Mbit

I also find that the speedtest shows a lower speed than expected. I think this is due mainly to a capacity issue with the test site or possible a router hardware constraint, sometimes trying a different test site will help. Generally though I use my xbox for performing speedtests as this seems more reliable.

 

[RMerlin]

or possible a router hardware constraint

This is a CPU limitation.

 

[cybrnook]

Speed test seems to be working fine on a GT-AX11000 with a 500/50 link:

 

[tkeung mo]

why is AC-5300 not getting any updates?

 

[Sjekke]

This is a CPU limitation.

If there is a CPU limitation maybe it’s better not 2 foresee this utility. Nevertheless when I perfom an Iperf3 on my internal network it‘s slower then with the factory firmware.
LED LAN is not working.

 

[bumpengrinder]

An issue as arisen in the last few days that wasn't there before: if laptop is connected to node, then streaming video halts for a few seconds, then runs normally for a few seconds, then halts for a few etc etc etc.

The issue is only on my main wireless network which is set up as Dual-Band Smart Connect (2.4 GHz and 5 GHz). All is well on my 2.4 GHz only guest network.

I am running a GT-AC2900 as main router (on RC2-7) and an RT-AC66U B1 as node (on RC2-7 for RT-AC68U). I see that RC2-8 is now available for the GT-AC2900 and that release 3.0.0.4.386.40558 is available for RT-AC68U, but from my understanding it is best to keep both routers on the same which is the reason I haven't upgraded. One last thing to mention: I am running wireless backhaul as wired backhaul isn't avaible for RT-AC66U B1 on RC2-7 (and as far as see there is nothing in the release notes for 3.0.0.4.386.40558 to suggest that this has been addressed).

I would be grateful for any thoughts before I do embark on the firmware update fun and games again.


Thank you.

I hereby sheepishly admit that I took the lazy route to solve this and acquired an RT-AC86U Black Friday bargain to use as the node. Now all is smooth, wired backhaul is working and, for the first time ever, I have a good signal to every corner of the house, where the RT-AC66U B1 couldn't quite reach. More to the point - the wife's streaming yoga back on track. A happy wife is a happy life. And that's worth way more than £85

For sale: one slightly questionable hardware revision of an RT-AC66U B1

 

[bumpengrinder]

I've just realized in fact that, entirely because of this thread, I have bought two new Asus routers. Could this whole beta thing be an elaborate sales ploy from Asus?! If so then good work Asus! I am quite happy - for the first time ever I am 100% satisfied with the wifi set up in my house!

(... now then, if only all of the guest networks could appear on the nodes...)