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 speeds are stuck in the single digits. Even on a fast fiber connection, the experience feels sluggish. Web pages hang, and file transfers take ages. Many users blame the drivers. But the cause is often more basic: the radio band you are connected to.

Modern WiFi hardware is very capable. But old networking setups often hold it back. Most routers today broadcast on two main bands: 2.4GHz and 5GHz, and more and more on 6GHz. The 2.4GHz band has better range and gets through walls well. It is also very crowded. Every neighbor’s router, your Bluetooth mouse, and even your microwave use this same space. That congestion leads to packet loss and big speed drops, no matter how fast your internet plan is.

Step 1: Identifying the Bottleneck

One of the first signs is “link rate” deception. Your system might report a speed of 130 Mbps or higher. But a real throughput test shows you only get a fraction of that. The gap 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. A channel number between 1 and 13 means you are on the 2.4GHz band. If the “Rate” looks high (say, 130 Mbit/s) but your real speed is slow, interference is the likely cause.

Step 2: Testing Real-World Throughput

Next, confirm 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

High “Retr” (Retransmissions) and low “Bitrate” confirm the problem. Interference or congestion is choking your WiFi signal before it even reaches the internet.

Step 3: Moving Beyond Signal Strength

On Linux, NetworkManager often prefers the strongest signal by default. Since 2.4GHz signals travel further, your laptop might lock onto the slower 2.4GHz band. It does this even when 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 twice: once on a low channel for 2.4GHz, and once on a high channel like 36, 44, or 149 for 5GHz. The 5GHz signal will almost always be faster, even when its “Signal” percentage is lower than the 2.4GHz one.

Step 4: Forcing the Faster 5GHz Band

The best fix is to lock your connection profile onto the 5GHz band. You can tell NetworkManager to use only the “A” band, which covers 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 this, your laptop ignores the 2.4GHz signal for that network. Your data moves onto a much wider, less crowded highway.

Step 5: Checking for Driver Throttling

Beyond band steering, it is also worth checking driver power management. Many modern Intel WiFi cards turn on aggressive power-saving features 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 on and causing latency spikes, turn it off for a moment to see if stability improves:

sudo iw dev wlp0s20f3 set power_save off

Driver quirks that hurt hardware performance are a recurring theme on Linux. If you hit similar issues with display output, the same diagnostic mindset applies to fixing Wayland screen tearing .

Conclusion: Tuning for Performance

Slow WiFi on Linux is rarely just a “bad driver.” It works much like slow Linux boot times , which trace back to blocking services rather than faulty hardware. The real cause is usually the tangled mix of hardware, firmware, and radio interference. Once you know the difference between the 2.4GHz and 5GHz bands, you can set your system to prefer the faster one. A few minutes of command-line tuning is often all it takes to turn a slow connection into a fast one.