From: Vivek Das Mohapatra <vivek@collabora.com>
To: Denis Kenzior <denkenz@gmail.com>, iwd@lists.linux.dev
Subject: Re: Interop problem with Quantum Fiber WiFi7 pods (duplicate RSNXE IE)
Date: Wed, 2 Oct 2024 22:55:48 +0100 [thread overview]
Message-ID: <c400002b-ce76-4cfa-b5f0-c51be00eb9cb@collabora.com> (raw)
In-Reply-To: <f8703c80-14fd-42b8-bf8a-d06919b0db6e@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
On 02/10/2024 22:41, Vivek Das Mohapatra wrote:
> On 02/10/2024 19:14, Denis Kenzior wrote:
>>
>> Why are the elements duplicated? Are they the same or different? If
>> different, which one would iwd use?
OTA capture:
I've linked 1 file to this email:
* 0926_qfiber.tar.xz
Size: 5.2 MB
Link:
https://www.dropbox.com/scl/fi/i573yehaenpvkgy29smwb/0926_qfiber.tar.xz?rlkey=sxhhiwhmqppyic5wsc446h88r&dl=0
[-- Attachment #2: 0926_qfiber.tar.xz.html --]
[-- Type: text/html, Size: 3413 bytes --]
next prev parent reply other threads:[~2024-10-02 21:55 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
2024-10-02 21:41 ` Vivek Das Mohapatra
2024-10-02 21:55 ` Vivek Das Mohapatra [this message]
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=c400002b-ce76-4cfa-b5f0-c51be00eb9cb@collabora.com \
--to=vivek@collabora.com \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.