From: Denis Kenzior <denkenz@gmail.com>
To: "Pedro André" <PEDA@bang-olufsen.dk>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: [PATCH] add AllowRoaming station property
Date: Wed, 18 Oct 2023 09:20:17 -0500 [thread overview]
Message-ID: <cd9a73d3-8ed9-4c76-b44c-4c8af6250977@gmail.com> (raw)
In-Reply-To: <20231018122534.33455-1-peda@bang-olufsen.dk>
Hi Pedro,
On 10/18/23 07:27, Pedro André wrote:
> From: Pedro Andre <peda@bang-olufsen.dk>
>
> This adds an AllowRoaming property to the station struct that makes it
> possible to indicate to the station/interface that it should not go
> into roaming state (when set to false). This property defaults to true
> (i.e. it defaults to the normal iwd behaviour that allows roaming).
>
Is it possible for you to share the actual use case for this? It would help to
understand what problem this is trying to solve. One problem I see here is that
we might still want to honor AP directed roaming.
> ---
> src/station.c | 40 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
>
<snip>
> +static struct l_dbus_message *station_property_set_allow_roaming(
> + struct l_dbus *dbus,
> + struct l_dbus_message *message,
> + struct l_dbus_message_iter *new_value,
> + l_dbus_property_complete_cb_t complete,
> + void *user_data)
> +{
> + struct station *station = user_data;
> + bool roaming;
> +
> + if (!l_dbus_message_iter_get_variant(new_value, "b", &roaming))
> + return dbus_error_invalid_args(message);
> +
> + l_debug("Setting allow_roaming %s", roaming ? "true" : "false");
> +
> + station->allow_roaming = roaming;
So what happens if we're in the middle of a roam?
Also, what happens if this is reset to true and our rssi is already below the
roam threshold?
> +
> + return l_dbus_message_new_method_return(message);
> +}
> +
> void station_foreach(station_foreach_func_t func, void *user_data)
> {
> const struct l_queue_entry *entry;
<snip>
> @@ -4484,6 +4522,8 @@ static void station_setup_interface(struct l_dbus_interface *interface)
> station_property_get_scanning, NULL);
> l_dbus_interface_property(interface, "State", 0, "s",
> station_property_get_state, NULL);
> + l_dbus_interface_property(interface, "AllowRoaming", 0, "b",
> + station_property_get_allow_roaming, station_property_set_allow_roaming);
doc/coding-style.txt, Section 'Background', paragraph 2.
Also, there's missing documentation for this property. And it seems to overlap
rather significantly with "DisableRoamingScan" setting. What's the plan there?
And since we're adding a new API, can we at least add an auto test?
Regards,
-Denis
next prev parent reply other threads:[~2023-10-18 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 12:27 [PATCH] add AllowRoaming station property Pedro André
2023-10-18 12:51 ` James Prestwood
2023-10-18 14:32 ` Denis Kenzior
2023-10-18 14:56 ` James Prestwood
2023-10-18 14:20 ` Denis Kenzior [this message]
2023-10-19 11:55 ` Pedro André
2023-10-20 14:57 ` Denis Kenzior
2023-10-20 16:29 ` 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=cd9a73d3-8ed9-4c76-b44c-4c8af6250977@gmail.com \
--to=denkenz@gmail.com \
--cc=PEDA@bang-olufsen.dk \
--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