Beta ASUSWRT 386 RC2 public beta with full functions AiMesh 2.0

[karma]

VLAN is in 2021 roadmap.
For the generic user, VLAN is very hard to understand and causes lots of problems. We plan to make network group management instead of VLAN.
It will include guest network, bandwidth limiter ... etc.
It is not an easy project but will bring benefits to most users.

thanks very much for the update, sounds interesting and indeed very hard for the generic user to understand.

if you can, please keep in mind that some of us use the routers as access points with our own standalone firewalls which can manage vlans and would only need functionality like in a managed switch has where a vlan id can be assigned to a network interface. if I'm not mistaken something like that is already exists in router mode for iptv for the physical network interfaces (maybe i'm wrong about that, never used it and am not a network specialist ). I'm a relative newbie at all this so i hope i'm using the right terminology and concepts .

it's very cool that you guys are working on making the routers more versatile! thanks!

 

[VANT]

@o-l-a-v really thanks for this wish list. Some items are in 2021 roadmap and I would discuss with engineers again to rearrange the developer resource.

ASUSWRT_2020

If we are already at the list of wishes, I will ask the more down-to-earth ones "

-LED ON/OFF for main router
-eco mode also configured form router menu + scheduler, not only from app
-AD Blocker feature (Asus has already introduced such a function, but removed it for unknown reasons). Now people install third party fw and add this feature manually.


THX

 

[brummygit]

@o-l-a-v really thanks for this wish list. Some items are in 2021 roadmap and I would discuss with engineers again to rearrange the developer resource.

I would also agree that implementing Cake for routers that can support it would be a very good move. Just the basic settings "Best Effort" that require only the bandwidth values up & down similar to existing QoS would be amazing.

 

[Bee]

Is it just to implement the latest firmware (9.0.0.4.386.41157) into my Asus Zenwifi XT8 units to get the Guest network from the satellites as well? I don´t think it works. What else do I have to do? /New in this area

 

[Zorax]

Upgraded my ASUS Zenwifi XT8 system to 9.0.0.4.386.41157 and all my Sonos speakers started living their own lives. The speakers could not be found or controlled from the Sonos app anymore. Downgraded to 3.0.0.4.386.25790 and everything is working again.

 

[hancox]

Anyone else only seeing "1G WAN First" on backhaul preference? I'm on merlin's 386 Alpha 4, but i know AIMesh is closed source, so it should be common to the beta.

 

[OzarkEdge]

Anyone else only seeing "1G WAN First" on backhaul preference? I'm on merlin's 386 Alpha 4, but i know AIMesh is closed source, so it should be common to the beta.

No. Defaults to Auto here.

Clean installed RC2-9 from Firmware page...

o Uploaded remote node. Then upload of root node failed first time as it did before with RC2-8. Kicked out and tried and succeeded the second time. It fails immediately but the progress % bar continues to climb before it eventually kicks out:

o US Central Time Zone should default to 1st Sunday in Nov, yes? This is not a new/beta issue.

o Should Media Server and Network Share default to OFF for all nodes? Let the user enable these, if needed. This is not a new/beta issue except now it applies to all nodes.

o Failed adding remote node from new AiMesh page. Succeeded adding remote node from Network Map page the old way. 5.0 backhaul PHY rate is above 800 Mbps at 77 feet. This is the second time I've tried adding the remote node from the new AiMesh page and the second time it has failed. I'm not looking forward to losing the old AiMesh controls on the Network Map page!

o AiMesh system reboot kicked out to an incomplete render of the Network Map page that remained frozen until the reboot completed and the login page appeared.

I'm giving Smart Connect another trial with Roaming Assistant 2.4 RSSI raised to -55.

Thanks, Asus!

OE

 

[drabisan]

+1 for Media Server and Network Share default to be off by default! I found it minutes earlier and than I saw your post.
I get it it would make life easier for most users, but it's an annoyance for people that don't need that. I would call it borderline a security risk! If I don't enable a service on router, why would you enable it on node?

