Wi-Fi Packet Queue Control Field Sizes: A Closer Look

When it comes to Wi-Fi network performance, most users focus on data transfer speed or coverage. However, the real bottlenecks often lie at the network level. package management — this is where delays, losses, and inefficient use of the channel occur. One of the key aspects is queue management (queue management), which ensures the correct delivery of frames in conditions of interference and competition for airtime.

In this article we will figure out, how many bytes exactly is allocated for the fields responsible for the order in a standard Wi-Fi packet (802.11), including Sequence Control, QoS Control and control bits in the MAC header. You'll learn how these fields affect the overall packet size, why they can't simply be "removed" to save traffic, and how modern standards (like 802.11ax) optimize this process. This material will be useful for both network engineers and advanced users who want to gain a deeper understanding of how wireless networks operate.

Let's be clear: this topic is technically complex, but we'll try to explain it without unnecessary jargon. If you're new to network protocol analysis, we recommend reading our guide first. the basics of Wi-Fi packet structure (section below). For experienced readers, skip to parsing bytes.

Basics: Wi-Fi Packet Structure and the Role of Queue Management

Any packet in a Wi-Fi network consists of several layers, but for our topic, the most critical one is MAC header (Media Access Control). This is where the fields responsible for:

• 🔄 Delivery procedure (Sequence Number - prevents duplication of packages).
• 📦 Traffic prioritization (QoS Control — for voice calls, video, etc.).
• ✅ Confirmation of receipt (ACK — a mechanism for retransmission in case of errors).
• 🔄 Fragmentation (Fragment Number - if the package is too big).

Without these fields, the network simply wouldn't be able to function: packets would be lost, duplicated, or delivered out of order. For example, when watching video over Wi-Fi, the field Sequence Number ensures that frames will be played without interruption, even if some packets have to be retransmitted due to interference.

It is important to understand that queue management — this is not a single field, but a collection of mechanisms distributed across different parts of the header. Their total size depends on:

• 📡 Versions of the Wi-Fi standard (in 802.11ax New multiplexing capabilities have been added).
• 🔧 Frame type (control, data, access control).
• 🎯 QoS (Quality of Service) availability - in networks without prioritization, some fields may be missing.

How many bytes does queue management take: field-by-field breakdown

Now let's move on to specific numbers. Let's look at the standard data frame (Data Frame) in a Wi-Fi network with QoS support (typical for modern networks). Its MAC header has a fixed and variable portion. The following fields are critical for queuing:

Total, minimum overhead size to control the queue in a typical QoS packet:

• 🔢 Sequence Control + QoS Control = 4 bytes.
• 📊 Taking into account Frame Control And Duration (which are indirectly involved in access control) - 8 bytes.
• 🚀 On the networks 802.11ax fields are added for HE Control, which can increase the header by another 2–6 bytes.

4–8 bytes may seem like a small amount. But under high load conditions (for example, when streaming 4K video or on a network with 50+ devices), these overheads add up. For example, when transmitting 1,000 packets per second, Sequence Control 2 KB/s of service traffic is used!

Why can't you just reduce the size of the fields?

At first glance, reducing overhead bytes seems like a logical step to increasing usable throughput. However, this has serious consequences:

⚠️ Attention: Reducing the size Sequence Number (for example, from 12 to 8 bits) will result in cyclic repetition of package numbers Every 256 frames. In a busy network, this will cause collisions: the router will not be able to distinguish a new packet from a retransmission of an old one, leading to data loss.

Other risks:

• 🔄 Packet loss without recovery (if you remove ACK or reduce timeouts).
• 🎥 Video stuttering and audio artifacts when disabling QoS (priorities for multimedia).
• 📵 Speed ​​drop in networks with interference (without Fragment Number large packets will be lost entirely).

Standard Engineers 802.11 have already optimized field sizes taking into account the balance between overhead costs and reliability. For example, in 802.11ax Instead of reducing service bytes, we implemented:

• 🔗 Aggregation (combining several packets into one frame, which reduces the proportion of headers).
• 📶 OFDMA (simultaneous transmission to multiple devices, reducing channel competition).
• ⚡ Target Wake Time (TWT) (scheduling device activity time, reducing the number of service packets).

Comparison of standards: how the size of service fields has changed

The size of queue management fields has evolved along with Wi-Fi standards. Below is a comparison table for the most common versions:

Paradoxically, in the new standards the headings are increasing, rather than decreasing. This is due to the addition of features for:

• 🎯 Multiplexing (simultaneous work with several devices).
• 🔋 Energy saving (TWT allows devices to "sleep" between transmissions.)
• 📡 Resistance to interference (BSS Coloring reduces collisions in dense networks).

However, thanks to aggregation and OFDMA effective throughput grows despite the increase in service data. For example, in Wi-Fi 6 The actual speed in a busy network can be 2-4 times higher than in Wi-Fi 5, even if the raw transmission speed has only increased by 30–40%.

Practical example: how much traffic does queue management "eat"?

Let's calculate what percentage of traffic goes to service fields in a typical scenario. Let's take:

• 📦 Average payload size = 1200 bytes (typical for web traffic).
• 📡 Standard = 802.11ac (Wi-Fi 5) with QoS.
• 🔄 Frame aggregation = 4 packets in one physical frame.

Calculation:

1. Header size per packet: 36 bytes (including QoS Control And VHT Control).
2. When aggregating 4 packages:
   • General header = 36 bytes (per group) + 4 x 4 bytes (individual Sequence Control for each package) = 52 bytes.
   • Payload = 4 × 1200 bytes = 4800 bytes.

1% seems insignificant. But in real life:

• 📉 When transmitting small packets (for example, TCP ACK size of 40 bytes) the proportion of headers increases to 30–40%.
• 🎮 In online games or VoIP, packets are often 60-100 bytes in size, which increases the overhead to 15–25%.
• 📡 In networks with interference, the number of retransmissions increases, and with it the share of service traffic.

⚠️ Attention: If you have a lot of small packet devices on your network (IoT sensors, IP cameras), consider disabling QoS for background traffic or manually setting priorities. This will reduce overhead costs by 5-10%.

How to Optimize Overhead in Your Network

While it's impossible to completely eliminate order control fields, their impact on performance can be reduced. Here are some practical steps:

Enable frame aggregation (A-MPDU/A-MSDU) in the router settings|

Disable QoS for devices with background traffic (e.g. smart bulbs)|

Update your router firmware to a version that supports 802.11ax (if your hardware allows it)|

Use 80 or 160 MHz wide channels (reduces retransmissions)|

Manually configure QoS priorities for critical devices (e.g. set-top boxes or IP telephony)

-->

Let's look at each point in more detail:

1. Aggregation (A-MPDU/A-MSDU):

   Packet aggregation reduces the amount of headers. In modern routers, this option is usually enabled by default, but it can be forced to activate in the section Wireless → Advanced → AggregationFor example, in firmware DD-WRT or OpenWRT This is done with the command:

   iw dev wlan0 set bitrates legacy-2.4 6 9 12 18 24 36 54 65
   iw dev wlan0 set ampdu force

2. Disabling QoS for background traffic:

   In routers based on Tomato or Asuswrt-Merlin You can create rules that disable prioritization for specific MAC addresses. For example, for IoT devices:

   iptables -t mangle -A PREROUTING -m mac --mac-source 00:11:22:33:44:55 -j CLASSIFY --set-class 0:0

   This will reduce the overhead by 2 bytes (QoS Control) for each packet from these devices.

3. Upgrade to Wi-Fi 6:

   If your router supports 802.11ax, turn on OFDMA And BSS ColoringThis will reduce the number of collisions and retransmissions, indirectly reducing the share of service traffic. In firmware OpenWRT This is configured via:

   uci set wireless.radio0.he_su_beamformee=1
   uci set wireless.radio0.he_bss_color=1
   uci commit

Important: Before making changes Make a backup copy of your router settingsSome options (such as forced aggregation) may cause instability with older devices.

Common Myths About Wi-Fi Queue Management

There are many misconceptions surrounding Wi-Fi service fields. Let's address the most common ones:

1. "Disabling QoS will speed up the network."

   ❌ Reality: Disabling QoS will remove two bytes from the header, but will deprioritize critical traffic (such as voice calls). As a result, video in Zoom will start to lag, even if the test speed increases by 1–2%.

2. "Sequence Control fields are useless in modern networks."

   ❌ Reality: Even in Wi-Fi 6 These fields are critical for retransmission mechanisms (Retry) and defragmentation. Without them, the network will become unstable at the slightest interference.

3. "Aggregation of personnel is always useful"

   ❌ Reality: In networks with devices that do not support aggregation (e.g. older smartphones), forcing A-MPDUs may result in loss of compatibility.

4. Wi-Fi 6 Reduces Header Size

   ❌ Reality: Headlines in 802.11ax steel more, but thanks to OFDMA and TWT their impact on performance has been reduced.

⚠️ Attention: If you see advice like "remove the Duration field to speed up the network" - this is bad advice. Field Duration necessary for the mechanism NAV (Network Allocation Vector), which prevents collisions. Removing it would lead to chaos in the airwaves.

FAQ: Frequently asked questions about Wi-Fi queue management

iw dev wlan0 get power_save
iw dev wlan0 get ampdu