From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v3 1/8] doc: Document station Affinities property
Date: Fri, 23 Aug 2024 10:59:59 -0700 [thread overview]
Message-ID: <20240823180006.317353-1-prestwoj@gmail.com> (raw)
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(+)
v3:
* Fixed typo
diff --git a/doc/station-api.txt b/doc/station-api.txt
index 84f1b7bf..707c6834 100644
--- a/doc/station-api.txt
+++ b/doc/station-api.txt
@@ -170,6 +170,23 @@ Properties string State [readonly]
BSS the device is currently connected to or to which
a connection is in progress.
+ ao Affinities [optional] [experimental]
+
+ Array of net.connman.iwd.BasicServiceSet object paths
+ that will be treated with higher affinity compared to
+ other BSS's. Currently the only allowed value to be
+ set in this array is the path to the currently connected
+ BasicServiceSet object, i.e.
+ Station.ConnectedAccessPoint.
+
+ 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{5G} at which point
+ IWD will proceed with normal roaming behavior.
+
+ This property is cleared on roams/disconnections.
+
SignalLevelAgent hierarchy
==========================
diff --git a/src/iwd.config.rst b/src/iwd.config.rst
index d9c94e01..2d1f6dcd 100644
--- a/src/iwd.config.rst
+++ b/src/iwd.config.rst
@@ -130,6 +130,22 @@ The group ``[General]`` contains general settings.
This value can be used to control how aggressively **iwd** roams when
connected to a 5GHz access point.
+ * - CriticalRoamThreshold
+ - Value: rssi dBm value, from -100 to 1, default: **-80**
+
+ The threshold (for 2.4GHz) at which IWD will roam regardless of the
+ affinity set to the current BSS. If the connected BSS has affinity
+ (set in Station's Affinities list) the roam threshold will be lowed to
+ this value and IWD will not attempt to roam (or roam scan) until either
+ the affinity is cleared, or the signal drops below this threshold.
+
+
+ * - CriticalRoamThreshold5G
+ - 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**)
--
2.34.1
next reply other threads:[~2024-08-23 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 17:59 James Prestwood [this message]
2024-08-23 18:00 ` [PATCH v3 2/8] netdev: define netdev settings in netdev.h James Prestwood
2024-08-23 21:03 ` Ryan Smith
2024-08-23 22:24 ` James Prestwood
2024-08-23 18:00 ` [PATCH v3 3/8] netdev: store signal threshold in netdev object, not globally James Prestwood
2024-08-23 18:00 ` [PATCH v3 4/8] netdev: add critical signal threshold level James Prestwood
2024-08-23 18:00 ` [PATCH v3 5/8] station: add Affinities DBus property James Prestwood
2024-08-23 18:00 ` [PATCH v3 6/8] station: Use Affinities property to change roaming threshold James Prestwood
2024-08-23 18:00 ` [PATCH v3 7/8] auto-t: add affinities property for station, and extended_service_set James Prestwood
2024-08-23 18:00 ` [PATCH v3 8/8] auto-t: add tests for Affinities behavior James Prestwood
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=20240823180006.317353-1-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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