In the world of wireless networks, there are many parameters that are hidden from the average user by default but can dramatically impact connection quality. One such parameter is the fragmentation threshold. Many router owners are unaware that their problems with connection drops or low speeds in noisy environments can be solved by simply adjusting this value. Fragmentation — is the process of splitting large packets of data into smaller pieces before sending them over the air.
If you notice that Wi-Fi If you seem to have a signal, but pages load intermittently or the video stream is interrupted, it's possible the packet size is the issue. Default router settings aren't always ideal for your home or office environment. In this article, we'll explore the fragmentation threshold, how it relates to noise levels, and what value is best for your network for maximum performance.
Understanding this mechanism will allow you to avoid guessing and accurately diagnose bottlenecks in data transmission. RTS/CTS and fragmentation often go hand in hand, helping to avoid collisions on the air. Let's figure out when it's worth tweaking the settings and how to do it correctly.
What is packet fragmentation in a wireless network?
Imagine you're sending a large box of things to a friend, but the road the courier has to travel is very narrow and winding. If the box is too big, it simply won't fit or will get stuck, and you'll have to re-ship it. In the world of WiFi, data is transmitted in packets. Fragmentation threshold (Fragmentation Threshold) defines the maximum size of one such packet that can be sent without splitting.
When the size of the transmitted data exceeds a set threshold, the wireless card driver or router firmware breaks the information into chunks. This is done to minimize transmission losses. If there is a lot of interference in the air, a large packet is more likely to be corrupted by noise than a small one. A corrupted packet requires retransmission, which reduces overall throughput.
Technical detail
IEEE 802.11 standard: In the 802.11 standard, the maximum frame size can reach 2346 bytes, but in real noisy environments it is more efficient to work with much smaller values in order to reduce the likelihood of collisions and retransmissions.
It's important to understand that fragmentation itself adds overhead. Each small piece of data requires its own header and delivery confirmation. Therefore, blindly reducing the fragmentation threshold on a clean channel will lead to a drop in speed. However, in a "dirty" environment, this becomes a lifesaver.
The influence of noise and interference levels on settings
The main enemy of a wireless signal is interference. Neighbors' routers, microwave ovens, Bluetooth devices, and even dimmer switches create electromagnetic noise. When noise levels are high, the likelihood that a data packet will be received with errors increases dramatically. This is where fragmentation comes into play.
If you live in an apartment building, where a single channel can contain dozens of neighboring networks, the airwaves become crowded. In such conditions, large data packets are often "broken" by interference. The WiFi protocol requires an acknowledgment of receipt of each fragment. If a fragment is lost, a retransmission request is sent. The smaller the fragment size, the higher the chance it will slip through the interference.
⚠️ Attention: Don't lower the fragmentation threshold unless absolutely necessary. If you live in a private home in the woods and have no neighbors, the default settings (usually 2346 bytes, i.e., disabled) will work faster than any manual adjustments.
You can determine if there are problems by paying attention to the number retransmissions (retransmissions) in router logs or specialized Wi-Fi analysis software. A high percentage of retransmissions is a clear sign that the current packet size is too large for the current reception conditions.
Optimal values of the fragmentation threshold
So, what fragmentation threshold is best to choose? The standard default value for most routers (TP-Link, ASUS, Keenetic, MikroTik) is 2346 Bytes. This effectively means that fragmentation is disabled, and packets are sent at the maximum possible size. This is ideal for pure Ether.
If you experience stability issues, it is recommended to gradually lower the threshold. The optimal starting value for a noisy environment is often considered to be 1500 Bytes. This value is close to the standard Ethernet MTU, which simplifies routing and reduces overhead at the interface between wired and wireless networks.
For extremely difficult conditions, where the signal barely penetrates thick walls or interference is off the charts, you can try values in the range 500-1000 Bytes. However, remember: the lower the value, the more service headers are added to the data, which reduces the useful transfer rate (throughput), even if the connection stability increases.
| Value (bytes) | Recommended scenario | Impact on speed | Impact on stability |
|---|---|---|---|
| 2346 (Default) | Clear air, private house | Maximum | Low (with noise) |
| 1500 | Apartment, moderate noise | High | Average |
| 1000 | Office, many clients | Average | High |
| 500-800 | Critical interference, long range | Low | Maximum |
Critical: The fragmentation threshold change applies to the entire network and all connected clients. Please ensure that older devices (such as older printers or IoT light bulbs) can handle the new packet size, although compatibility issues are not present in 99% of cases.
Relationship with the RTS/CTS protocol
You can't talk about fragmentation without mentioning RTS/CTS (Request to Send / Clear to Send). This is a related mechanism that is often configured in pairs. If fragmentation splits data into pieces, RTS/CTS reserves airtime before sending to avoid collisions.
The RTS threshold determines the packet size above which the device first sends a short "Can I speak?" (RTS) request. The router responds with "Yes, go ahead" (CTS), and only then does data transmission begin. This effectively combats the "hidden node" problem, where two clients cannot "hear" each other but interfere with the router.
Typically, the RTS threshold is set slightly above or equal to the fragmentation threshold. For example, if fragmentation is set to 1500, then it makes sense to set RTS to 1500 or 1600If you set the RTS too low (for example, 200 bytes), the network will be overwhelmed by service requests, and the speed will drop drastically.
Using these mechanisms together allows you to create a robust network resilient to external influences. However, like any tool, they require careful handling. Excessive fragmentation and aggressive RTS will turn your fast router into a bottleneck.
How to change settings on a router
The process for changing the fragmentation threshold may vary depending on your router model and firmware version. These settings are typically hidden in the advanced wireless network settings. Below are general instructions that apply to most popular models.
First, you need to log into the router's web interface. Open your browser and enter the address 192.168.0.1 or 192.168.1.1 (The exact address is indicated on the sticker on the bottom of the device.) Enter the administrator login and password. Next, look for the section related to wireless mode.
- 📡 For routers TP-Link: go to
Wireless→AdvancedThere you will see the fields Fragmentation Threshold And RTS Threshold. - 🛡️ For routers Keenetic: in the menu
My Networks and WiFiselect your network, clickAdditionallyand find the advanced mode settings. - 🌀 For routers ASUS: chapter
Wireless network→ tabProfessionallyLook for the options at the bottom of the list. - 🚀 For MikroTik: settings are in the menu
Wireless→ tabData Ratesor in the security profile, depending on the RouterOS version.
After changing the value, be sure to click "Save" or "Apply." The router may temporarily disconnect. If your internet connection is completely lost or the speed drops to zero after applying the settings, return the value to the default (2346 or 2347).
☑️ Checklist before changing settings
Diagnostics and testing results
How do you know if the adjustment helped? Simply looking at the signal "bars" isn't enough. You need to evaluate actual performance and stability. Use utilities to check for packet loss, such as the standard command ping.
Launch the command prompt on your computer and enter the command to continuously ping the gateway (your router) or an external resource, such as Google DNS:
ping 8.8.8.8 -tMonitor the response time (time) and timeouts. Normally, the response time should be stable. If you see sudden spikes (for example, from 5 ms to 300 ms) or "Timeout exceeded" messages, this indicates packet loss. Adjusting the fragmentation threshold should reduce the number of such spikes.
⚠️ Attention: Firmware interfaces and settings locations may change with security updates. If you don't see the Fragmentation Threshold setting, the manufacturer may have hidden it in a new firmware version. Check the official documentation for your model.
It is also useful to use specialized software like WiFi Analyzer On your smartphone, you can visually assess the channel's noise level. If, after configuring fragmentation, your download speed (throughput) drops, but your ping becomes stable, you're on the right track; this is a tradeoff for stability.
Common Mistakes When Setting Up WiFi
When trying to improve their signal, users often make common mistakes that only make matters worse. The most common is setting the fragmentation threshold to the lowest possible level "just in case." This results in the network spending up to 40% of its time on overhead, rather than transmitting your data.
Another mistake is ignoring channel selection. If you live in a building where all your neighbors are on channel 6, no amount of fragmentation will save you from constant airtime competition. In such cases, it's better to switch to a less crowded channel or use the 5 GHz band, which requires fragmentation much less frequently.
It's also worth remembering that older WiFi standards (802.11b/g) are more susceptible to interference than modern ac/ax. If you have legacy devices, they may dictate the operating conditions of the entire network, causing the router to reduce overall performance.
Does fragmentation threshold affect 5GHz speed?
In the 5 GHz band, the airwaves are generally clearer and the channels are wider. Fragmentation is less necessary here. However, if the router is located far away or behind several walls, lowering the threshold can help break through the signal, albeit at the cost of reduced maximum speed.
Do I need to change settings on all devices?
No. The fragmentation threshold is configured only on the access point (router). Client devices (laptops, phones) automatically adapt to the rules dictated by the router. Changing the settings on each phone is unnecessary and often impossible.
Can a low fragmentation threshold "kill" a router?
Physically, no. But software-wise, this will create a high load on the router's processor due to the need to process a huge number of small packets. On weaker budget models, this could lead to device freezes or reboots.
What should I do if the speed drops after setup?
Reset the fragmentation threshold value to factory default (2346). Chances are, your environment doesn't have interference issues that require packet fragmentation, and you've simply added unnecessary overhead.