Many users, when trying to improve the quality of their wireless connection, encounter confusing parameters in the advanced settings of network adapter drivers or professional equipment interfaces. One such parameter is the "ready to transmit threshold," often referred to as Ready to Transmit or related to the RTS/CTS mechanism. Misinterpreting this value can lead to a drop in speed or, conversely, an increase in the number of collisions in the air.
The essence of this parameter lies in the collision avoidance protocols that underlie wireless communication standards. When a device "hears" a lot of noise or other networks, it needs to determine whether there's enough space to transmit a data packet. If the threshold is set too low, the router will remain silent where it could otherwise transmit data. If it's set too high, it will constantly retransmit and lose packets.
In this article, we'll take a detailed look at what exactly this term means, how it relates to packet fragmentation and the RTS mechanism, and provide specific recommendations on the best numerical value to set for a city apartment, a private home, or an office with a high device density.
What's behind the Ready to Transmit parameter?
Technical parameter Ready to Transmit Threshold (or the associated RTS Threshold) determines the minimum data packet size that requires channel readiness confirmation. In WiFi networks, where all devices share the same radio frequency, it's crucial to avoid situations where two devices start talking at the same time. This phenomenon is called a collision.
When the transmitted packet size exceeds a set threshold, a handshake is activated. The device sends a short service request (Request to Send), waiting for a response (Clear to Send) from the router. Only after receiving an acknowledgment does it begin transmitting the bulk of the data. This helps clear the air of interference, but adds latency.
If you see this parameter in your computer's network card driver settings, it often controls the aggressiveness of transmission attempts. A low threshold value forces the adapter to check the channel more frequently, which is useful in noisy environments, but reduces overall throughput. A high value allows for streaming data, ignoring minor interference, which is ideal for a clear signal.
- 📡 Small threshold: increases reliability in conditions of strong interference, but reduces speed.
- 🚀 Large threshold: maximizes speed under ideal conditions, but has a higher risk of packet loss.
- ⚙️ Default value: typically 2347 bytes, which effectively disables checking for most packets.
⚠️ Attention: Changing this setting in Windows drivers (under the "Advanced" tab) only affects the operation of this specific adapter. Changing it on your laptop won't fix any signal issues with the router itself.
Relationship of the transmission threshold with the RTS/CTS mechanism
It is impossible to correctly set the readiness threshold without understanding the mechanism RTS/CTS (Request to Send / Clear to Send). This protocol was developed specifically to solve the "hidden node" problem. Imagine this: your laptop can't "hear" your neighbor's router from behind the wall, but they're both on the same channel. The laptop thinks the airwaves are clear and begins transmitting, while the neighbor also begins broadcasting. A collision occurs, and data is lost.
The Threshold parameter sets the limit in bytes. If a data packet is smaller than this value, it is sent immediately. If it is larger, a negotiation process is initiated. In modern networks, where video traffic and large files predominate, packets often exceed the standard 1500 bytes, so setting this limit becomes critical for stability.
There's also a downside. If you set the threshold too low (for example, 500 bytes), even small service packets will undergo a handshake. This will create a huge amount of service traffic ("overhead"), which will eat up the useful bandwidth. The result will be a stable but very slow internet connection.
Technical detail about hidden nodes
The hidden node problem occurs when two WiFi clients are within the coverage area of a single access point but cannot hear each other due to physical obstructions. Without RTS/CTS, their simultaneous data transmissions are guaranteed to result in a collision at the access point, as it will be unable to decode either signal.
The Impact of Fragmentation Size on Network Stability
Often, along with the readiness threshold, users encounter the parameter Fragmentation ThresholdThese two settings are closely related. Fragmentation allows large data packets to be broken into smaller pieces before transmission. In noisy radio environments, the probability of transmission errors when transmitting a small packet is significantly lower than when transmitting a large one.
If the airwaves are "dirty" (with many neighboring networks, microwave ovens, or Bluetooth devices), lowering the fragmentation threshold and RTS threshold helps improve overall connection reliability. Smaller packets are transmitted faster and receive acknowledgements (ACKs) more quickly. If one small fragment is lost, only that fragment is retransmitted, rather than the entire large file.
However, as with RTS, excessive fragmentation hurts performance. Each fragment requires its own header and acknowledgement, which increases overhead. Therefore, the golden rule is: don't tweak these settings unless you have obvious issues with packet loss or unstable ping.
| Parameter | Recommended value (Home) | Recommended value (Office) | Impact on speed |
|---|---|---|---|
| RTS Threshold | 2347 (Default) | 1500-2000 | Decreases when decreasing |
| Fragmentation | 2346 (Default) | 1500-2300 | Decreases when decreasing |
| Beacon Interval | 100 ms | 50-100 ms | Affects response time |
| DTIM Period | 1-3 | 1 | Affects clients' battery life |
Optimal values for different usage scenarios
There is no universal number that will suit everyone. Choosing a value Ready to Transmit Threshold Depends on the building density and the number of active devices. In ideal conditions (a private house in a field or a new building with thin walls and few neighbors), it's best to leave the default values.
For a typical office or dorm, where dozens of devices are simultaneously broadcasting, the default settings may not be able to handle the queues. Here, it makes sense to experiment with lowering the threshold. This will force devices to "ask permission" more frequently before transmitting, which will streamline traffic and reduce the number of retransmissions of lost data.
It's also important to consider the type of equipment. Older routers of the standard 802.11n may perform worse with aggressive fragmentation settings than modern models with support WiFi 6 (802.11ax)New standards have more sophisticated airtime management mechanisms (OFDMA), which partially take over this work.
☑️ Diagnostics before changing settings
Where to find settings on routers and adapters
The location of these settings varies greatly depending on the equipment manufacturer. Most home routers hide these settings deep within menus to prevent inexperienced users from damaging the network. They are typically found in sections related to professional or advanced Wi-Fi configuration.
In Windows, threshold settings are often accessible through the Device Manager. This allows you to fine-tune the behavior of your laptop or PC without affecting other devices on the network. However, keep in mind that if the problem is an overloaded router channel, adjusting one client will only have a partial effect.
Below are some sample paths for finding these parameters in popular equipment interfaces:
- 🔹 Keenetic: Web interface → “My networks and WiFi” → “Home network” → “Advanced settings” button (requires expert mode).
- 🔹 Mikrotik: WinBox → Wireless → Tab “Data Rates” or via the terminal command
/interface wireless set wlan1 rts-threshold=1500. - 🔹 Windows (Adapter): Device Manager → Network Adapters → Properties → Advanced Tab → Search for the lines “RTS Threshold” or “Fragmentation Threshold”.
⚠️ Attention: Firmware interfaces are updated regularly. If you don't see the above options, check for updates for your router or look for similar options in the "Advanced Settings" section.
Problem diagnosis and testing methods
Before making any changes, you need to make sure the problem is actually due to collisions and interference, and not a weak signal. To do this, use WiFi analyzer apps such as WiFi Analyzer or AirPort UtilityThey will show channel load and noise level.
Run a test by elimination. First, measure the speed and ping to a game server or popular resource using default settings. Then change the readiness threshold (for example, set it to 1500) and reboot the router. Repeat the measurements. If the ping has become more stable (less jitter) and the speed hasn't dropped dramatically, the settings are correct.
Pay attention to the behavior of IoT devices (smart light bulbs, sockets). They often operate at their limits and use outdated communication protocols. Overly aggressive router transmission threshold settings can cause the smart home to disconnect from the network, as low-end modules don't have time to complete the handshake.
For in-depth diagnostics, you can use console utilities. For example, in Linux or macOS, you can run packet monitoring via the terminal. In Windows, the command ping with continuous polling flag:
ping 8.8.8.8 -tMonitor the response time. If you see sudden spikes (timeouts) after changing the threshold settings, the value is incorrect and creating unnecessary load. Reset the settings to the default (usually 2347 bytes) and try switching to a less congested WiFi channel.
What should I do if the Internet is completely lost after the changes?
If the network stops working or becomes unavailable after changing the readiness threshold, reset the network adapter or router. On the router, this can be done either by pressing the Reset button (holding it for 10 seconds) or through the web interface if you still have access. On Windows, click the "Standard" button in the driver properties or uninstall the device from Device Manager and refresh the hardware configuration.
Does this setting affect 5GHz speed?
The 5 GHz band is less susceptible to interference from household appliances, but has lower penetration capability. The RTS/CTS mechanism works similarly here, but due to the higher transmission speeds, data travels faster, and the probability of collisions per unit of time may be lower. However, in multi-apartment buildings with dozens of 5 GHz networks, adjusting the threshold can also be useful.
Is it possible to completely disable RTS Threshold?
In fact, setting the maximum value (usually 2347) is equivalent to disabling the mechanism for standard Ethernet packets (MTU 1500). This is not recommended in very noisy areas, as it deprives the network of collision protection, relying solely on resending lost packets, which reduces the overall efficiency of the link.