Solving Slow WiFi on Linux: Moving Beyond the 2.4GHz Bottleneck

It’s a common frustration: you have a high-end Linux laptop with a cutting-edge WiFi card, yet your actual internet speeds are stuck in the single digits. Even on a 100 Mbps or faster fiber connection, the experience can feel sluggish, with web pages hanging and file transfers taking ages. When this happens, many users immediately blame the drivers, but the culprit is often much more fundamental: the physical radio band you are connected to.

Modern WiFi hardware is incredibly capable, but it is often held back by legacy networking environments. Most routers today broadcast on two main frequencies: 2.4GHz and 5GHz (and increasingly 6GHz). While 2.4GHz has better range and can penetrate walls more effectively, it is also extremely crowded. Every neighbor’s router, your Bluetooth mouse, and even your microwave operate in this same space. This congestion leads to packet loss and significant speed drops, regardless of how fast your internet service is.

Step 1: Identifying the Bottleneck

One of the first signs of this issue is “link rate” deception. Your system might report a connection speed of 130 Mbps or higher, but a real-world throughput test reveals you’re only getting a fraction of that. This discrepancy is usually caused by interference and retransmissions.

To check your current connection details, use nmcli:

nmcli -f IN-USE,SSID,BSSID,CHAN,SIGNAL,RATE dev wifi list

Look for the asterisk (*) next to your current connection. If you see a channel number between 1 and 13, you are on the 2.4GHz band. If you see a “Rate” that looks high (e.g., 130 Mbit/s) but your actual speed is slow, you are likely suffering from interference.

Step 2: Testing Real-World Throughput

To confirm that the issue is local (between your laptop and the router) and not your internet provider, use iperf3 to test the speed to another device on your local network:

# On your laptop (as client)
iperf3 -c [IP_OF_ANOTHER_LOCAL_HOST] -t 10

If the results show high “Retr” (Retransmissions) and low “Bitrate,” it confirms that your WiFi signal is being “choked” by interference or congestion before it even reaches the internet.

Step 3: Moving Beyond Signal Strength

On Linux, the default behavior of NetworkManager is often to prefer the strongest signal. Since 2.4GHz signals travel further, your laptop might automatically “handshake” with the slower 2.4GHz band even if a much faster 5GHz signal is available.

To see which bands are available for your current network, scan the environment:

nmcli dev wifi list | grep [YOUR_SSID_NAME]

You will often see the same SSID appearing twice: once on a low channel (2.4GHz) and once on a high channel (like 36, 44, or 149 for 5GHz). If the 5GHz signal is available, even if the “Signal” percentage is lower than the 2.4GHz one, it will almost always be faster.

Step 4: Forcing the Faster 5GHz Band

The most effective way to solve this is to force your connection profile to prioritize or lock onto the 5GHz band. You can tell NetworkManager to only use the “A” band (which includes 5GHz and 6GHz):

# Replace 'MyNetworkName' with your actual connection name
sudo nmcli connection modify "MyNetworkName" 802-11-wireless.band a
sudo nmcli connection up "MyNetworkName"

After running this, your laptop will ignore the 2.4GHz signal entirely for that specific network, moving your data onto a much wider, less-congested highway.

Step 5: Checking for Driver Throttling

Beyond band steering, it is also worth checking for driver-specific power management. Many modern Intel WiFi cards have aggressive power-saving features enabled by default on Linux. To see if power saving is active on your wireless interface:

# Replace wlp0s20f3 with your actual interface name from 'ip link'
nmcli dev show wlp0s20f3 | grep -i state
# Or check the kernel module directly
grep . /sys/module/iwlwifi/parameters/power_save

If power saving is active and causing latency spikes, you can temporarily disable it to see if it improves stability:

sudo iw dev wlp0s20f3 set power_save off

Conclusion: Tuning for Performance

In conclusion, slow WiFi on Linux is rarely just a “bad driver.” It is usually a symptom of the complex dance between hardware, firmware, and radio interference. By understanding the difference between the 2.4GHz and 5GHz bands and learning how to configure your system to prefer the latter, you can unlock the true potential of your hardware. A few minutes of command-line tuning is often all it takes to turn a frustratingly slow connection into a high-speed workstation.