Many users, trying to improve the quality of their wireless connection, sooner or later look into their router's advanced settings. There, among the many obscure abbreviations and numerical values, a parameter often appears RTS ThresholdFor the average person who simply wants a stable internet connection, this name means nothing and only makes them want to leave the settings alone to avoid making things worse. However, this very setting could be the key to resolving connection drops in busy areas.
RTS (Request To Send) is a mechanism that helps devices negotiate data transmission, preventing packet collisions. If you live in an apartment building with multiple neighboring WiFi networks per square meter, standard protocols may struggle to coordinate. In such cases, manually adjusting the RTS threshold can significantly reduce errors and increase overall channel throughput.
In this article, we'll take a detailed look at how this mechanism works, why it's often disabled or set to its maximum value by default, and in what situations changing this parameter is truly necessary. You'll learn how to select the correct value for your equipment and avoid common mistakes that, instead of improving it, can completely cripple your network.
How the RTS/CTS mechanism works
To understand the essence RTS Threshold, you need to understand the basic protocol for device interaction. The 802.11 standard uses the CSMA/CA method, which assumes that a device first "listens" to the air. If the channel is clear, it begins transmitting. A problem arises when two devices begin talking at the same time—a collision occurs, data is lost, and it must be retransmitted.
The RTS/CTS (Request To Send / Clear To Send) mechanism was developed as a solution to the "hidden node" problem. Imagine this: your laptop can't "hear" your neighbor's router, but they're both on the same channel. The laptop thinks the airwaves are clear and begins transmitting, while the neighbor's router also decides to send data. As a result, signals collide at the access point (your router).
The exchange process is as follows:
- 📡 The client device sends a short RTS (Request to Send) service frame to the router.
- 📡 The router, if the channel is free, sends a CTS (Clear to Send) frame to all devices within range.
- 📡 All devices that receive CTS go silent while transmitting data, ensuring silence on the air.
- 📡 The client receives confirmation and begins transmitting the main data packet.
This is where the parameter comes into effect RTS ThresholdThis is the packet size threshold in bytes. If the size of the transmitted data packet is less than the set threshold, the RTS/CTS mechanism is not used—the device proceeds directly to transmission, saving time on overhead communication. If the packet is larger than the threshold, the handshake described above is initiated.
⚠️ Attention: The RTS/CTS mechanism creates additional network overhead. Using it for every small packet (for example, when sending messages in instant messaging apps) will significantly reduce the actual speed, as the payload will be drowned out by the overhead requests.
Default parameter value and its impact
In most modern routers, whether Keenetic, TP-Link or Asus, the default RTS Threshold value is set to 2346 bytes (or 2347). This is the maximum value, which effectively disables the mechanism for standard data packets. Why do manufacturers choose this strategy?
The fact is that under ideal conditions, when interference is minimal, the overhead of RTS/CTS is detrimental. Every small file and every delivery confirmation (ACK) takes time. If the airwaves are clear, it's easier to send data immediately and receive confirmation than to waste time on lengthy negotiations. Therefore, for most home users, changing this parameter will have no positive effect and may even worsen the situation.
However, if you experience the following symptoms, the default settings may not work:
- 📉 Sharp drops in speed during rush hour (in the evening, when neighbors are also online).
- 📉 Frequent connection interruptions when downloading large files.
- 📉 High level of packet retransmissions (can be seen in logs or special utilities).
In such cases, lowering the RTS threshold forces devices to "negotiate" more frequently. It's like a traffic controller at an intersection: he slows traffic when there are few cars, but prevents a complete gridlock when the traffic is heavy.
When to change the RTS Threshold
The main task of the network administrator is to find a balance. Reducing the value RTS Threshold It only makes sense in conditions of high competition for airtime. If you live in the center of a large city, in a dorm, or in an office where there are dozens of active clients per access point, the standard 2346 bytes may be too much.
Let's look at typical scenarios when intervention is necessary:
- Oversaturated ether. The scanner shows 15-20 neighboring networks on channel 6. Devices are constantly trying to break through, and collisions occur.
- The "Hidden Node" problem. Clients are far apart and cannot hear each other's signals, but their signals intersect at the access point.
- Prioritize stability over speed. For VoIP telephony or online gaming, the absence of packet loss (lag) is more important than the maximum theoretical throughput.
If you live in a private house where, besides your router, only one other network is caught at the limit of hearing, touch this parameter strongly not recommendedYou'll only add latency without any benefit to stability.
It's also worth considering the type of traffic. When transferring large files (movies, backups), large packets are effective. When working with databases or game servers, small packets are needed, and here RTS can play a nasty trick if the threshold is set incorrectly.
How to choose the optimal value
Finding the ideal value is an empirical process, dependent on the specific environment. There's no one-size-fits-all figure. Typically, people start by gradually decreasing the value from the maximum (2346) to the minimum (often 0 or 256, depending on the firmware).
Recommended course of action:
- 🔧 Record your current speed and ping using Speedtest or PingPlotter.
- 🔧 Set the value
2000Byte. Test the network for 15-20 minutes of active operation. - 🔧 If there is no improvement, reduce to
1500, then to1000. - 🔧 The optimal range is often considered to be between
500And1000byte for very "noisy" apartments.
It's important to understand that a value of 0 or 1 typically means RTS is used for all packets of any size. This is an extreme measure. In most cases, the "sweet spot" is a value of around 1500 bytes, as the standard Ethernet MTU is 1500 bytes. This allows large packets to pass through the handshake, and small service packets to skip through without delay.
⚠️ Attention: Router interfaces may vary. In some models (for example, older D-Link or TP-Link models), the slider may be non-linear, while in OpenWRT firmware, the value is manually set using numbers. Always consult the documentation for your specific model.
What is Fragmentation Threshold?
Fragmentation Threshold is a related parameter that breaks large packets into smaller fragments before sending. It is often configured in conjunction with the RTS Threshold. While RTS controls "when to speak," Fragmentation controls "in what chunks to speak." Lowering this threshold also helps in noisy environments, but it puts more strain on the router's processor.
Instructions for setting up on different routers
The process for changing settings may vary depending on the hardware manufacturer and firmware version. Below are general settings paths for popular brands. Please note that accessing these menus may require administrator privileges.
First, you need to access the router's web interface. This is usually done through a browser at 192.168.0.1 or 192.168.1.1Enter the login and password indicated on the sticker on the bottom of the device.
Typical ways to configure RTS Threshold:
- TP-Link: Wireless → Wireless Settings → Advanced → RTS Threshold.
- Asus (AsusWRT): Wireless Network → Advanced → Advanced Tab → RTS Threshold.
- Keenetic (KeeneticOS): My Networks and WiFi → Home Network → Advanced → RTS Threshold.
- MikroTik: Wireless → Interface → Advanced Mode → RTS Threshold (requires knowledge of CLI or deep diving into WinBox).
After changing the value, be sure to click "Save" or "Apply." In some cases, the router may reboot the wireless module, causing connections to be lost for a few seconds.
If network performance deteriorates or devices stop connecting after making these changes, return the value to its original state (2346). In extreme cases, a full reset of the router to factory settings using the button will help. Reset on the body.
Comparison with other optimization parameters
RTS Threshold isn't the only setting that affects stability. Users often try to solve interference issues with this setting alone, ignoring more important factors. Let's compare the effectiveness of various methods.
| Parameter | Impact on speed | Impact on stability | Difficulty of setup |
|---|---|---|---|
| Channel selection | High | Critical | Low |
| Channel width | High | Average | Low |
| RTS Threshold | Medium/Low | High (in noisy air) | High |
| Signal strength | Low | Average | Low |
As the table shows, the first step is choosing a free channel and channel width (20 MHz vs. 40/80 MHz). Reducing the channel width to 20 MHz in the 2.4 GHz band often yields a greater stability boost than any RTS manipulation.
Parameter RTS Threshold It should be considered "fine-tuning" when the main parameters have already been optimized, but problems persist. This is a tool for advanced users who have exhausted the basic methods.
Possible problems and their solutions
Incorrectly setting the RTS Threshold can lead to paradoxical results. Instead of improving the connection, you may experience complete network failure or extremely low speeds. This occurs because devices spend 90% of their time on service requests and transmit almost no useful data.
Typical symptoms of improper settings:
- 📉 Download speed dropped to tens of kilobits per second.
- 📉 Ping delay increased to 500-1000 ms.
- 📉 Old devices (such as IoT light bulbs or old smartphones) no longer see the network.
If you encounter this, the solution is simple: reset your wireless settings to factory defaults. Don't try to guess the value without monitoring the network status. It's also worth checking that WMM (Wi-Fi Multimedia) mode isn't enabled, as it can conflict with aggressive RTS settings on some chipsets.
⚠️ Attention: Some router firmware may have bugs in its RTS implementation. If the router starts overheating or rebooting after enabling this feature, this is a software error. In this case, it's best to leave this setting alone or update the firmware to the latest version.
Frequently Asked Questions (FAQ)
Can changing the RTS Threshold increase the maximum WiFi speed?
No, it can't. This parameter only affects connection stability and the number of packet retransmissions. The theoretical speed limit is determined by the WiFi standard (n, ac, ax) and the channel bandwidth. At best, you'll regain the speed lost due to errors, but you won't be able to exceed the standard.
Does RTS Threshold affect online gaming performance?
Yes, it can. If the value is chosen correctly for your noisy environment, the ping will become more stable and jitter will disappear. However, if the value is set too low, the ping will increase due to the overhead of service frames.
Should Fragmentation Threshold be changed along with RTS?
These parameters are often adjusted in tandem. If you've lowered the RTS, it's worth experimenting with the Fragmentation Threshold, setting it close to the RTS value. However, it's always best to start with the RTS.
Does this work on the 5GHz band?
Yes, the mechanism also works on the 5 GHz band. However, this range typically has less interference from neighboring devices (due to greater signal attenuation and a larger number of channels), so manual tuning is less necessary than on the 2.4 GHz band.
Will the setting be reset after updating the firmware?
In most cases, the settings are preserved. However, if the update is a major one (changing the firmware version, for example, from 3.x to 4.x), the router may reset all parameters to factory defaults. It is recommended to check the settings after any update.