Another setting I just noticed: Bonding/ Link aggregation on node!
Makes sense by all means! Especially if there would be a 2.5 or 10G backhaul (I know there are 1-2 models with 2.5G interface so having 2 of those as router+node...). But with backhaul at 1G or AX speeds for most models, it doesn't make too much sense to enable link aggregation on node.
I wonder if it works to have a 2x1G backhaul by enabling on both sides link aggregation. I don't have 2 cables in between, but that would be an interesting testing scenario.

 

[hancox]

No. Defaults to Auto here.

Sorry, I wasn't specific enough. By "only 1G Wan" i meant that is have Auto + 1G Wan, but not ethernet. In prior builds i had ethernet to select. I also default to auto.

 

[OzarkEdge]

Sorry, I wasn't specific enough. By "only 1G Wan" i meant that is have Auto + 1G Wan, but not ethernet. In prior builds i had ethernet to select. I also default to auto.

1G Wan is Gigabit Ethernet, yes?

OE

 

[hancox]

1G Wan is Gigabit Ethernet, yes?

OE

Maybe? It doesn't match their own 386 FAQ ( https://www.asus.com/support/FAQ/1044184 ), and changed since 384.x, if so.

 

[OzarkEdge]

Maybe? It doesn't match their own 386 FAQ ( https://www.asus.com/support/FAQ/1044184 ), and changed since 384.x, if so.

I suppose it could mean legacy 1G cellular wireless from the early '90s.

Roll with it.

OE

 

[Domdus]

Dear @ASUSWRT_2020 and all,

I guess dealing with a compatibility issue here with the RP-AC55 added to my network (AiMesh 1.0 vs AiMesh 2.0) - did anybody experience problems with it?
The RP is on official firmware 3.0.0.4.384.83130 which supports AiMesh.

ASUSWRT_2020 I'm happy to test any 2.0 beta firmware for this RP device.

Since 2.0 for my 2x AC68U I see a ton of log entries for IP conflicts etc - as soon as the RP is added. Clients fail to resolve an IP via the RP, the connection works somethimes when the IP had been resolved on another node already.
Removing the Node RP again it all works perfect (after rebooting setup).

Setup (clean install):
- RT-AC68U AiMesh 2.0 Router (RC2-9/RC2-8/3.0.0.4.386.40558)
- RT-AC68U AiMesh 2.0 Node (RC2-9, wired backhaul)
(work perfect until here, now adding...)
- RP-AC55 AiMesh 1.0 Node (3.0.0.4.384.83130, wireless backhaul)

Case 1:
RP-AC55 Node <--> RT-AC68U Router
(MACs are clients)

Log:

Dec  1 23:00:39 kernel: 80:4E:70:21:FB:D0 not mesh client, can't update it's ip
Dec  1 23:54:17 kernel: D8:CB:8A:C4:47:29 not mesh client, can't update it's ip
Dec  1 23:56:20 kernel: 00:11:32:89:35:89 not mesh client, can't update it's ip
Dec  1 23:56:39 kernel: 60:45:CB:59:A2:B8 not mesh client, can't update it's ip
Dec  2 03:07:31 kernel: 54:60:09:D6:2D:B8 not mesh client, can't update it's ip
Dec  2 10:22:53 kernel: 80:4E:70:21:FB:D0 not mesh client, can't update it's ip
Dec  2 12:45:52 kernel: 80:4E:70:21:FB:D0 not mesh client, can't update it's ip
Dec  2 13:08:03 kernel: 80:4E:70:21:FB:D0 not mesh client, can't update it's ip
Dec  2 13:12:40 kernel: 80:4E:70:21:FB:D0 not mesh client, can't update it's ip

Case 2 (daisy chain):
RP-AC55 Node <--> RT-AC68U Node <--> RT-AC68U Router
(192.168.1.3 is RP itself, other IPs are clients that try connect or roam to the RP)

Log:

