If you added a Wi-Fi 6E router as an AiMesh node under a Wi-Fi 7 primary router and the 6 GHz network disappeared near that node, this is documented ASUS behavior rather than a hardware fault. ASUS states that when MLO (Multi-Link Operation) is enabled on an AiMesh primary router, a node that does not support MLO will not broadcast 6 GHz Wi-Fi.
ASUS’s documented remedy is to disable MLO on the primary router, under Wireless → MLO → Enable MLO, which ships enabled by default. For most mixed-generation homes that is the right trade: MLO benefits only the clients that support it, while 6 GHz is usable by every 6 GHz-capable device in the house. Replacing the node is the better answer in a narrower set of cases, covered below.
Quick Answer: A Non-MLO AiMesh Node Will Not Broadcast 6 GHz
ASUS documents this behavior directly. If MLO is enabled on the AiMesh primary router, an AiMesh node that does not support MLO will not broadcast 6 GHz Wi-Fi. A Wi-Fi 7 node that supports MLO and includes a 6 GHz radio can broadcast it. The documented remedy is disabling MLO on the primary router.
ASUS publishes the two combinations as a support table:
| AiMesh scenario | AiMesh primary router | AiMesh node | Node broadcasts 6 GHz? |
|---|---|---|---|
| Scenario 1 | Wi-Fi 7 router (MLO enabled) | MLO-capable Wi-Fi 7 router with a 6 GHz radio | Supported |
| Scenario 2 | Wi-Fi 7 router (MLO enabled) | Wi-Fi 6E router | Not supported |
Two distinctions prevent most misdiagnoses here. Wi-Fi 6E support and MLO support are not the same thing: a Wi-Fi 6E node has a 6 GHz radio but no MLO, and it is the missing MLO that triggers this behavior. This 6 GHz fronthaul condition is also separate from ASUS’s MLO backhaul limits, which are covered later.
Quick Fix Checklist
Run these six checks in order before changing any setting. The order matters: it separates a region or client limitation from the MLO condition, so you do not disable a Wi-Fi 7 feature that was never the cause of your missing 6 GHz network.
- Confirm whether 6 GHz is missing everywhere in the house, or only near one node.
- Confirm that 6 GHz is available in your region and is broadcasting from the primary router.
- Check whether the node supports MLO, or is a Wi-Fi 6E or older model.
- Check whether 6 GHz is currently assigned as the AiMesh wireless backhaul band.
- Disable MLO on the primary router under Wireless → MLO → Enable MLO.
- Retest with a client device that is confirmed to support 6 GHz.
Identify Where 6 GHz Is Missing: Main Router, Node, or Client Device
Missing 6 GHz has three different locations, and they have different causes. Check whether the band is absent everywhere, absent only near one node, or absent only on one device. Each answer points to a different section, and testing in the wrong place wastes the most time.
Walk to each unit with the same phone or laptop and note where the 6 GHz SSID appears. Match what you see against this table.
| What you observe | Most likely cause | Where to go next |
|---|---|---|
| 6 GHz missing everywhere, including next to the primary router | Region restriction, 6 GHz not enabled, or the test client cannot see 6 GHz | Router, node, and firmware checks below |
| 6 GHz visible at the primary router, missing near one specific node | MLO is enabled on the primary router and that node does not support MLO | The step-by-step fix below |
| 6 GHz visible near every unit, but one device never sees it | That client device does not support the 6 GHz band | Router, node, and firmware checks below |
| 6 GHz is visible, but the connection drops or falls back to another band | Client-side behavior or another MLO stability issue, rather than a broadcast condition | Our MLO disconnection guide, linked below |
That last row is a different problem. If the 6 GHz network is visible but your Windows 11 PC keeps dropping its MLO connection, investigate the client and the MLO configuration separately: Wi-Fi 7 MLO Disconnects Fix: Intel BE200 and Router Settings for Windows 11.
Check the Primary Router, Node Generation, MLO Support, and Firmware
Four attributes decide whether a node can serve 6 GHz: the primary router’s generation, the node’s generation, whether the node supports MLO, and the firmware on both units. Wi-Fi 6E support and MLO support are not the same thing, and that distinction is where most diagnoses go wrong.
| What to check | Where to check it | Why it matters |
|---|---|---|
| Primary router generation | Web GUI network map, or the model label on the unit | The documented condition applies to a Wi-Fi 7 primary router with MLO enabled |
| Node generation and MLO support | The node’s official product specification page | A Wi-Fi 6E node has 6 GHz but no MLO, which is what triggers the condition |
| Firmware on both units | Web GUI firmware page, or the ASUS Download Center | ASUS publishes minimum firmware versions for MLO support |
| Regional 6 GHz availability | Official product specification page for your region | ASUS notes that 6 GHz applies only where the band is supported in your region |
| Which unit is set as primary | Web GUI AiMesh topology view | ASUS recommends setting the highest-specification unit as the main router |
ASUS describes MLO support as covering its Wi-Fi 7 series and publishes minimum firmware versions for named models — the GT-BE96, RT-BE96U, GT-BE98, and GT-BE98 Pro — in its official MLO support article. ASUS also directs readers to the product specification page, so confirm your exact model there rather than relying on the published list alone. Its separate Wi-Fi 7 compatibility guide covers mixed AiMesh systems, 6 GHz client support, and legacy-device encryption compatibility.
What Users Report in Mixed-Generation AiMesh Setups
According to multiple community reports, some users have been unable to reach 6 GHz through an AiMesh node in Wi-Fi 6E-only setups that predate MLO entirely. This does not appear to affect every configuration, but it matters here: it means disabling MLO will not always restore 6 GHz on a node.
Two patterns show up repeatedly in ASUS community threads, and both are worth checking before you conclude that MLO is the only variable in play:
- 6 GHz unreachable through a node in Wi-Fi 6E-era systems. Multiple posters across more than one thread describe Wi-Fi 6E primary routers with Wi-Fi 6E nodes, wired backhaul included, in which 6 GHz clients associate with the primary router but not the downstream node. These reports predate MLO, so node-side 6 GHz behavior has more than one possible cause.
- 6 GHz assigned as the wireless backhaul band. In at least one reported configuration, 6 GHz was set as the dedicated wireless backhaul and clients were not connecting to nodes. ASUS exposes a backhaul band setting in the Web GUI, so confirm which band is carrying backhaul traffic. Treat this as a check, not a confirmed cause.
None of this overrides the documented MLO condition. It is included for one reason: if you disable MLO and 6 GHz still does not appear at the node, you are most likely looking at a separate issue rather than a failed fix.
Disable MLO, Adjust the AiMesh Configuration, or Retest the 6 GHz Network
The fix takes five steps. You disable MLO on the primary router, confirm the AiMesh backhaul band, let every unit restart, and then retest the 6 GHz SSID standing next to the node rather than next to the primary router, using a client that supports 6 GHz.
- Sign in to the primary router’s Web GUI by opening its LAN IP address or the ASUS router URL in a browser. The settings changed in this procedure are applied on the primary router rather than on the node.
- Open Wireless → MLO and turn off Enable MLO, which is enabled by default on supported Wi-Fi 7 models. MLO fronthaul can also be toggled under Network → Main network profile → Advanced Settings → Multi-Link Operation (MLO), or via MLO Fronthaul for Clients on that profile’s General tab.
- Apply the change and allow every unit to re-establish its links before evaluating the result.
- Check the backhaul band under Wireless → MLO → Backhaul Band. ASUS states that changing it restarts every router in the AiMesh system, so do this when a brief outage is acceptable.
- Retest at the node. Stand next to it with a client confirmed to support 6 GHz and check the available-networks list. Testing where the client can still hear the primary router tells you nothing.
ASUS’s AiMesh Web GUI setup guide covers the router login, firmware update, node preparation, and topology screens if you want to confirm the layout first.
Verification and Edge Cases
Disabling MLO is not free. ASUS states that enabling MLO also enables the AiMesh MLO backhaul function, so turning MLO off removes that backhaul option as well. Three further conditions decide whether 6 GHz returns: region availability, client support, and the encryption mode in use.
- You lose MLO backhaul along with MLO fronthaul. The two are tied together, so a system using an MLO backhaul link falls back to a single-band wireless backhaul or a wired one. If your nodes are wired, this costs almost nothing. If they are wireless, weigh it against the 6 GHz coverage you gain at the node.
- MLO backhaul has its own separate limits. ASUS states that with multiple Wi-Fi 7 nodes, only the first node can use MLO backhaul, and that MLO backhaul supports the same model only, attributing the first-node limit to known chipset constraints. These are backhaul conditions, not the 6 GHz fronthaul condition covered earlier.
- Region availability comes first. ASUS notes that 6 GHz applies where the band is supported in your region. If it is not permitted or not enabled where you are, no MLO setting will make the SSID appear.
- Encryption can block older clients. ASUS describes Wi-Fi 7 networks using AES with GCMP-256 and notes that some legacy devices are not compatible, recommending an IoT network for those. That is a separate compatibility path, not a 6 GHz broadcast problem.
Confirm the manufacturer’s official specifications for your exact model and region before changing hardware or wireless settings, and check any rules that apply to your network. No change described here can guarantee coverage, throughput, or uninterrupted operation in a given home.
When to Keep the Legacy Node and When to Replace It
Keep the legacy node and disable MLO. In most mixed-generation homes, MLO benefits only the handful of clients that support it, while 6 GHz serves every 6 GHz-capable device you own. Replace the node only when MLO-capable clients are concentrated in that node’s coverage area.
The reasoning is a straightforward count of devices. MLO is a Wi-Fi 7 client feature, and ASUS states that the mode in use depends on what the client supports in the first place. The 6 GHz band, by contrast, is available to every Wi-Fi 6E and Wi-Fi 7 device in the house. Trading a band many devices can use for a feature few of them can use is the wrong trade in most homes.
AD: This section contains affiliate links. See the disclosure at the top of this article.
✅ Keep the node and disable MLO if:
- Most of your devices are Wi-Fi 6E or Wi-Fi 6, with few or no MLO-capable clients.
- Your nodes are connected by Ethernet backhaul, so losing MLO backhaul costs you little.
- The area served by that node is where you actually need 6 GHz coverage.
⚠️ Consider replacing the node if:
- Your MLO-capable clients are concentrated in that node’s coverage area, so MLO fronthaul there is worth keeping.
- You use a wireless backhaul and want MLO backhaul between the primary router and the first node, which ASUS documents as requiring the same model.
- You are planning a wider Wi-Fi 7 refresh anyway and the legacy node is the oldest unit in the system.
One verified example is the ASUS RT-BE92U Wi-Fi 7 AiMesh router on Amazon.com. It supports 6 GHz, MLO, and AiMesh, but it is not a universal match: confirm the exact model of your primary router before buying, especially if you want to use MLO backhaul, which ASUS documents as a same-model feature.
If replacing the mixed-generation AiMesh setup makes more sense than disabling MLO on a system you are already planning to retire, our comparison of current Wi-Fi 7 mesh systems covers the options by home size and budget: Best Wi-Fi 7 Mesh Routers in 2026: Top Picks for Every Home and Budget.
Frequently Asked Questions
These three questions come up most often once the MLO condition is understood. Each answer stays inside what ASUS publishes in its own official support documentation, and none of them depends on the community reports discussed earlier in this article, so they apply to any supported model.
Does disabling MLO also disable the AiMesh MLO backhaul?
Yes. ASUS states that when the MLO function is enabled, the AiMesh MLO backhaul function is enabled with it. Turning MLO off on the Wireless MLO page therefore removes MLO backhaul as well, and the AiMesh system falls back to another wireless backhaul band or to a wired link.
Will a Wi-Fi 7 AiMesh node broadcast 6 GHz when MLO is enabled?
ASUS’s published scenario table lists a Wi-Fi 7 primary router with MLO enabled and a Wi-Fi 7 node as supported for 6 GHz broadcast. In practice, confirm that the node supports MLO and has a 6 GHz radio, because some Wi-Fi 7 routers are dual-band models without 6 GHz.
Do I need to disable Wi-Fi 7 mode to fix this?
No. MLO and Wi-Fi 7 mode are separate settings. Wi-Fi 7 mode, found on the main network Wi-Fi profile, exists mainly for legacy clients that cannot associate with a Wi-Fi 7 network. The 6 GHz broadcast condition on a node is governed by MLO, not by that toggle.
How We Researched
This article is based on ASUS official support documentation, which we opened and read directly, together with community reports where the same pattern appeared across more than one thread. We have not conducted hands-on lab testing. Every compatibility claim above is attributed either to official documentation or to clearly identified community reports.
The official sources are ASUS’s support articles on MLO and on Wi-Fi 7 compatibility with existing ASUS routers, which supplied the scenario table, the settings paths, the backhaul conditions, and the encryption and regional caveats. The community material comes from ASUS ROG Forum threads in which several separate posters described 6 GHz being unreachable through an AiMesh node. Single-post reports were excluded rather than summarized.
Conclusion
Work in this order: confirm where 6 GHz is missing, confirm whether the node supports MLO at all, then disable MLO on the primary router if the node does not. That sequence resolves the documented case and tells you quickly when you are looking at something else entirely.
The one decision worth pausing on is whether to keep the legacy node. For most mixed-generation homes the answer is yes: disable MLO, keep 6 GHz coverage at the node, and revisit it when you own enough MLO-capable clients to make the feature worth the band. If those clients already cluster around that node, replacing it is the cleaner fix.
