From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.taht.net (mail.taht.net [IPv6:2a01:7e00:e000:2d4:f00f:f00f:b33b:b33b]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id BDE793B2A4 for ; Sat, 25 Jan 2020 12:35:49 -0500 (EST) Received: from dancer.taht.net (unknown [IPv6:2601:646:8301:676f:eea8:6bff:fefe:9a2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.taht.net (Postfix) with ESMTPSA id 8E6C02296C for ; Sat, 25 Jan 2020 17:35:47 +0000 (UTC) From: Dave Taht To: make-wifi-fast@lists.bufferbloat.net References: <33bd9a39-0028-2f99-f43e-5e15c9e87287@candelatech.com> <6e9ad429-2a0b-37a8-4767-c5a036f77567@timhiggins.com> Date: Sat, 25 Jan 2020 09:35:45 -0800 In-Reply-To: <6e9ad429-2a0b-37a8-4767-c5a036f77567@timhiggins.com> (Tim Higgins's message of "Wed, 11 Sep 2019 15:10:34 -0400") Message-ID: <87lfpvzbf2.fsf@taht.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] Question on Intel AX200 X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2020 17:35:49 -0000 Tim Higgins 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 featur= es? >>>> >>>> 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 no= t 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),=C2=A0 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-o= fdma-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.