Reply To: DSL-AC68U – Support setup as AiMesh RE node/child (Beta) ASUS have kindly given myself access to the first beta for the DSL-AC68U to now act as a Child/Node within an Aimesh configuration. ‘Note: this is a beta so normal…

[Juicenut]

Thanks for the feedback.

Yes – with the RT-AC68U it had full bars on the 5Ghz backhaul while showing 1 bars 5Ghz backhaul for the DSL-AC68U when just feet apart. Looking at the available WiFi networks – the 5Ghz mesh network had 3 showing, 2 on channel 149 and the other on channel 52. I don’t seem to have Smart Connect available on the DSL-AC68U — perhaps that’s just the 86U?

I was running firmware version 9.0.0.4.384_56087-ga1d12f2 on the main DSL-AC68U and didn’t think of running both DSL’s on the same version (which I should have picked up on). So – removed both nodes, put the beta on the main router also and re-connected the two nodes. Same thing – 1 bar 5Ghz backhaul for the DSL-AC68U node.

I then noticed that there’s a newer stable version of the firmware – released 25/07/19 – Version 3.0.0.4.384_80766 that had a line in the release notes of “Fixed Aimesh Issues” plus a bunch of other fixes. So have now loaded that on to the main DSL router and have re-added the nodes (again). Have noticed now in the 5Ghz wifi options that the channel selection dropdown does not go as high as it did on the earlier firmware version. Could previously go to 149+. The 5Ghz backhaul link quality is now full bars when very close to the main router – so off to a good start. Have now moved it into place and has dropped a bar – but seems to be working.

Wired backhaul would be great – however cabling here is a challenge.

Will continue testing the beta firmware on the second (node) DSL-AC68U — while running the current stable release on the main DSL.

Main reason to have the network running smoothly right now is to have a baby monitor (Arlo Baby) steaming audio without any hitches – otherwise I get the death stare from my wife. :/ Before running with the 2nd node (DSL-AC68U) had some devices dropping out (with successful reconnects) and full drops and needing to reconnect. Sonos also was dropping out – alternatively complaining that bandwidth was a problem (which it shouldn’t have been) and other connectivity errors. Seemed to be a combination of roaming assistant settings plus poor connectivity. Hoping that the additional node would help. Could be a chance that the node connectivity issues aren’t anything to do with the beta firmware and all to do with the existing setup…

Fingers crossed the stability has improved. Over the last 45 mins of running the audio streaming has been pretty good. Will update any findings going forward.

You need to login in order to vote