2.4GHz not being distributed on AIMesh node w 10GbE backhaul

[chA]

The following is my AIMesh setup:

• BE96U primary router
• 2x BE7200U (BE88U) satellite nodes – 1st node is using 10GbE backhaul; 2nd node is using wireless 5GHz backhaul
  • Due to different backhaul configurations, I am unable to choose the universal "Ethernet Backhaul Mode" in the AIMesh System Settings (if that matters)
• All devices running the latest 3006_102.5_alpha2-g2bdc88d5c5 build
  • Have experienced issues dating back to the three previous builds of Asuswrt-Merlin installed (3006_102.4_0, 3006_102.4_beta2, and 3006_102.3_0)

For some time now, I've been having issues with some devices connecting to a suboptimal node. As in I can be in the same room as my 10GbE-backhaul satellite node and the client device will connect to the 5GHz wireless-backhaul satellite node all the way in the opposite corner of my property. This is especially true of devices which only connect to the 2.4GHz band. On the 10GbE backhaul-connected BE7200U node, all downstream wired clients operate without issue. But the 2.4GHz radio on this AIMesh node doesn't appear to even be visible. Like at all. I have 2.4GHz-only devices in the same room which cannot connect to this node even after manual binding. These devices will default to a node much further away where the 2.4GHz radio operates decently, but suboptimally.

Looking into this issue deeper, I recently scanned for available nearby networks using NetSpot. The 10GbE-backhaul node is broadcasting on the 5GHz radio, but none of the 2.4GHz SSIDs are getting relayed. I have separate 2.4GHz and 5GHz SSIDs, along with a 2.4GHz-only IoT-dedicated VLAN and 2.4GHz + 5GHz child VLAN. This should result in 15 SSIDs found when scanning, but only 12 are found, with the three missing being the 2.4GHz-only SSIDs broadcast from this 10GbE-backhaul node. Also somewhat alarmingly, I am seeing similar issues with 2.4GHz SSID detection from the BE96U, even though I am currently running NetSpot from the same room as this router is located.

I'm truly at a loss as to what is happening here. Any help would be appreciated. Please see the attached pics for more details.

 

[bbunge]

The general recommendation is to run the AiMesh nodes on Asus firmware. For mixed backhaul leave the settings on the nodes at default. Let the router and nodes select what they want to use for backhaul. I would also recommend removing both nodes, after you flash them to the Asus firmware, factory reset the router and manually configure it, use the SmartConnect and leave the WIFI settings at default. Then add the nodes. I would add both nodes not connected to the Ethernet then move the First Floor node to its place and connect it to the Ethernet. Once the AiMesh nodes are connected add any guest WIFI networks. I would also set the 2.4 GHz bandwidth to 20 MHz but leave it on Auto Channel.
If this does not work you should put the router on Asus firmware as it should work as intended.

 

[Tech9]

All devices running the latest 3006_102.5_alpha2-g2bdc88d5c5 build

- unsupported firmware
- run stock Asuswrt on nodes

use the SmartConnect... Auto Channel

- avoid Smart Connect
- use fixed channels only

 

[bbunge]

- avoid Smart Connect
- use fixed channels only

Mmmm... not for initial set up. Just because you do not like or use it does not mean I can't recommend its use. My network runs just fine this way. Even with an AiMesh node added!

 

[Tech9]

Your router doesn't even have the same initial setup as RT-BE96U. After 37xxx firmware there is a new Network menu and Smart Connect setup is different. And your common Auto channel advice for 2.4GHz band is totally wrong for users with many IoT devices. Auto channel for users in countries with different power on different 5GHz channels and multiple APs is also totally wrong unless the system has per AP power control. AiMesh doesn't. "Works for me" in the US (region specific) with different model routers (model specific) is not enough.

 

[chA]

The general recommendation is to run the AiMesh nodes on Asus firmware.

Thank you – I definitely was not aware of this and must have completely missed the recommendation! My previous router was the AX89X with an AIMesh AC68U node, so I haven't been able to run Merlin for a few years...

I would also recommend removing both nodes, after you flash them to the Asus firmware, factory reset the router and manually configure it, use the SmartConnect and leave the WIFI settings at default. Then add the nodes. I would add both nodes not connected to the Ethernet then move the First Floor node to its place and connect it to the Ethernet. Once the AiMesh nodes are connected add any guest WIFI networks. I would also set the 2.4 GHz bandwidth to 20 MHz but leave it on Auto Channel.

This is similar to how I initially setup these nodes, but was using merlin fw. I'll give it a shot on stock fw however!

- unsupported firmware
- run stock Asuswrt on nodes

- avoid Smart Connect
- use fixed channels only

Thanks! Will flash to stock fw first thing tomorrow! I have typically avoided Smart Connect in my daily operation (have experienced issues with previous Asus routers where a much slower band would consistently be selected – maybe this has been improved in the intervening time – or cheap IoT devices would constantly drop and reconnect), and use only fixed channels with the least local surrounding network interference.

FYI, the BE7200U is basically just a rebadged BE88U. I've not found many details as to why this same hardware has two different models, but my guess is that it has something to do with retail distribution and potentially so a retailer such as Best Buy doesn't have to price match an online competitor if the margin is considerably less on this model. Loading the BE88U fw onto the BE7200U does not present any issues or warnings, though I did see the note that the BE7200U is not tested against. Regardless, since the recommendation is to just use stock fw on the satellites, that shouldn't be an issue going forward.

Your router doesn't even have the same initial setup as RT-BE96U. After 37xxx firmware there is a new Network menu and Smart Connect setup is different.

Could you please explain what you mean by these statements? Sorry if I'm not connecting the dots regarding the initial setup comment – or maybe this wasn't intended for me?

 

[chA]

Thanks for the suggestions. I loaded the latest stock fw (3.0.0.6_102_38152) onto the 10GbE backhauled node and the 2.4GHz radios immediately became visible. I need to do the full reset now, but this is a promising start!

 

[bbunge]

Thanks for the suggestions. I loaded the latest stock fw (3.0.0.6_102_38152) onto the 10GbE backhauled node and the 2.4GHz radios immediately became visible. I need to do the full reset now, but this is a promising start!

Just remove the nodes from the mesh and re add them. That does a reset.

 

[chA]

Just remove the nodes from the mesh and re add them. That does a reset.

I did exactly that. Everything's back up and running now and looking good. Performance is where I was hoping it would be (finally) when I decided to upgrade to this hardware earlier this year.

Thanks again for everyone's suggestions!