From: Denis Kenzior <denkenz@gmail.com>
To: Simonas Kazlauskas <iwd.lists.linux.dev@kazlauskas.me>
Cc: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: Is the data rate estimation for 5GHz channels overly pessimistic?
Date: Sat, 14 Oct 2023 13:07:27 -0500 [thread overview]
Message-ID: <05aedfe6-82ad-4e41-a9fa-e9f8a5619947@gmail.com> (raw)
In-Reply-To: <bwuu4ra65fpfpenytgu5a6ftjpvyury4omx7ucy65cshorqskl@5ikhebki4wnk>
Hi Simonas,
On 10/14/23 12:45, Simonas Kazlauskas wrote:
> Denis Kenzior wrote:
>> Hi James,
>>
>>>>
>>>> RSSI -78 dBm
>>>> AverageRSSI -79 dBm
>>>> RxMode 802.11ax
>>>> RxMCS 8
>>>> TxMode 802.11ax
>>>> TxMCS 4
>>>> TxBitrate 206400 Kbit/s
>>>> RxBitrate 206500 Kbit/s
>>>
>>> This is probably because IWD doesn't take into account any of the newer
>>> 802.11ax IEs when estimating the data rate. So its estimation is based on VHT
>>> and not the newest EHT rates.
>>
>> We should support HE rates just fine. Just look at the unit tests in
>> test-band.c. Probably need an iwmon log of the AP IEs and local capabilities
>> to see why the estimate is lower than what happens in practice.
>>
>> What hardware is being used here?
>
> Intel’s AX201 on the client side and Ubiquiti’s U6-Pro are the AP(s).
>
> Thank you for pointing me at iwmon, I’ll fiddle with it :)
It may be we screwed something up with HE since hardware was still pretty rare
when the feature was developed. But we do treat RSSI values below -82 as almost
unusable. Perhaps this needs to be tweaked for newer hardware.
If you want to get your hands dirty, it should be fairly easy to modify
unit/test-band.c to test what our estimate code does with your specific
circumstances.
The local HE capabilities can be found via 'iw phy', looking at what iwd prints
at start, or using iwmon. Similarly, remote capabilities can be sniffed using
iwmon and running an iwd scan or 'iw scan trigger'.
Me or James can walk you through all this if needed.
Regards,
-Denis
next prev parent reply other threads:[~2023-10-14 18:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 9:23 Is the data rate estimation for 5GHz channels overly pessimistic? Simonas Kazlauskas
2023-10-14 16:02 ` James Prestwood
2023-10-14 17:36 ` Denis Kenzior
2023-10-14 17:45 ` Simonas Kazlauskas
2023-10-14 18:07 ` Denis Kenzior [this message]
2023-10-15 19:40 ` Simonas Kazlauskas
2023-10-16 11:35 ` James Prestwood
2023-10-16 12:38 ` James Prestwood
2023-10-16 19:12 ` Denis Kenzior
2023-10-16 20:20 ` Simonas Kazlauskas
2023-10-21 23:23 ` Simonas Kazlauskas
2023-10-22 20:14 ` Denis Kenzior
2023-10-24 12:32 ` James Prestwood
2023-10-24 14:26 ` Denis Kenzior
2023-10-24 15:06 ` James Prestwood
2023-10-24 15:32 ` Denis Kenzior
2023-10-24 15:40 ` James Prestwood
2023-10-24 15:19 ` Simonas Kazlauskas
2023-10-24 15:29 ` Denis Kenzior
2023-10-16 18:36 ` Denis Kenzior
2023-10-14 17:42 ` Simonas Kazlauskas
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=05aedfe6-82ad-4e41-a9fa-e9f8a5619947@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd.lists.linux.dev@kazlauskas.me \
--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 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.