From: James Prestwood <prestwoj@gmail.com>
To: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
Cc: "Jonas Große Sundrup" <cherti-iwd@letopolis.de>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>,
"Pedro André" <PEDA@bang-olufsen.dk>
Subject: Re: Force use of 5GHz band
Date: Thu, 21 Sep 2023 07:50:02 -0700 [thread overview]
Message-ID: <0aae89f9-0ca6-4748-9e69-b0413a15e90c@gmail.com> (raw)
In-Reply-To: <cmbwlnlbewbuiu4ricqyl3txilk6ybvvmoqyu3ljmui6imuzjw@rs2ug3nxl37w>
Hi Alvin,
On 9/21/23 7:21 AM, Alvin Šipraga wrote:
> On Thu, Sep 14, 2023 at 11:06:18AM -0700, James Prestwood wrote:
>> Hi Jonas,
>>
>> On 9/14/23 10:44 AM, Jonas Große Sundrup wrote:
>>> Hi,
>>>
>>> is there a way to force iwd to use the 5GHz flavor of a specific wifi?
>>> I am aware of BandModifier5GHz, but even with setting this to 1000 I
>>> still end up on the 2.5GHz band. That band specifically, however, is
>>> unfortunately suspect for some stability issues I'm facing and hence I
>>> would like to force iwd onto the 5GHz band to see if the problems still
>>> occur. That proves to be difficult, of course, if iwd is picking the
>>> 2.5GHz band…
>>>
>>> Even though I do see that iwd probably has the better insight into band
>>> stability from a signal-strength point of view, any chance of
>>> overruling iwd's internal mechanisms here? (Or should I just crank up
>>> BandModifier5GHz by a couple of magnitudes?)
>>
>> All we have now is BandModifier5GHz which is multiplied by the computed
>> rank. The stock rank is based mainly on a data rate computation which is
>> theoretical, but uses capabilities and signal strength to estimate.
>>
>> 1000 is pretty high, so essentially your 2.4GHz BSS's would need to have a
>> rank 1000x larger than the 5Ghz ones. So either 5ghz is incredibly low
>> signal, doesn't support HT/VHT, or maybe the IEs are malformed so the data
>> rate isn't being computed correctly e.g. (defaulting to basic rates).
>
> We had a request at the company to disable 2.4 GHz entirely as well, but I did
> not want to completely disable it as some customers may not even have 5 GHz
> infrastructure. My colleague Pedro drafted a patch which allows for the internal
> BSS ranking to be normalized according to a required bitrate, so that 5 GHz
> networks do not always out-compete 2.4 GHz networks. We found this worked well
> together with the BandModifier option.
Effectively yes this would work, though its not a guarantee to disable
2.4 (although the option isn't named as such so its not deceiving anyone).
I personally don't take issue to adding such an option, but FWIW I'm
currently working on a way to explicitly disable a band entirely. This
is more complicated due to IWD's scanning logic but its better in that
it prevents IWD from scanning on those bands as well as connecting.
Thanks,
James
>
> I have asked him to send the patch to the list, so please take a look. Might be
> something of interest for upstream.
>
> Kind regards,
> Alvin
prev parent reply other threads:[~2023-09-21 14:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 17:44 Force use of 5GHz band Jonas Große Sundrup
2023-09-14 18:06 ` James Prestwood
2023-09-14 18:13 ` Jonas Große Sundrup
2023-09-14 18:16 ` James Prestwood
2023-09-14 18:22 ` Jonas Große Sundrup
2023-09-14 18:33 ` James Prestwood
2023-09-14 18:46 ` Jonas Große Sundrup
2023-09-15 14:35 ` Denis Kenzior
2023-09-15 14:44 ` James Prestwood
2023-09-15 14:55 ` Denis Kenzior
2023-09-15 14:30 ` Denis Kenzior
2023-09-15 14:42 ` James Prestwood
2023-09-15 14:47 ` Denis Kenzior
2023-09-15 17:36 ` James Prestwood
2023-09-16 15:18 ` Denis Kenzior
2023-09-19 17:29 ` James Prestwood
2023-09-21 14:21 ` Alvin Šipraga
2023-09-21 14:50 ` James Prestwood [this message]
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=0aae89f9-0ca6-4748-9e69-b0413a15e90c@gmail.com \
--to=prestwoj@gmail.com \
--cc=ALSI@bang-olufsen.dk \
--cc=PEDA@bang-olufsen.dk \
--cc=cherti-iwd@letopolis.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).