Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>,
	Mauro Condarelli <mc5686@mclink.it>,
	iwd@lists.linux.dev
Subject: Re: Setup help request
Date: Tue, 2 Jan 2024 11:10:15 -0600	[thread overview]
Message-ID: <dadf5399-4c77-4b99-b2a4-3ed2f18c7bde@gmail.com> (raw)
In-Reply-To: <bf00447d-9817-4bd9-ba67-149356d6ecd6@gmail.com>

Hi James,

> 
> I'll need to look more at the spec to determine if this is "illegal" (for lack 
> of a better term) to duplicate these IEs. There are some IEs that we allow 
> duplicates of (which you can see in that patch). With a simple search I cant 
> find anything in the spec that disallows duplicates specifically, but we have 
> this comment in IWD:
> 
> "Tag found, make sure no duplicates present unless allowed"
> 
> Denis, any idea where that comes from off the top of your head?

802.11 allows some IEs to be duplicated.  For example, see verbiage in 
802.11-2020 Section 9.3.2 dealing with Beacons:

"One or more Multiple BSSID elements are present if"...
"One or more Emergency Alert Identifier elements are present if"...
"One or more Emergency Alert Identifier elements are present if"...
"One or more Vendor Specific elements are optionally present. These..."

Regards,
-Denis

  reply	other threads:[~2024-01-02 17:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 19:26 Setup help request Mauro Condarelli
2024-01-01 23:03 ` James Prestwood
2024-01-02  0:34   ` Mauro Condarelli
2024-01-02 13:01     ` James Prestwood
2024-01-02 14:07       ` Mauro Condarelli
2024-01-02 14:40         ` James Prestwood
2024-01-02 17:10           ` Denis Kenzior [this message]
2024-01-02 15:11         ` Mauro Condarelli
2024-01-02 15:36           ` James Prestwood
2024-01-02 17:09             ` Mauro Condarelli
2024-01-02 17:30               ` James Prestwood
2024-01-02 17:45                 ` Mauro Condarelli
2024-01-02 19:52                   ` James Prestwood
2024-01-02 20:30                     ` Mauro Condarelli

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=dadf5399-4c77-4b99-b2a4-3ed2f18c7bde@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=mc5686@mclink.it \
    --cc=prestwoj@gmail.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