From: Denis Kenzior <denkenz@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>,
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 09:50:44 -0500 [thread overview]
Message-ID: <00d912c8-ecf1-8dea-fc54-c73c73f01afb@gmail.com> (raw)
In-Reply-To: <1526976774.6787.7.camel@sipsolutions.net>
Hi Johannes,
On 05/22/2018 03:12 AM, Johannes Berg wrote:
> Hi Denis,
>
>> Just FYI, there's definitely something funny with the scanning code:
>>
>> denkenz@iwd-test ~ $ sudo iw dev wlp2s0 scan flush
>> BSS 10:c3:7b:54:74:d4(on wlp2s0)
>> last seen: 274.815s [boottime]
>> freq: 5765
>> beacon interval: 100 TUs
>> signal: -35.00 dBm
>> last seen: 349 ms ago
>> Information elements from Probe Response frame:
>> SSID: \x00\x00\x00\x00\x00\x00\x00\x00\x00
>
> This is already rather strange to start with. Can you provide a sniffer
> capture of this situation?
Will do
>
> Thing is - the all-zero-bytes there points to using hidden SSID with a
> length of 9 characters, BUT
> * "myssid" is just 6 characters long - or did you edit that?
Good eyes! Yes this was edited to protect the innocent neighbors ;)
> * normally the zeroed-out SSID isn't transmitted in a *probe response*
> but only in beacons
Exactly. That's what makes this really weird.
Regards,
-Denis
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
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 [this message]
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=00d912c8-ecf1-8dea-fc54-c73c73f01afb@gmail.com \
--to=denkenz@gmail.com \
--cc=johannes@sipsolutions.net \
--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 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.