Quick Answer: Wi-Fi 7 packet loss in MLO (Multi-Link Operation) environments most commonly stems from misconfigured band steering, incompatible driver stacks, or incorrect aggregation policies between 2.4 GHz, 5 GHz, and 6 GHz links. The fix usually requires firmware alignment across AP and client, explicit MLO group configuration, and disabling legacy fallback modes that silently degrade throughput.
If you've upgraded to Wi-Fi 7 hardware and you're still watching ping spikes or jitter graphs, check out our guide on how to stop Wi-Fi 7 latency spikes to ensure a stable connection. The problem is real, it's widespread, and it's almost never what the spec sheet prepared you for.
Wi-Fi 7, formally IEEE 802.11be, ships with the most ambitious architectural change in wireless history: Multi-Link Operation, or MLO. The idea is elegant. Instead of hopping between bands like every previous Wi-Fi generation, a single logical connection simultaneously uses multiple physical radio links — say, 6 GHz and 5 GHz — and aggregates, load-balances, or redundancy-switches between them in real time. On paper: lower latency, higher throughput, fewer drops. In practice: a system with three entirely separate radio paths, three separate MAC schedulers, cross-layer state machines that were designed in committee, and firmware that vendors were still writing when hardware shipped to reviewers.
The result is a very specific kind of operational pain, much like troubleshooting a gaming console stuck on a green screen. Packet loss in a Wi-Fi 7 MLO setup doesn't look like traditional wireless interference. It often looks like random loss, at irregular intervals, with excellent signal strength, on hardware that should theoretically be working fine. And if you go to any home networking forum right now — r/HomeNetworking, the SmallNetBuilder forums, the Asus router subreddit, various Discord servers for networking enthusiasts — you'll find threads that are six months old and still have no resolution, just people comparing firmware versions and muttering about vendor-specific MLO "compatibility matrices."
Why MLO Packet Loss Is Different From Classic Wi-Fi Interference
Before getting into the fix, you have to understand why this fails in ways that prior Wi-Fi generations didn't.
In Wi-Fi 5 and Wi-Fi 6/6E, packet loss was largely explainable by the usual suspects: channel congestion, co-channel interference, weak signal, bad AP placement, or driver bugs. The remediation playbook was well-understood, much like following a specialized guide to fix a Roborock S7 LiDAR obstruction or resolving complex hardware errors. MLO introduces a fundamentally different failure mode.
The Multi-Link Scheduler Problem and IEEE 802.11be State Synchronization
In an MLO connection, the access point and the client device maintain a shared state across multiple physical links. Each link has its own MAC (Medium Access Control) layer, its own EDCA (Enhanced Distributed Channel Access) queue, and its own retransmission logic. The magic of MLO is that these separate MAC layers are coordinated by a higher-level multi-link entity — the MLE — that decides which link to use for which packet, when to switch, and when to aggregate.
When this coordination works, it's genuinely impressive. Latency drops because the MLE can route time-sensitive traffic (like ACKs or gaming packets) over whatever link currently has the shortest queue, while bulk transfers use whichever link has more available bandwidth. Redundancy mode can even send identical copies over two links to ensure delivery.
When it breaks — and it breaks — the MLE's state machine gets out of sync between AP and client. This manifests as:
- Silent packet drops: Packets are transmitted on one link but the receiver's MLE is expecting them on a different link it thinks is active.
- Spurious retransmissions: The AP retransmits packets the client has already received because ACKs arrived on a different link than expected.
- Link oscillation: The MLE keeps switching the "active" link in a tight loop, causing micro-outages on every switch.
- Phantom association: The client reports full connectivity, the AP shows an active MLE session, but actual data flow has silently stopped.
This last one is especially nasty. Your ping works. DNS resolves. But your video stream buffers. Your file transfer stalls at 99%. A speed test shows 2 Mbps instead of 2 Gbps.
The Real Firmware Situation: What Vendors Actually Shipped
Let's be direct about something: most Wi-Fi 7 routers shipped in 2023 and early 2024 with MLO that was either incomplete, experimental, or simply broken in specific client combinations.
The Asus RT-BE96U, one of the first broadly available Wi-Fi 7 routers, shipped with firmware where MLO was listed as supported but only functioned correctly in a very narrow configuration. Users on the Asus ROG forum documented (thread: "BE96U MLO packet loss - ongoing investigation," started January 2024) that enabling MLO with certain Intel BE200 adapters caused random 30-second connectivity drops. The workaround — forcing the client to use only 6 GHz by disabling 2.4 GHz and 5 GHz radios on the AP — obviously defeated the entire purpose of MLO.
TP-Link's BE900 had a different problem. Its MLO implementation used a proprietary band aggregation mode that wasn't fully compliant with the 802.11be spec as ratified, meaning it worked well with other TP-Link clients but exhibited severe packet loss with Qualcomm-based clients using the FastConnect 7800 chipset. TP-Link's response on their community forums was, essentially, "update to the latest firmware" — which fixed one bug and introduced another.
The Intel BE200 adapter itself went through multiple driver iterations where MLO behavior changed significantly. Windows users discovered that driver versions 23.x and 24.x handled MLO teardown and re-association differently, and that a downgrade to a specific minor version (a detail circulated in a GitHub issue on the linux-wireless repository) was necessary to prevent continuous re-negotiation under load.
On Linux, the situation was — and remains — worse. The BE200's MLO support in the kernel requires kernel 6.7+ and specific firmware blobs from Intel's linux-firmware repository. As of mid-2024, there are open bugs in the iwlwifi driver tracker (specifically iwlwifi bug #3492 and related issues) documenting MLO state sync failures under load conditions that don't reproduce in isolation. The maintainers have acknowledged these are real, non-trivial bugs, not user configuration errors.
Step-by-Step MLO Configuration: What Actually Works
This guide assumes you have a Wi-Fi 7 access point and a Wi-Fi 7 client adapter. If either side is Wi-Fi 6E or older, MLO is not available — you'll get backward-compatible operation on a single band.
Step 1: Firmware and Driver Baseline — The Unglamorous Starting Point
Before touching MLO configuration, establish a known-good firmware baseline. This sounds obvious, but it's where most people skip steps.
For your router/AP:
- Download the firmware changelog, not just the latest version. Read it. MLO-specific bug fixes are usually buried under generic "improved stability" language, but sometimes explicitly mention MLO or 802.11be link management.
- Check your vendor's community forum for the specific firmware version that other users report as most stable for your hardware revision. The "latest" firmware is not always the most stable for MLO — this is a repeated finding across multiple vendors.
- After flashing, do a full factory reset and reconfigure from scratch. Upgrading firmware while keeping saved settings has caused persistent MLO misconfiguration states that survive reboots.
For your client adapter (Intel BE200, Qualcomm FastConnect 7800, MediaTek Filogic):
- Windows: Go to Device Manager, check the driver version, and cross-reference against Intel's or Qualcomm's release notes for MLO-specific fixes. Don't use Windows Update's driver — get it directly from the chipset manufacturer's support page.
- Linux: You need kernel 6.7 minimum for any meaningful BE200 MLO support. Check
dmesg | grep iwlwififor firmware loading messages. If you see firmware version below 89.x for BE200, your MLO support will be limited. - macOS: Apple's proprietary wireless stack doesn't expose MLO controls and handles band selection internally. If you're debugging packet loss on a Mac connected to a Wi-Fi 7 AP, you have limited visibility into which links are active.
Step 2: Understanding Your MLO Configuration Options
Different vendors expose MLO configuration at different depths. Here's what you're actually controlling:
MLO Mode Selection: Most Wi-Fi 7 routers offer at minimum:
- MLO Disabled: Router operates as a standard multi-band AP. Clients connect to one band at a time. Use this to establish a baseline.
- MLO Enhanced Multi-Link (eMLSR): Only one link is active at a time, but transitions are faster than traditional band steering. Lower complexity, lower packet loss risk.
- MLO Simultaneous Transmit/Receive (STR): Multiple links truly active simultaneously. Highest performance, highest complexity, highest probability of firmware-related packet loss.
- MLO NSTR (Non-Simultaneous Transmit and Receive): Intermediate mode — useful for hardware that can't truly do simultaneous TX on multiple bands.
The practical recommendation for a system experiencing packet loss: Start with eMLSR. It gives you most of the latency benefit of MLO with dramatically reduced state synchronization complexity. If eMLSR is stable for 48 hours under real load, then test STR.
Step 3: Channel and Width Configuration for Stable MLO Stacking
MLO stacking — using multiple links in aggregate — is highly sensitive to the channel configuration of each link. Here's what to set:
6 GHz Band (the primary MLO workhorse):
Channel Width: 320 MHz (if space permits) or 160 MHz
Channel: Use static channel assignment. Auto selection during a session can
cause MLO link drops. Choose an upper UNII-5 channel away from
DFS-prone ranges in your region.
BSS Color: Enable. Reduces spatial reuse conflicts when multiple 6 GHz
networks are nearby.
5 GHz Band (secondary MLO link):
Channel Width: 80 MHz recommended, 160 MHz if you have a clean RF
environment (unlikely in dense urban settings)
DFS Channels: Avoid completely for MLO. A DFS radar detection event will
force a channel switch mid-session, which can desynchronize
the MLO state machine catastrophically.
Channel: Static assignment. W52/W53 channels in regions that require
indoor-only operation.
2.4 GHz Band:
For MLO: Generally exclude from MLO group. The 2.4 GHz band's
lower throughput and higher congestion makes it a net negative
participant in most MLO configurations.
Keep it: Active as a fallback for legacy devices, but not in your
primary MLO group.
Step 4: The MLO Group Configuration — Where Most Guides Stop Too Early
Most setup guides tell you to "enable MLO" and call it done. The real work is in defining which bands participate in the MLO group and how the MLE arbitrates between them.
In vendor UIs that expose this (Asus's newer firmware, some OpenWrt BE builds), you'll see an MLO group or "Multi-Link Group" configuration where you explicitly assign radios to an MLO logical interface. The key settings:
Primary Link Designation: Assign your 6 GHz radio as the primary MLO link. This is the link the MLE defaults to for new sessions and high-priority traffic. If left to auto-assignment, some firmware versions will default to 5 GHz as primary (a legacy behavior from band-steering logic) which degrades MLO performance.
Traffic Classification (TID-to-Link Mapping): Wi-Fi 7 introduced TID-to-Link Mapping — the ability to assign specific Traffic IDs (which correspond to QoS classes) to specific links. This is powerful and underutilized:
TID 0-1 (Background): Map to 5 GHz — bulk transfers, backups
TID 2-3 (Best Effort): Split across 6 GHz and 5 GHz
TID 4-5 (Video): Map to 6 GHz — streaming, video calls
TID 6-7 (Voice/High Priority): Map exclusively to 6 GHz — gaming, VoIP
Not all vendor firmware exposes TID mapping directly. If yours doesn't, you're at the mercy of the MLE's default policy, which in many implementations is just "send everything on the link with the most current throughput" — a policy that's fine for bulk transfers but terrible for latency-sensitive traffic.
Step 5: Disabling Features That Silently Break MLO
Several features that are "enabled by default" on modern routers actively interfere with MLO stability:
Band Steering / Smart Connect: Turn this off. Band steering is a pre-MLO technology that actively moves clients between bands. In a router running MLO, band steering and the MLE's link management are competing systems. Some firmware versions handle this gracefully; most don't. The symptom is rapid disconnections and reconnections as both systems try to "optimize" the client's connection simultaneously.
Airtime Fairness: In MLO mode, airtime fairness algorithms designed for single-link operation can interfere with the MLE's link selection logic. Disable it on MLO-capable SSIDs.
Roaming Assist / 802.11k/v/r: These are important in mesh networks but create complications in single-AP MLO deployments. 802.11r fast transition, in particular, has known interaction bugs with MLO association in several firmware versions. Unless you specifically need fast roaming, disable it on your Wi-Fi 7 SSID.
MU-MIMO + MLO interaction: Some routers show decreased MLO stability when MU-MIMO is active with many simultaneous clients. If you're debugging a dense environment, try disabling MU-MIMO as a diagnostic step.
Real Field Reports: What People Are Actually Experiencing
The gap between MLO's specification and its current implementation reality is significant. Here's what the operational evidence actually shows.
A user running a home lab documented on SmallNetBuilder forums (late 2023) that their TP-Link BE900 showed packet loss exclusively during periods when both 6 GHz and 5 GHz links were simultaneously saturated — the exact condition MLO is supposed to handle gracefully. Investigation showed the router's internal switching fabric was bottlenecking the backhaul aggregation, not the wireless links themselves. The fix wasn't a wireless configuration change — it was recognizing that the hardware's internal bus was a constraint that no RF setting could address.
In another frequently referenced case on Reddit's r/HomeNetworking, a user with an Intel BE200 adapter reported that MLO worked perfectly during iperf3 tests but degraded severely during actual browsing and streaming. Packet capture analysis showed the client was constantly re-negotiating TID-to-Link mappings — a behavior suggesting the driver's MLE was reacting to traffic pattern changes by issuing mapping renegotiation frames, which briefly suspended data flow each time. The fix: locking TID mapping to static assignments in the driver's advanced parameters, a setting buried in Device Manager's adapter properties under "Wi-Fi 7 Link Management."
A developer working on OpenWrt support for a Wi-Fi 7 chipset posted in the OpenWrt forum (thread: "mt7996 MLO support status," 2024) that the MediaTek Filogic 880 chipset's MLO implementation in current open-source drivers passes the basic conformance tests but fails under specific TID mapping changes triggered by QoS reclassification events — a bug that doesn't show up in standard throughput tests but becomes obvious in gaming or video conferencing workloads.
Counter-Criticism and the Debate Around MLO Complexity
There's a real argument — made by serious networking engineers, not just skeptics — that MLO's complexity was premature standardization.
The criticism goes like this: 802.11be's MLO was designed primarily for enterprise and high-density environments where link aggregation provides meaningful capacity gains. In a typical home, with one or two simultaneous high-bandwidth users, the practical benefit of simultaneous multi-link operation over well-implemented single-band 6 G