connman.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <wagi@monom.org>
To: HENRIET Vivien <vivien.henriet@overkiz.com>
Cc: "connman@lists.linux.dev" <connman@lists.linux.dev>
Subject: Re: [PATCH] wifi: Choose a random channel when opening an ap
Date: Wed, 29 Sep 2021 11:16:41 +0200	[thread overview]
Message-ID: <20210929091641.fg4v7pbol2nysgrd@carbon.lan> (raw)
In-Reply-To: <bd9eda8f-02c8-7ae0-7fa7-5bf8b2127db8@overkiz.com>

Hi Vivien,

On Wed, Sep 29, 2021 at 08:57:25AM +0000, HENRIET Vivien wrote:
> Hi Daniel,
> 
> Could you have a look to this patch?

Sorry for the delay. Anyway, I think it would be better to make this
configurable or smarter instead of a random channel selection. I just
checked what iwd is doing and if I got it right, the iwd daemon does the
channel selection itself.

> I would like to be able to open the WiFi AP on different channel.
> The simplest way to do it, is to select a random channel, which fit my need.
> Do you think its acceptable to integrate this way?

Random channel selection is a bit a wild solution :).

> I've got also other ideas to achieve the same goal:
> - Add an optional channel parameter when opening the AP

This is what I would suggest. Alternatively, can't we use some metrics
from the last scan to figure out which channel is crowded?

> - Add a global config to set the channel

Generally I would like to avoid adding more config option if there is a
way to figure it out.

Daniel


  reply	other threads:[~2021-09-29  9:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23 12:44 [PATCH] wifi: Choose a random channel when opening an ap Vivien Henriet
2021-09-29  8:57 ` HENRIET Vivien
2021-09-29  9:16   ` Daniel Wagner [this message]
2021-10-04  6:45     ` Michael Nazzareno Trimarchi
2021-10-04  7:09       ` Daniel Wagner
2021-10-04  7:34         ` Michael Nazzareno Trimarchi
2021-10-04  7:46           ` Daniel Wagner
2021-10-04 21:21             ` Michael Nazzareno Trimarchi

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=20210929091641.fg4v7pbol2nysgrd@carbon.lan \
    --to=wagi@monom.org \
    --cc=connman@lists.linux.dev \
    --cc=vivien.henriet@overkiz.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).