public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: "James Prestwood" <prestwoj@gmail.com>,
	"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:32:37 -0500	[thread overview]
Message-ID: <76261973-a04e-488c-8fc0-a0f623c15af0@gmail.com> (raw)
In-Reply-To: <8bef6b0a-8284-4889-bd23-b33e26b450f2@gmail.com>

Hi James,

> 
> LGTM, I actually needed something along these lines for dynamically disabling 
> roaming e.g. during a software upgrade or some time when networking is critical. 
> Just hadn't gotten to it yet.

I'm curious about the use cases.  What were your thoughts on how this should 
look like?

I imagine for things like firmware update you still have a set time limit in 
which this upgrade should happen?

Right now I like Pedro's earlier proposal with the minimum throughput guidance. 
I think we can go further and calculate the roaming RSSI threshold based on the 
minimum throughput.  This would allow iwd to ignore roaming until that minimum 
throughput can no longer be delivered.

If we need a bigger hammer, then we may want to consider using an implementation 
similar to how Modem.Lockdown was implemented in oFono.

Regards,
-Denis

  reply	other threads:[~2023-10-18 14:32 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 [this message]
2023-10-18 14:56     ` James Prestwood
2023-10-18 14:20 ` Denis Kenzior
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=76261973-a04e-488c-8fc0-a0f623c15af0@gmail.com \
    --to=denkenz@gmail.com \
    --cc=PEDA@bang-olufsen.dk \
    --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