From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH v2 1/8] doc: Document station Affinities property
Date: Fri, 23 Aug 2024 11:03:11 -0500 [thread overview]
Message-ID: <1ae5fbdc-631b-4bac-a913-2011a7e9996e@gmail.com> (raw)
In-Reply-To: <20240819175151.1310546-1-prestwoj@gmail.com>
Hi James,
On 8/19/24 12:51 PM, James Prestwood wrote:
> This documents new DBus property that expose a bit more control to
> how IWD roams.
>
> Setting the affinity on the connected BSS effectively "locks" IWD to
> that BSS (except at critical RSSI levels, explained below). This can
> be useful for clients that have access to more information about the
> environment than IWD. For example, if a client is stationary there
> is likely no point in trying to roam until it has moved elsewhere.
>
> A new main.conf option would also be added:
>
> [General].CriticalRoamThreshold
>
> This would be the new roam threshold set if the currently connected
> BSS is in the Affinities list. If the RSSI continues to drop below
> this level IWD will still attempt to roam.
> ---
> doc/station-api.txt | 17 +++++++++++++++++
> src/iwd.config.rst | 16 ++++++++++++++++
> 2 files changed, 33 insertions(+)
Couple of questions:
> + Setting the affinity will lower the roaming threshold,
> + effectively locking IWD to the current BSS unless the
> + RSSI drops below the critical threshold set by
> + [General].CriticalRoamThreshold{_5GHz} at which point
Should '{_5GHz}' be without the '_'?
<snip>
> +
> + * - CriticalRoamThreshold5G
What about 6G?
> + - Value: rssi dBm value, from -100 to 1, default: **-82**
> +
> + This has the same effect as ``CriticalRoamThreshold``, but for the 5GHz
> + band.
> +
> * - RoamRetryInterval
> - Value: unsigned int value in seconds (default: **60**)
>
Regards,
-Denis
next prev parent reply other threads:[~2024-08-23 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 17:51 [PATCH v2 1/8] doc: Document station Affinities property James Prestwood
2024-08-19 17:51 ` [PATCH v2 2/8] netdev: store signal threshold in netdev object, not globally James Prestwood
2024-08-19 17:51 ` [PATCH v2 3/8] netdev: add critical signal threshold level James Prestwood
2024-08-23 16:07 ` Denis Kenzior
2024-08-19 17:51 ` [PATCH v2 4/8] station: emit property changed for ConnectedAccessPoint James Prestwood
2024-08-23 16:10 ` Denis Kenzior
2024-08-19 17:51 ` [PATCH v2 5/8] station: add Affinities DBus property James Prestwood
2024-08-19 17:51 ` [PATCH v2 6/8] station: Use Affinities property to change roaming threshold James Prestwood
2024-08-19 17:51 ` [PATCH v2 7/8] auto-t: add affinities property for station, and extended_service_set James Prestwood
2024-08-19 17:51 ` [PATCH v2 8/8] auto-t: add tests for Affinities behavior James Prestwood
2024-08-23 16:03 ` Denis Kenzior [this message]
2024-08-23 16:09 ` [PATCH v2 1/8] doc: Document station Affinities property James Prestwood
2024-08-23 16:11 ` Denis Kenzior
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=1ae5fbdc-631b-4bac-a913-2011a7e9996e@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.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