[PATCH] AP MLD: Break the mutual ACS deferral between partner links
Jouni Malinen
j at w1.fi
Sun Nov 15 13:11:26 PST 2026
On Tue, Sep 22, 2026 at 06:27:12PM +0200, Nilanka de Silva wrote:
> hostapd_driver_scan() refuses to start an ACS scan while any ML partner
> link's interface is in HAPD_IFACE_ACS state. When two links of the same
> MLD are configured with channel=0 they enter that state at the same
> time, each sees the other "in ACS", and both return -EBUSY. acs.c retries
> every ACS_SCAN_RETRY_INTERVAL until ACS_SCAN_RETRY_MAX_COUNT, then one
> link fails ("ACS: Failed to request initial scan (all re-attempts
> failed)") and is disabled, leaving a single-link MLD. Nothing ever
> breaks the tie, because the state check does not distinguish a partner
> that is scanning from a partner that is also waiting to scan.
>
> Observed on MT7996 (one wiphy, 5 GHz + 6 GHz AP MLD links): both links
> log "ACS in progress in a partner link - try to scan later" and "Failed
> to request acs scan ret=-16 (Resource busy)" in lock step for the whole
> retry window. The behaviour is the same under different regulatory
> domains (NL, SA); a separate non-MLD BSS on the same wiphy completes ACS
> normally.
>
> Only defer while the partner really has a scan in flight (scan_cb set).
> When both links are still waiting to start, let the link with the lowest
> mld_link_id go first so the two ACS runs serialise.
>
> Tested on MT7996 with both MLD links on ACS: the second link logs
> "Partner link 1 starts ACS first - try to scan later", the first link
> completes ACS, then the second runs its own; both links are up about
> 50 s after start, on a reload and on a cold boot.
Thanks, applied.
--
Jouni Malinen PGP id EFC895FA
More information about the Hostap
mailing list