From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pavel Roskin <proski@gnu.org>, linux-wireless@vger.kernel.org
Subject: Re: nl80211 and wext interoperability
Date: Mon, 13 Jul 2009 13:55:24 -0400 [thread overview]
Message-ID: <1247507724.4369.13.camel@localhost.localdomain> (raw)
In-Reply-To: <1247161696.22527.1.camel@johannes.local>
On Thu, 2009-07-09 at 19:48 +0200, Johannes Berg wrote:
> On Thu, 2009-07-09 at 13:13 -0400, Pavel Roskin wrote:
>
> > I think using random data is a problem by itself. Are we exposing
> > random pieces of kernel memory in probe requests? That's bad.
>
> You misunderstood. wpa_supplicant _explicitly_ tells us it _wants_ to
> use that 32-byte random SSID. It's just like it telling us it wants to
> use the ssid "foobar" or "Pavel's House" or ... I don't see what we can
> do, other than actually take it seriously and at least attempt to
> connect to that network.
That was the idea, expect that this random BSSID/SSID combo will simply
fail to be found in a scan, and either the card driver will just keep
periodically scanning to find the AP until another request comes in, or
they will eventually just give up and idle. What it was meant to do was
to stop the card from trying to keep re-associating to a previous AP now
that the supplicant has terminated. See my just-posted mail a bit up in
this thread as to why. WEXT sucks.
Dan
next prev parent reply other threads:[~2009-07-13 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 11:43 nl80211 and wext interoperability Johannes Berg
2009-07-09 14:43 ` John W. Linville
2009-07-09 17:13 ` Pavel Roskin
2009-07-09 17:48 ` Johannes Berg
2009-07-13 17:55 ` Dan Williams [this message]
2009-07-09 17:53 ` Luis R. Rodriguez
2009-07-09 18:15 ` Johannes Berg
2009-07-13 17:53 ` Dan Williams
2009-07-13 17:54 ` Johannes Berg
2009-07-13 19:10 ` Dan Williams
2009-07-13 19:14 ` Johannes Berg
2009-07-13 20:52 ` Dan Williams
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=1247507724.4369.13.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
/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;
as well as URLs for NNTP newsgroup(s).