linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: Arend van Spriel <arend@broadcom.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	Hante Meuleman <meuleman@broadcom.com>,
	Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH 08/11] brcmfmac: Make 5G join preference configurable.
Date: Wed, 2 Dec 2015 17:12:45 +0200	[thread overview]
Message-ID: <20151202151245.GA25870@w1.fi> (raw)
In-Reply-To: <565EF307.90002@broadcom.com>

On Wed, Dec 02, 2015 at 02:32:55PM +0100, Arend van Spriel wrote:
> On 12/01/2015 12:08 PM, Jouni Malinen wrote:
> >I would like to see this as a new attribute to NL80211_CMD_CONNECT to
> >provide parameters for offloaded (driver and/or firmware) BSS selection
> >and roaming. If there is a driver that uses roaming offload with
> >NL80211_CMD_ASSOCIATE, the same attribute could be used there (but I'm
> >not sure how exact such offloading would work in practice since I'd
> >expect both authentication and (re)association to be offloaded).
> 
> Sounds reasonable. Just would like to explore the use-case a bit
> more. Looking at tools like NetworkManager and android network list,
> the user is always presented with just SSID listed once. For
> NetworkManager details can be configured for a connection and the
> bss selection parameters could be one of those. What level of detail
> would be needed there. Not saying we can not have more detail in the
> nl80211 API.

As far as wpa_supplicant is concerned, I'm thinking of having a "global
parameter" as the default and option to have per-network override. For
most end user GUI things, I'm not sure there would be much to expose
(i.e., seems reasonable to prefer 5 GHz nowadays by default). For an
advanced UI, there could be an option to toggle this type of information
on/off or even give more details like how many dB to prefer.

> So does the driver need to advertise support for bss selection
> parameters or can it simply ignore the parameters. Assuming the
> latter for now.

I thought about this a bit and did not ask for such advertisement since
I didn't see how wpa_supplicant would behave any differently based on
the knowledge.. That said, if someone does think of exposing this in an
UI to a real end user, it would be convenient to have means for
determining whether the parameter is really supported. However, I'm not
sure vendors would provide the exact same set of configuration
parameters for this type of preferences for offloaded roaming, so coming
up with a generic and detailed advertisement can be a bit difficult.
Yes/no advertisement of something along the lines of preference for 5
GHz might be easier to handle.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2015-12-02 15:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25 10:32 [PATCH 00/11] brcmfmac: beamforming support and cleanup Arend van Spriel
2015-11-25 10:32 ` [PATCH 01/11] brcmfmac: Cleanup ssid storage Arend van Spriel
2015-11-30 12:48   ` [01/11] " Kalle Valo
2015-11-30 12:49     ` Kalle Valo
2015-11-25 10:32 ` [PATCH 02/11] brcmfmac: Return actual error by fwil Arend van Spriel
2015-11-25 10:32 ` [PATCH 03/11] brcmfmac: Change error print on wlan0 existence Arend van Spriel
2015-11-25 10:32 ` [PATCH 04/11] brcmfmac: no retries on rxglom superframe errors Arend van Spriel
2015-11-25 10:32 ` [PATCH 05/11] brcmfmac: Remove redundant parameter action from scan Arend van Spriel
2015-11-25 10:32 ` [PATCH 06/11] brcmfmac: Cleanup roaming configuration Arend van Spriel
2015-11-25 10:32 ` [PATCH 07/11] brcmfmac: Add beamforming support Arend van Spriel
2015-11-25 10:32 ` [PATCH 08/11] brcmfmac: Make 5G join preference configurable Arend van Spriel
2015-11-30 10:58   ` Kalle Valo
2015-12-01  8:33     ` Arend van Spriel
2015-12-01  9:48       ` Kalle Valo
2015-12-01 11:08         ` Jouni Malinen
2015-12-02 13:32           ` Arend van Spriel
2015-12-02 15:12             ` Jouni Malinen [this message]
2015-12-02 16:38             ` Dan Williams
2015-12-02 18:00               ` Paul Stewart
2015-12-02 21:07                 ` Dan Williams
2015-12-03 21:28                 ` Arend van Spriel
2015-11-25 10:32 ` [PATCH 09/11] brcmfmac: assure net_ratelimit() is declared before use Arend van Spriel
2015-11-25 10:32 ` [PATCH 10/11] brcmfmac: Unify methods to define and map firmware files Arend van Spriel
2015-11-25 10:32 ` [PATCH 11/11] brcmfmac: Fix double free on exception at module load Arend van Spriel
2015-11-30 11:00   ` Kalle Valo

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=20151202151245.GA25870@w1.fi \
    --to=j@w1.fi \
    --cc=arend@broadcom.com \
    --cc=dcbw@redhat.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=meuleman@broadcom.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).