From: Johannes Berg <johannes@sipsolutions.net>
To: Denis Kenzior <denkenz@gmail.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
Tim Kourt <tim.a.kourt@linux.intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] cfg80211: Fix support for flushing old scan results
Date: Tue, 22 May 2018 16:50:10 +0200 [thread overview]
Message-ID: <1527000610.6787.14.camel@sipsolutions.net> (raw)
In-Reply-To: <c8f3d9a7-b978-8af8-6594-d0ae66652956@gmail.com> (sfid-20180522_164839_367773_27F91548)
On Tue, 2018-05-22 at 09:48 -0500, Denis Kenzior wrote:
> Hi Arend,
>
> > > Are you saying the first result is from the Beacon and the other is from
> > > the Probe Response? Then why are the 'Information elements from Probe
> > > Response frame' the way they are?
> >
> > Nope. I am not saying that. I am saying that there are two probe
> > requests being sent. One with broadcast ssid, ie. ssid_len == 0, and
> > with ssid 'myssid'. But it is speculation without a sniffer capture.
>
> Ah I see what you mean now. No, we traced this down to hostapd itself
> and it was receiving a single Probe Request with the ssid set and
> replying to it per spec. So I'm pretty confident this scenario isn't
> what is happening. Let me try to get some actual packet captures...
Was "myssid" the real SSID, or did you hide that from us and it was
really 9 characters long in the original?
If it was really 9 characters long I could imagine that there's a
different bug with a beacon with all-zero-bytes having been received
(and getting stuck into the probe response buffer for some reason), and
then you *should* see both entries.
johannes
next prev parent reply other threads:[~2018-05-22 14:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 16:48 [PATCH] cfg80211: Fix support for flushing old scan results Tim Kourt
2018-05-18 8:13 ` Johannes Berg
2018-05-18 16:47 ` Denis Kenzior
2018-05-18 18:54 ` Arend van Spriel
2018-05-18 19:00 ` Denis Kenzior
2018-05-22 7:24 ` Arend van Spriel
2018-05-22 14:48 ` Denis Kenzior
2018-05-22 14:50 ` Johannes Berg [this message]
2018-05-22 14:51 ` Johannes Berg
2018-05-22 15:03 ` Denis Kenzior
2018-05-22 8:12 ` Johannes Berg
2018-05-22 14:50 ` Denis Kenzior
2018-05-22 20:12 ` Johannes Berg
2018-05-22 20:37 ` Denis Kenzior
2018-05-22 20:40 ` Johannes Berg
2018-05-22 20:49 ` Denis Kenzior
2018-05-22 20:52 ` Johannes Berg
2018-05-22 21:00 ` Denis Kenzior
2018-05-22 21:11 ` Johannes Berg
2018-05-22 21:25 ` Denis Kenzior
2018-05-22 21:28 ` Johannes Berg
2018-05-22 21:45 ` Denis Kenzior
2018-05-23 7:08 ` 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=1527000610.6787.14.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=denkenz@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tim.a.kourt@linux.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;
as well as URLs for NNTP newsgroup(s).