From: Dave Taht <dave@taht.net>
To: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Question on Intel AX200
Date: Sat, 25 Jan 2020 09:35:45 -0800 [thread overview]
Message-ID: <87lfpvzbf2.fsf@taht.net> (raw)
In-Reply-To: <6e9ad429-2a0b-37a8-4767-c5a036f77567@timhiggins.com> (Tim Higgins's message of "Wed, 11 Sep 2019 15:10:34 -0400")
Tim Higgins <tim@timhiggins.com> writes:
>>> On 9/11/2019 9:49 AM, Ben Greear wrote:
>>>> Hello,
>>>>
>>>> Does anyone know how well AX200 currently supports:
>>>>
>>>> OFDMA
>>>>
>>>> MU-MIMO (receiver)
>>>>
>>>> AP Mode
>>>>
>>>> And, can anyone suggest a good /AX AP to test against for these features?
>>>>
>>>> Thanks,
>>>> Ben
>>>>
>>> Hi Ben,
>>> I've been doing a lot of testing with the AX200 as a STA and
>>> sniffer, focusing on trying to see
>>> if OFDMA lives up to its advertised features. This topic is probably not of interest to this
>>> general list, so I'm happy to take the discussion to one-on-one.
>>>
>>> Tim
> I'll provide a brief summary and anyone interested can follow up directly with me.
>
> My focus is on the consumer Wi-Fi space, so I can't speak for Enterprise grade gear.
> In that space, the only products that currently have OFDMA enabled are
> the ASUS RT-AX88U (Broadcom platform), NETGEAR RAX120 (Qualcomm
> platform) and Arris SURFboard mAX PRO and SURFboard mAX PLUS. I have
> looked at the ASUS and NETGEAR, but don't have the Arris in hand.
>
> Engenius' EWS357AP (Qualcomm platform) also has OFDMA enabled. I'm not
> sure of the state of publicly released firmware. I tried a few
> firmware versions and the results were not very good. So I've set that
> one aside for now.
>
> The ASUS has beta code that the company says supports OFDMA DL in 5
> GHz best, uplink no so much and 2.4 GHz is not stable.
>
> The NETGEAR supports OFDMA in both 2.4 and 5 GHz, but downlink only.
>
> There is no product I know of that supports DL and UL OFDMA in both bands.
>
> I've been using four Samsung S10e's as my STAs to run traffic to using
> iperf3. I also have a few Intel AX200's on ASUS mini ITX boards and
> one on an ASUS pico ITX board. Right now, the AX200 is used mainly for
> capture. Thanks to help from Johannes, I got the debug kernel
> capability working that allows capturing individual AIDs. So I can
> capture OFDMA data frames and, of course, HE management and trigger
> frames.
>
> An ongoing issue is that I'm not sure what I'm supposed to be seeing
> when sniffing OFDMA DL and UL traffic. The DL OFDMA and UL OFDMA
> sequences described in David Coleman's Aerohive blog posts, which are
> also in the CWNA 5th Edition Study Guide that David co-authored, have
> yet to be seen.
> https://blog.aerohive.com/dl-ofdma/
> https://blog.aerohive.com/uplink-orthogonal-division-multiple-access-ul-ofdma-in-802-11ax/
>
> So I don't even know if the products I'm testing are implementing "proper" OFDMA.
>
> I've yet to see OFDMA's key features of higher efficiency and lower
> latency using simple TCP/IP traffic and ping. There are many moving
> parts on both AP and STA...this is going to take awhile to sort out.
parent reply other threads:[~2020-01-25 17:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6e9ad429-2a0b-37a8-4767-c5a036f77567@timhiggins.com>]
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
List information: https://lists.bufferbloat.net/postorius/lists/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfpvzbf2.fsf@taht.net \
--to=dave@taht.net \
--cc=make-wifi-fast@lists.bufferbloat.net \
/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