All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: Optional IEs into scan request
Date: Wed, 25 Mar 2009 18:32:25 +0200	[thread overview]
Message-ID: <20090325163225.GA28509@jm.kir.nu> (raw)
In-Reply-To: <1ba2fa240903250838qab8acb1v3abffe06c5384d13@mail.gmail.com>

On Wed, Mar 25, 2009 at 05:38:11PM +0200, Tomas Winkler wrote:

> After reading the WPS spec again and specifically the section 10.3
> that talks about PBC, it looks like for PBC you will need to have the
> WPS IE in the Probe request for it to function correctly. So it
> doesn't look optional to mee
> 
> The WPS IE in the Probe Request will indicate that the device is in
> PBC mode. The WPS IE is also used for Registrars to see if multiple
> requests were received within the PBC Monitor time.

It is not ideal to work without including the WPS IE in Probe Request,
but the Registrar should be able to do similar detection for session
overlap using M1. If you want something better, all you need to do is to
move from using WEXT to nl80211.. ;-)

The spec is somewhat unclear on this, but there are couple of places
which indicate that the WPS IE may not always be included in Probe
Request (e.g., APs must not reject WPS based on missing WPS IE in Probe
Request).

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2009-03-25 16:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 10:53 [PATCH] nl80211: Optional IEs into scan request Jouni Malinen
2009-02-13 11:00 ` Johannes Berg
2009-02-13 11:15   ` Jouni Malinen
2009-02-15 13:09     ` Tomas Winkler
2009-02-15 15:44       ` Jouni Malinen
2009-02-15 20:40         ` Tomas Winkler
2009-03-25 15:38           ` Tomas Winkler
2009-03-25 16:32             ` Jouni Malinen [this message]
2009-02-15 16:12       ` Johannes Berg
2009-02-15 20:45         ` Tomas Winkler

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=20090325163225.GA28509@jm.kir.nu \
    --to=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomasw@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 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.