From: James Prestwood <prestwoj@gmail.com>
To: "Jonas Große Sundrup" <cherti-iwd@letopolis.de>, iwd@lists.linux.dev
Subject: Re: Force use of 5GHz band
Date: Thu, 14 Sep 2023 11:06:18 -0700 [thread overview]
Message-ID: <34795e04-66e4-4359-a6b2-59b3f47eaf64@gmail.com> (raw)
In-Reply-To: <cfdbbdb5774c4db1c8d3ec7d1e09e70e340f075c.camel@grosse-sundrup.com>
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).
Do you have debug logs of the scan results?
>
>
> Thanks,
> Jonas
>
next prev parent reply other threads:[~2023-09-14 18:06 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 [this message]
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
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=34795e04-66e4-4359-a6b2-59b3f47eaf64@gmail.com \
--to=prestwoj@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.