Dec  1 21:16:24 kernel: 192.168.1.133 already exist in UDB, can't add it
Dec  1 21:16:24 kernel: 192.168.1.55 already exist in UDB, can't add it
Dec  1 21:19:38 kernel: 192.168.1.133 already exist in UDB, can't add it
Dec  1 21:19:38 kernel: 192.168.1.55 already exist in UDB, can't add it
Dec  1 21:24:19 kernel: 192.168.1.133 already exist in UDB, can't add it
Dec  1 21:24:19 kernel: 192.168.1.55 already exist in UDB, can't add it
Dec  1 21:27:33 kernel: 192.168.1.133 already exist in UDB, can't add it
Dec  1 21:27:33 kernel: 192.168.1.55 already exist in UDB, can't add it
(thousends of lines...)
Dec  2 12:35:48 kernel: 192.168.1.49 already exist in UDB, can't add it
Dec  2 12:37:20 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:37:20 kernel: 192.168.1.49 already exist in UDB, can't add it
Dec  2 12:38:53 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:38:53 kernel: 192.168.1.49 already exist in UDB, can't add it
Dec  2 12:40:23 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:40:23 kernel: 192.168.1.49 already exist in UDB, can't add it
Dec  2 12:42:20 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:42:20 kernel: 192.168.1.49 already exist in UDB, can't add it
Dec  2 12:43:50 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:43:50 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:45:25 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:45:25 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:45:52 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:45:52 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:47:04 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:47:04 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:48:36 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:48:36 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 12:52:10 kernel: 192.168.1.3 already exist in UDB, can't add it
(...)
Dec  2 18:26:59 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:28:33 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:28:33 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:31:50 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:31:50 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:35:28 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:35:28 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:36:57 kernel: 192.168.1.3 already exist in UDB, can't add it
Dec  2 18:36:57 kernel: 192.168.1.3 already exist in UDB, can't add it

Thanks and BR

 

[Lord_Vader]

AC-88U working fine with RC9 through Zyxel switch as an ethernet node; didn't get it to work in RC8 - only wireless by default.
Great job, keep killing the bugs one after one!

 

[tallytr]

Upgraded my ASUS Zenwifi XT8 system to 9.0.0.4.386.41157 and all my Sonos speakers started living their own lives. The speakers could not be found or controlled from the Sonos app anymore. Downgraded to 3.0.0.4.386.25790 and everything is working again.

Sonos is weird, my Sonos One Speakers require 2.4GHz Wi-Fi B/G/N enabled, with only wireless N nothing works and that is on the regular released firmware (not AiMesh).

 

[karma]

Sonos is weird, my Sonos One Speakers require 2.4GHz Wi-Fi B/G/N enabled, with only wireless N nothing works and that is on the regular released firmware (not AiMesh).

depending on the sonos it will only do 802.11b/g, nothing to do with the router.

Sonos Support

support.sonos.com

 

[neruve]

Does anyone else have an issue with the speedtest in the QoS section? I can only get about 150-160 ish down on the router itself, but on my computer hooked to the same router gets 400 down.

 

[Bee]

Is it just to implement the latest firmware (9.0.0.4.386.41157) into my Asus Zenwifi XT8 units to get the Guest network from the satellites as well? I don´t think it works. What else do I have to do? /New in this area

Has anyone made this work? Do you have any suggestions on how to get your guest networks via satellites?

 

[David Williams]

Few issues noted (9.0.0.4.386_40947).

1. When you setup the multimedia USB it states iTunes: daemon is stoped. (Should be stopped).
2. Under Internet Speed Test. When I change to AT&T it shows AT&amp;T.
3. Would be nice on Internet Speed Test where you can select a default server. When ever I go back it always selects Auto. Would prefer to keep same server so that I know speed differences are not from a different ISP.
4. This is an issue that has been around forever. Why when doing a Router Security Assessment does Default Login Username and Password changed say No. I have changed password and to me that should be the only option or you should be able to state that you understand that username admin is default. If I change my password has been changed then this should be sufficient to pass the Router Security Assessment.
5. Are there any plans to add options to the Network Tools? For example NSLookup is just basic, would be nice to add some flags. Same with the other tools.

Thanks as always.

 

[mmacedo]

Has anyone made this work? Do you have any suggestions on how to get your guest networks via satellites?

I'm not in the latest beta yet, but I guess this hasn't changed: