Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

[Manoel Mendes]

Good evening everyone! As I said, I came back to tell you a little about my experience with RT-AC88U with new RC3.
I currently use standard configuration, with no routers in the mesh or guest network. My connection is 300mb fiber, and the speeds on the Ookla are correct, I use in 5ghz selected on channel 149 with option only N / AC 80mhz. In network 2.4, I use channel 6 with automatic option 20 / 40.And both networks are working perfectly without disconnections or drop in speed, consumption of ram and processor are low. The only thing I noticed was that my smart TV does not disappear from the QOS list after being disconnected from the network.I hope I have been helpful with my functioning information, any other perception of problems I will post here. Any question I can be of assistance in, I would be happy to answer.
A great evening for everyone

 

[banger]

Anyone notice on the Bandwidth Tab if you have Apps Analysis on and click on the device icon it shows which apps are using bandwidth. Useful.

 

[Manoel Mendes]

Anyone notice on the Bandwidth Tab if you have Apps Analysis on and click on the device icon it shows which apps are using bandwidth. Useful.

Goodnight friend ! in my case clicking on the device icon does not show activity in the apps, and also does not respond to ping.

 

[banger]

Maybe this is not a feature of the AC88U only the AC68U?

 

[Neil62]

Anyone notice on the Bandwidth Tab if you have Apps Analysis on and click on the device icon it shows which apps are using bandwidth. Useful.

Where exactly is that if you don't mind me asking?

 

[dave14305]

Where exactly is that if you don't mind me asking?

Adaptive QoS > Bandwidth Monitor

 

[banger]

 

[GenericITGuy]

I have been working too much and stopped following the thread. I am running 39348 now in hopes it addressed my manual DHCP problem. It has not. Do we have sight on when that is planned?

 

[Neil62]

View attachment 25368

Got it, thanks

 

[Matthew Patrick]

View attachment 25368

It's been there for I think atleast a year hehe.. not new to this build I think

 

[Kiwipaul]

The list of Supported Asus Router Models for AIMESH 2.0 386 rc2-3 is even shorter then the last list. Is there a roadmap list of Routers that will be officially supported by AiMesh 2.0 when it is released? I have two 66U B1s, and one 68U, I am pretty sure my Blue Cave is not going to be supported (its the only router my wife allows in the living room) and I know for sure my primary router, my 3200 will not be supported. Most of my routers are refurbs or used, but i would like to buy a new primary router. I just want to be able to make a 3 year investment with some confidence. Thanks Dancinjammin

I too would like to know as I am about to purchase a new router. Asus, are you listening?

 

[gabzprime]

Can you control the transmit strength of the radios of each AP in AIMesh?

 

[drabisan]

Can you control the transmit strength of the radios of each AP in AIMesh?

No

 

[Manoel Mendes]

Maybe this is not a feature of the AC88U only the AC68U?

Goodnight friend ! this option is also present in the ac88u, i was referring to the problem of my smart tv, which even disconnected is still shown in the list of connected equipment.

 

[rickygao]

I have just noticed another bug:
All of the GUEST Wi-Fi connected devices are showing offline on ASUS iOS app.

@ASUSWRT_2020

 

[ASUSWRT_2020]

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.

 

[karma]

XT8, AP mode
Dirty flashed over previous beta, since it's not entire clear if the issues fixed in the changelog were supposed to impact the issues I reported:
- client node binding: issue remains, after reboot the clients bound to the node attach themselves to the main router. changing and saving any wifi option will move them back to the proper node.
- wireless backhaul: still only by setting control channel manually to 100 will it use 160Mhz. Still takes several minutes to connect to node.
- guest (i know, not mentioned in changelog): still not working, stuck at obtaining IP address.

feedback sent via router.

[edit, waiting to see how stable the backhaul is at 160Mhz, before it used to fallback to 80 after a while and after a channel being marked as unavailable]

[edit, positive note, 5ghz fronthaul on main router is at least 100-150Mbps faster for me, nice ]

 

[Neil62]

On applying a guest account there are some errors in the system log:

Aug 14 14:22:49 rc_service: httpd 1276:notify_rc restart_wireless;restart_firewall;
Aug 14 14:22:50 kernel: wfd_unregisterdevice Successfully unregistered ifidx 3 wfd_idx 0
Aug 14 14:22:50 kernel: wfd_unregisterdevice Successfully unregistered ifidx 3 wfd_idx 1
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds0.0.5.501^[[0m
Aug 14 14:22:50 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 0
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds0.0.5.0^[[0m
Aug 14 14:22:50 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 1
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds0.0.1.501^[[0m
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds0.0.1.0^[[0m
Aug 14 14:22:50 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.3.501^[[0m
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.2.501^[[0m
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.3.0^[[0m
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.2.0^[[0m
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.1.501^[[0m
Aug 14 14:22:50 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.1.0^[[0m
Aug 14 14:22:53 kernel: netdev path : eth5.0 -> eth5
Aug 14 14:22:53 kernel: BCMVLAN : eth5 mode was set to RG
Aug 14 14:22:53 kernel: netdev path : eth5.501 -> eth5
Aug 14 14:22:53 kernel: BCMVLAN : eth5 mode was set to RG
Aug 14 14:22:53 kernel: netdev path : eth6.0 -> eth6
Aug 14 14:22:53 kernel: BCMVLAN : eth6 mode was set to RG
Aug 14 14:22:53 kernel: netdev path : eth6.501 -> eth6
Aug 14 14:22:53 kernel: BCMVLAN : eth6 mode was set to RG
Aug 14 14:22:55 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
Aug 14 14:22:55 kernel: wfd_registerdevice Successfully registered dev wds1.0.1 ifidx 1 wfd_idx 1
Aug 14 14:22:55 kernel: Register interface [wds1.0.1] MAC: 40:b0:76:36:bd:44
Aug 14 14:22:56 kernel: wfd_registerdevice Successfully registered dev wds1.0.2 ifidx 2 wfd_idx 1
Aug 14 14:22:56 kernel: Register interface [wds1.0.2] MAC: 40:b0:76:36:bd:44
Aug 14 14:22:59 kernel: netdev path : wds1.0.1.0 -> wds1.0.1
Aug 14 14:22:59 kernel: BCMVLAN : wds1.0.1 mode was set to RG
Aug 14 14:22:59 kernel: netdev path : wds1.0.1.501 -> wds1.0.1
Aug 14 14:22:59 kernel: BCMVLAN : wds1.0.1 mode was set to RG
Aug 14 14:23:00 kernel: netdev path : wds1.0.2.0 -> wds1.0.2
Aug 14 14:23:00 kernel: BCMVLAN : wds1.0.2 mode was set to RG
Aug 14 14:23:00 kernel: netdev path : wds1.0.2.501 -> wds1.0.2
Aug 14 14:23:00 kernel: BCMVLAN : wds1.0.2 mode was set to RG
Aug 14 14:23:03 kernel: wfd_registerdevice Successfully registered dev wds0.0.4 ifidx 2 wfd_idx 0
Aug 14 14:23:03 kernel: Register interface [wds0.0.4] MAC: 40:b0:76:36:bd:40
Aug 14 14:23:05 roamast: ROAMING Start...
Aug 14 14:23:07 kernel: netdev path : wds0.0.4.0 -> wds0.0.4
Aug 14 14:23:07 kernel: BCMVLAN : wds0.0.4 mode was set to RG
Aug 14 14:23:07 kernel: netdev path : wds0.0.4.501 -> wds0.0.4
Aug 14 14:23:07 kernel: BCMVLAN : wds0.0.4 mode was set to RG
Aug 14 14:23:07 kernel: wfd_registerdevice Successfully registered dev wds0.0.6 ifidx 3 wfd_idx 0
Aug 14 14:23:07 kernel: Register interface [wds0.0.6] MAC: 40:b0:76:36:bd:40
Aug 14 14:23:08 kernel: wfd_unregisterdevice Successfully unregistered ifidx 3 wfd_idx 0
Aug 14 14:23:08 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds0.0.6.501^[[0m
Aug 14 14:23:08 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds0.0.6.0^[[0m
Aug 14 14:23:14 kernel: wfd_registerdevice Successfully registered dev wds0.0.6 ifidx 3 wfd_idx 0
Aug 14 14:23:14 kernel: Register interface [wds0.0.6] MAC: 40:b0:76:36:bd:40
Aug 14 14:23:18 kernel: netdev path : wds0.0.6.0 -> wds0.0.6
Aug 14 14:23:18 kernel: BCMVLAN : wds0.0.6 mode was set to RG
Aug 14 14:23:18 kernel: netdev path : wds0.0.6.501 -> wds0.0.6
Aug 14 14:23:18 kernel: BCMVLAN : wds0.0.6 mode was set to RG
Aug 14 14:23:21 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 1
Aug 14 14:23:21 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.2.501^[[0m
Aug 14 14:23:21 kernel: ^[[0;33;41m[ERROR vlan] vlanIoctl ,638: Failed to delete VLAN device wds1.0.2.0^[[0m
Aug 14 14:23:37 kernel: wfd_registerdevice Successfully registered dev wds1.0.2 ifidx 2 wfd_idx 1
Aug 14 14:23:37 kernel: Register interface [wds1.0.2] MAC: 40:b0:76:36:bd:44

My setup is as per my signature. I completed a dirty update across nodes and main with the latest RC released today.

In relation to above, I can though, still connect to the Guest Account and have internet access.

The above VLAN error, also appears on a reboot of all, i.e. via, Aimesh menu, system settings, system reboot, with a Guest Account enabled.

 

[Neil62]

A petty one, but ASUS (@ASUSWRT_2020), could we please match the last two options for the above "system settings" screen in the AiMesh menu, to be also in a "sentence case" as per the first 2 options. My OCD.

So far so good, everything remains stable and yes TX/RX rates are working across all. Have also noticed the TM issue (error), is no longer appearing.

Thanks again, for the another quick update.

 

[Neil62]

I have just noticed another bug:
All of the GUEST Wi-Fi connected devices are showing offline on ASUS iOS app.

@ASUSWRT_2020

I would unlink the app from the Main and then link it again to the main router. Has worked for me in the past.