[PATCH 8/9] tests: test MLO rejection for incorrectly configured MLD APs
Benjamin Berg
benjamin at sipsolutions.net
Tue Sep 30 06:51:03 PDT 2025
On Tue, 2025-09-30 at 12:08 +0300, Jouni Malinen wrote:
> On Wed, Jun 18, 2025 at 02:35:30PM +0200, Benjamin Berg wrote:
> > Add a test that injects various problematic ML elements and verify that
> > MLO is disabled in that case.
>
> Does this need something special to be done to work correctly or could
> some other commit in hostap.git have made an impact here? I'm seeing
> eht_mld_invalid_ml_elem fail in the first test ("2nd link misses ML
> elem") with
>
> Exception: Unexpected valid links (0x0003 != 0x0001)
I just rebased these on top of cfc59f26dfb9 ("IKEv2: Add support for
null encryption") and the test is working fine for me. I also updated
my Linux tree to current wireless-next/main.
Now, the test works by replacing the scan results for the second AP
with something invalid. So it would seem that either that injection
mechanism failed or there are scan results afterwards and BSS selection
is seeing the kernel data again.
Is the above base commit the same that you tested against?
Benjamin
More information about the Hostap
mailing list