Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, yi.zhu@intel.com,
	linux-wireless@vger.kernel.org,
	"Ron Rindjunsky" <ron.rindjunsky@intel.com>
Subject: Re: [PATCH 2/2 V2] mac80211: add direct probe before association
Date: Sun, 7 Sep 2008 03:21:41 +0300	[thread overview]
Message-ID: <1ba2fa240809061721k2082d038j63c272f5b29a66c6@mail.gmail.com> (raw)
In-Reply-To: <1220744663.21016.28.camel@johannes.berg>

On Sun, Sep 7, 2008 at 2:44 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
> Hi,
>
> I was just pondering rewriting parts of the state machine (and you've
> already seen the other cleanups I did today) and found this:
>
>> +     /* Direct probe is sent to broadcast address as some APs
>> +      * will not answer to direct packet in unassociated state.
>> +      */
>> +     ieee80211_send_probe_req(dev, NULL,
>> +                              ifsta->ssid, ifsta->ssid_len);
>
>> +     /* direct probe may be part of the association flow */
>> +     if (test_and_clear_bit(IEEE80211_STA_REQ_DIRECT_PROBE,
>> +                                                     &ifsta->request)) {
>> +             printk(KERN_DEBUG "%s direct probe responded\n", dev->name);
>> +             ieee80211_authenticate(dev, ifsta);
>
> Doesn't the latter code have to check that the sender is the correct
> one? First we broadcast the probe request, and then we may be getting
> one from a different AP but still clear our direct probe association
> flow step, no?

Yep, this is not covered. Don't remember why it wasn't straight
forward to implement...will look at it again after sunrise.

Thanks
Tomas

  reply	other threads:[~2008-09-07  0:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-09  0:02 [PATCH 2/2 V2] mac80211: add direct probe before association Tomas Winkler
2008-09-06 23:44 ` Johannes Berg
2008-09-07  0:21   ` Tomas Winkler [this message]
2008-09-07 13:49     ` Johannes Berg

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=1ba2fa240809061721k2082d038j63c272f5b29a66c6@mail.gmail.com \
    --to=tomasw@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=ron.rindjunsky@intel.com \
    --cc=yi.zhu@intel.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