During Wireless LAN Professional Conference 2019 (WLPC_EU) in Prague, I had a presentation where the WiFi AirTime Calculator was presented. You can read about it and download it from here. And I used the results from the calculator to look at data rate versus throughput in a WiFi network.

Note
This is a theoretical approach and we assume it is no other traffic in the BSS or on the channel. And it is on a 20 MHz channel at the 5 GHz.
A Data field size of 300 bytes is used in this article. I call it the Data field size, other common names are payloads, MPDU, A-MPDU or frame body. The Data field is the correct name according to the standard and it embraces all frame format types.

Read More »

I have made a YouTube video on how to capture 802.11ax OFDMA traffic with Jetson Nano. It is pretty much the same as in this article and this article

The process of wireless capturing of 802.11ax OFDMA-frames has evolved. The newest step, for me, is to capture the UL OFDMA frames.

I use the NVIDIA Jetson Nano developer kit with the Intel AX200 NIC for wireless capturing and I have earlier showed how to capture:

• Single-user 802.11 in this blog
  • But Francois Verges has developed this method, see his blog
• Multi-user frames during DL OFDMA in this blog
• UL OFDMA without capturing the data frames in this blog

Read More »

LENGTH, the subfield in the legacy Signal field of every 802.11 WiFi frames legacy preamble is more important than you maybe think.

Remarks: This is primarily for the 802.11 5GHz band

During CWNA, and other wireless studies, the Duration value in the MAC header gets a lot of attention because it is used to protect the transmission. But this is only half the truth. The Duration value is only to protect the rest of the transmission after the frame currently been sent. In many of the 802.11 frames, this duration value is either 0 or a very small value. The only place it has real value is in a TXOP with protection, with RTS and CTS. In the RTS and CTS frames, this Duration value includes the duration of the rest of the transmission, including the QoS frame, the ACK-frame, and all the SIFS.

Read More »

The introduction of the OFDMA feature in the 802.11ax standard gives us packet analyzers some challenges regarding wireless capturing. It is two aspects that are challenging. Capture data inside specific resource units (RUs) and how to visualize it in a graphic user interface (GUI) if we can capture several parallel transmissions.
Some experts have said it would be very difficult to do multi-user capturing, but I have always thought it should be possible to do this
It is basically the same transmission method as we have used for over 20 years. It is some new frame formats and the OFDM subcarriers are split between several stations, but that’s all (almost).

Read More »

My previous blog post was on how the RF spectrum looks like during a UL ODFMA transmission.

This article is about the DL OFDMA transmission. The DL ODFMA transmission can be preceded by an MU-RTS (multi-user request to send) and CTS (clear-to-send). I keep it to a later article.

Read More »

During 802.11ax UL OFDMA magic happens in the RF space. What were RF collisions before is with 802.11ax normal behavior.

I will in this blog briefly explain what happens in the RF space during UL OFDMA.
I recommend reading one of the previous articles where I explain what it looks like in Wireshark.
I will simplify it so it is two clients that will send their data uplink in two different 106-tones RU

A short summary of the UL OFDMA process
– The AP sends a Basic Trigger frame, as a broadcast frame, in the legacy frame format at one of the mandatory rates
– STAs (clients) that are announced in the Basic Trigger frame sends their data uplink to the AP in parallel
— The AP sends a broadcast Multi-STA BlockAck frame to acknowledgment the received data frames

Read More »