From: Arend van Spriel <arend@broadcom.com>
To: Johannes Berg <johannes@sipsolutions.net>, Jouni Malinen <j@w1.fi>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: broadcast ssid in scheduled scan
Date: Mon, 23 Mar 2015 22:37:39 +0100 [thread overview]
Message-ID: <551087A3.4090905@broadcom.com> (raw)
In-Reply-To: <55105DA7.3040703@broadcom.com>
On 03/23/15 19:38, Arend van Spriel wrote:
> Johannes, Jouni,
>
> I have noticed that under some circumstances wpa_supplicant initiates a
> scheduled scan with broadcast ssid. This is something our firmware can
> not do so could this be avoided? Maybe by adding a feature flag for it.
> I will look into it some more to understand the scenarios in which
> broadcast ssid is used in scheduled scan request. If you know about this
> feel free to let me know.
From the code in wpa_supplicant_req_sched_scan() it seems the wildcard
ssid (referred to as broadcast ssid) is added if one or more networks
are configured without 'scan_ssid=1'. So if none of the networks have
this option only the broadcast ssid ends up in the request.
Regards,
Arend
> Regards,
> Arend
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-03-23 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 18:38 broadcast ssid in scheduled scan Arend van Spriel
2015-03-23 21:37 ` Arend van Spriel [this message]
2015-03-31 14:21 ` Johannes Berg
2015-04-01 6:28 ` Luca Coelho
2015-04-01 9:01 ` Arend van Spriel
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=551087A3.4090905@broadcom.com \
--to=arend@broadcom.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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 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.