public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Vivek Das Mohapatra <vivek@collabora.com>, iwd@lists.linux.dev
Subject: Re: Interop problem with Quantum Fiber WiFi7 pods (duplicate RSNXE IE)
Date: Wed, 2 Oct 2024 13:14:22 -0500	[thread overview]
Message-ID: <f234b143-63f6-4184-b97a-bfaa082d8cf6@gmail.com> (raw)
In-Reply-To: <26febdbb-1184-46be-989b-45aace86f104@collabora.com>

Hi Vivek,

On 10/2/24 12:08 PM, Vivek Das Mohapatra wrote:
> Hi - we've had reports of an incompatibility between network manager and
> the wifi7 hardware mentioned when using iwd as the backend.
> 
>  From what we've been able to tell:
> 
> validate_mgmt_ies() fails
> cause: disallowed duplicate IEs in the AssocResponse frame
> 
> We appear to have two dupes:
> 
> 221 - IE_TYPE_VENDOR_SPECIFIC - allowed
> 244 - IE_TYPE_RSNX - not allowed as a dup.
> 
> We checked IEEE 80211-2020.pdf couldn't find specific details about IEs
> that can be duplicated vs the ones that can’t.
> [ Sections 9.4.2.1 and 9.4.2.241 ]

Refer to section 9.3.3.1:
"The frame body consists of fields and elements as defined for each management 
frame subtype. All fields and elements are mandatory unless stated otherwise. 
Fields and elements appear in the specified, relative order, skipping fields or 
elements that are not present. STAs that encounter an element ID they do not 
recognize in the frame body of a received Management frame ignore that element 
and continue to parse the remainder of the management frame body (if any) for 
additional elements with recognizable element IDs."

IEs that allow duplication are explicitly called out:
"Vendor Specific
One or more Vendor Specific elements are optionally present. These elements 
follow all other elements."

Why are the elements duplicated?  Are they the same or different?  If different, 
which one would iwd use?

> 
> We've tried various devices and software combinations (linux and non)
> and it seems to be an interop problem with iwd specifically - we think adding 
> IE_TYPE_RSNX to the allowed dups list in validate_mgmt_ies should
> do the trick.

How about fixing the firmware?

Regards,
-Denis

  parent reply	other threads:[~2024-10-02 18:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 17:08 Interop problem with Quantum Fiber WiFi7 pods (duplicate RSNXE IE) Vivek Das Mohapatra
2024-10-02 17:40 ` James Prestwood
2024-10-02 18:14 ` Denis Kenzior [this message]
2024-10-02 21:41   ` Vivek Das Mohapatra
2024-10-02 21:55     ` Vivek Das Mohapatra
2024-10-03 12:17       ` James Prestwood
2024-10-04  2:58         ` Denis Kenzior
2024-10-04 11:45           ` Vivek Das Mohapatra
2024-10-05  2:19             ` RFC: Be more lenient about duplicate IEs with identical payloads Vivek Das Mohapatra
2024-10-05  2:19               ` [PATCH 1/2] unit: add a test for harmless IE clones Vivek Das Mohapatra
2024-10-07 18:26                 ` Denis Kenzior
2024-10-05  2:19               ` [PATCH 2/2] mpdu: tolerate technically illegal but harmless cloned IEs Vivek Das Mohapatra
2024-10-07 18:27                 ` Denis Kenzior
2024-10-07 18:29                   ` Vivek Das Mohapatra
     [not found] <e6936d40-0667-4128-a342-bd65dd553230@collabora.com>
2024-10-03 12:49 ` Interop problem with Quantum Fiber WiFi7 pods (duplicate RSNXE IE) Vivek Das Mohapatra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f234b143-63f6-4184-b97a-bfaa082d8cf6@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=vivek@collabora.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox