How to Get an 866 Mbps 5 GHz Wi-Fi Link on Linux
Getting a fast and stable Wi-Fi connection on Linux does not always require complicated driver modifications or custom kernel parameters.
If your laptop has a modern 2Γ2 wireless adapter and your router or mobile hotspot supports 802.11ac, you can often achieve a Wi-Fi link speed of 866.7 Mbps by using the 5 GHz band with an 80 MHz channel.
This guide explains how to check and optimize a Linux Wi-Fi connection using standard tools such as `iw` and NetworkManager.
The commands are designed to be broadly applicable to RPM-based Linux distributions, including Fedora, RHEL, AlmaLinux, Rocky Linux, CentOS Stream, and Oracle Linux.
Test Environment
In this example, the Linux laptop is connected to a 5 GHz mobile hotspot provided by an Android smartphone. The phone acts as the Wi-Fi access point, while Linux operates as the Wi-Fi client.
The actual connection used for this test achieved:
How to Optimize 5 GHz Wi-Fi on Linux for an 866 Mbps Link Speed
Getting a fast and stable Wi-Fi connection on Linux does not always require complicated driver modifications or custom kernel parameters.
If your laptop has a modern 2Γ2 wireless adapter and your router or mobile hotspot supports 802.11ac, you can often achieve a Wi-Fi link speed of 866.7 Mbps by using the 5 GHz band with an 80 MHz channel.This guide explains how to check and optimize a Linux Wi-Fi connection using standard tools such as `iw` and NetworkManager.
The commands are designed to be broadly applicable to RPM-based Linux distributions, including:
- Fedora
- RHEL
- AlmaLinux
- Rocky Linux
- CentOS Stream
- Oracle Linux
The exact wireless interface name and available Wi-Fi features will vary between systems, but the basic troubleshooting process is largely the same.
What Does 866 Mbps Actually Mean?
Before changing anything, it is important to understand what Linux is reporting when it shows:
This is the Wi-Fi link rate, not the actual Internet download speed.A typical 866 Mbps connection might look like this:
After accounting for Wi-Fi protocol overhead, encryption, TCP/IP overhead, retransmissions, acknowledgements, and other factors, the actual network throughput will normally be lower.
For example, an 866 Mbps Wi-Fi link might produce several hundred megabits per second of actual TCP throughput.
Therefore, seeing 866.7 Mbps in `iw` is already a very good result.
1. Check Your Wireless Network Interface
Start by checking the network devices detected by NetworkManager:
You may see something similar to:
The wireless interface in this example is:
Your interface may have a different name.
Modern Linux distributions normally use predictable network interface names such as:
Do not assume that your wireless interface is called `wlan0`.
You can also use:
For example:
The interface listed after `Interface` is the name you should use with `iw`.
2. Check the Current Wi-Fi Connection
The most useful command for troubleshooting the actual Wi-Fi link is:
Replace `wlp0s20f3` with your own wireless interface.
A healthy 5 GHz 866 Mbps connection may look like:
Several important pieces of information are contained in this output.
3. Confirm That You Are Using the 5 GHz Band
Look at the `freq` value:
This means the wireless connection is operating at 5200 MHz, which is part of the 5 GHz Wi-Fi band.A 2.4 GHz connection would normally show frequencies around:
A 5 GHz connection may show values such as:
There is no requirement to use exactly 5805 MHz to achieve 866 Mbps.
For example:
can provide the same 866 Mbps class of link as another suitable 5 GHz channel when the other conditions are identical.
The important factors are the channel width, number of spatial streams, modulation, signal quality, and capabilities of both devices.
4. Check the Channel Width
One of the most important values is:
For example:
The `80MHz` portion means that the connection is currently using an 80 MHz channel width.For a typical 2Γ2 802.11ac connection, 80 MHz is an important part of reaching an 866 Mbps link rate.
If the connection falls back to:
or:
the maximum link rate can be significantly lower.
This is one of the first things to check when a supposedly fast 802.11ac adapter is only connecting at a few hundred megabits per second.
5. Understand VHT-MCS 9
You may see:
in the `iw` output.
VHT stands for Very High Throughput, which is associated with 802.11ac. MCS means Modulation and Coding Scheme.The MCS value describes the modulation and coding combination being used by the wireless link.
For a typical 2Γ2 802.11ac connection using 80 MHz, MCS 9 represents one of the highest link-rate configurations available for that combination.
That is why a connection such as:
can show:
6. Understand VHT-NSS 2
Another important part of the output is:
NSS means Number of Spatial Streams.`VHT-NSS 2` means the connection is using two spatial streams.
In practical terms, this corresponds to a typical:
wireless configuration.
This is important because an 802.11ac adapter that only has one spatial stream cannot reach the same maximum link rate as a 2Γ2 adapter under the same channel conditions.
Therefore, an 866 Mbps connection is commonly associated with:
7. Check Signal Strength
The same `iw` command also reports signal strength:
For example:
A rough guide is:
| Signal | General Condition |
| -------------- | ----------------- |
| -30 to -50 dBm | Excellent |
| -50 to -60 dBm | Very good |
| -60 to -67 dBm | Good |
| -67 to -70 dBm | Fair |
| Below -70 dBm | Weak |
A value around:
is excellent for a typical indoor Wi-Fi connection.
Strong signal does not guarantee maximum performance by itself, but it gives the wireless adapter a much better chance of maintaining a high modulation rate.
8. Why 5 GHz Is Usually Better for High-Speed Wi-Fi
The 2.4 GHz band has better range and generally penetrates walls more effectively.
However, it is also more crowded.
Bluetooth devices, wireless peripherals, neighboring routers, IoT devices, and many other systems may use the 2.4 GHz band.
The 5 GHz band provides access to wider channels and is generally a better choice when the priority is high Wi-Fi throughput.
For an 866 Mbps 802.11ac connection, the preferred configuration is usually:
The trade-off is that 5 GHz normally has a shorter practical range than 2.4 GHz.
9. Configure NetworkManager to Prefer 5 GHz
Most modern RPM-based desktop Linux distributions use NetworkManager.
First, check the saved connections:
For example:
The connection name in this example is:
You can configure this connection to use the 5 GHz band:
Here:
selects the 5 GHz Wi-Fi band.
After changing the setting, reconnect:
Then check the result:
10. Do Not Force 5805 MHz Just Because You Want 5.8 GHz
It is tempting to think that a 5 GHz connection must use a frequency around 5800 MHz.
That is not how Wi-Fi performance works.
For example, these are all 5 GHz frequencies:
A connection at:
can achieve an 866 Mbps link rate just as a suitable higher 5 GHz channel can.
There is generally no advantage in forcing 5805 MHz simply because it looks more like "5.8 GHz."
In most cases, it is better to allow the access point and wireless adapter to select an appropriate channel.
11. Check What Your Wireless Adapter Supports
Use:
This displays the capabilities reported by the wireless driver.
The output can be very long.
You can search for VHT capabilities:
You can also look for supported frequencies:
Depending on the wireless adapter and driver, you may see information related to:
Modern adapters may support much newer standards than 802.11ac.
For example:
- 802.11ac = Wi-Fi 5
- 802.11ax = Wi-Fi 6 / 6E
- 802.11be = Wi-Fi 7
If your adapter supports Wi-Fi 6 or Wi-Fi 7, its maximum link rate may be substantially higher than 866 Mbps.
12. Check the Available Wi-Fi Networks
NetworkManager can show nearby access points:
You may see:
The channel number can help you determine which part of the 5 GHz spectrum is being used.
For example:
corresponds to:
The available channels depend on your regulatory domain, access point configuration, hardware, and local regulations.
13. Make Sure the Access Point Supports 80 MHz
The laptop cannot create an 80 MHz Wi-Fi connection by itself.
The access point must support it as well.
For a typical 802.11ac setup, check the router or hotspot configuration and look for settings such as:
The exact names vary between routers.
Some devices may call the setting:
If the access point is configured for only 20 MHz or 40 MHz, the Linux laptop cannot simply force it to become an 80 MHz connection.
14. Mobile Hotspots Can Also Reach 866 Mbps
A phone hotspot can sometimes provide the same type of connection as a traditional wireless router.
For example, a modern smartphone may advertise:
When a compatible Linux laptop connects to it, `iw` may report:
This means the Wi-Fi link between the laptop and phone is operating at 866 Mbps.
However, the actual Internet speed is still limited by the phone's cellular connection.
In other words:
The Wi-Fi link can be much faster than the cellular connection.
15. Test Internet Latency Separately
Wi-Fi link speed and Internet latency are different measurements.
For example:
A result such as:
indicates the network path has relatively low latency.
You should look at:
For example:
That would indicate:
which is a very good result for many Internet connections.
16. Wi-Fi Link Speed Is Not Internet Speed
This distinction is worth repeating because it causes a lot of confusion.
Suppose Linux reports:
but an Internet speed test reports:
That does not automatically mean the Wi-Fi is broken.
The Internet connection might be limited by:
- Cellular network performance
- ISP bandwidth
- Router uplink
- VPN overhead
- Server location
- Server capacity
- TCP behavior
- Network congestion
- Cloudflare or CDN routing
The 866 Mbps figure only describes the negotiated wireless link between the laptop and the access point.
17. Use iperf3 to Measure Actual Wi-Fi Throughput
If you want to test the Wi-Fi connection itself rather than the Internet connection, `iperf3` is a much better tool.
On Fedora, AlmaLinux, Rocky Linux, RHEL-compatible systems, or other RPM-based distributions, try:
If the package is available through your enabled repositories, it will be installed normally.
On another computer connected to the same network, run:
Find the other computer's IP address.
For example:
Then run the client on the Linux laptop:
You can now measure the actual TCP throughput between the two devices.
18. Why 866 Mbps Link Rate May Produce Only 500β700 Mbps
This is normal.
Wi-Fi is not a simple Ethernet connection.
There is protocol overhead caused by:
- Wireless framing
- MAC headers
- Encryption
- Acknowledgements
- Retransmissions
- Channel contention
- TCP/IP overhead
- Operating system networking
- Driver processing
Therefore:
does not normally translate into:
A real throughput result in the range of several hundred megabits per second can be completely normal.
The exact result depends on the hardware and test conditions.
19. What If the Link Rate Is Only 433 Mbps?
Suppose you run:
and get:
First look at the channel width.
If you see:
the connection may not be using the 80 MHz configuration required for an 866 Mbps-class 2Γ2 802.11ac link.
Check the access point configuration.
Make sure the 5 GHz network is configured for an appropriate channel width, such as:
Then reconnect and check again.
20. What If the Link Rate Is Only 173 Mbps?
A much lower result such as:
means that something is limiting the negotiated link.
Check:
Look at:
Possible causes include:
- Weak signal
- 20 MHz channel width
- One spatial stream
- Interference
- Access point limitations
- Driver limitations
- Power-saving behavior
- Poor antenna conditions
- Regulatory restrictions
Do not immediately change kernel parameters.
First determine what the wireless link is actually negotiating.
21. Avoid Blindly Changing Driver Parameters
Linux Wi-Fi drivers often expose many parameters.
You may find online recommendations to:
- Disable power saving
- Force a particular MCS
- Force a specific channel
- Change regulatory settings
- Increase transmit power
- Modify driver options
- Disable roaming
- Change kernel module parameters
These changes are not universally beneficial.
A configuration that works for one Intel, MediaTek, Realtek, or Qualcomm adapter may be completely inappropriate for another.
If the system is already reporting:
there is usually no reason to start modifying driver parameters.
22. Do Not Randomly Change the Regulatory Domain
You may also find instructions recommending commands such as:
Do not change the regulatory domain simply to unlock more channels or increase transmit power.
Wi-Fi frequencies and transmit power are regulated differently in different countries and regions.
The correct regulatory configuration should normally be determined by the operating system, firmware, hardware, and local configuration.
Trying to force an unsupported regulatory configuration can create both technical and regulatory problems.
23. Keep the Laptop Close to the Access Point When Testing
If you are trying to determine the maximum possible Wi-Fi performance, perform the initial test relatively close to the router or hotspot.
For example:
This reduces the chance that signal strength is the limiting factor.
Once you confirm that the connection can reach:
you can move farther away and observe how the rate changes.
You may see something like:
The exact thresholds depend on the hardware and environment.
24. A Simple Wi-Fi Troubleshooting Workflow
When a Linux laptop is not reaching the expected Wi-Fi speed, use the following sequence.
Step 1: Find the wireless interface
Step 2: Inspect the wireless device
Step 3: Check the current connection
Step 4: Check the frequency
Look for:
Step 5: Check the channel width
Look for:
Step 6: Check MCS
Look for something such as:
Step 7: Check spatial streams
Look for:
Step 8: Check signal strength
Look for:
Step 9: Check NetworkManager
Step 10: Test real throughput
Use:
This workflow is usually much more useful than randomly changing wireless driver parameters.
25. A Good 866 Mbps Configuration
For a typical 2Γ2 802.11ac device, an ideal configuration looks like:
The `iw` output might look like:
This is an excellent result for a 2Γ2 802.11ac connection.
26. Useful Commands at a Glance
Find network interfaces:
Find wireless interfaces:
Check current Wi-Fi connection:
Show nearby Wi-Fi networks:
Show saved NetworkManager connections:
Prefer the 5 GHz band:
Reconnect:
Show wireless capabilities:
Install `iperf3` on an RPM-based system:
Run an `iperf3` server:
Run an `iperf3` client:
Conclusion
A fast Linux Wi-Fi connection does not necessarily require complicated system modifications.
For a typical 2Γ2 802.11ac adapter, the most important combination is:
When these conditions are met, Linux can report a link rate of approximately:
The most useful command for checking the final result is:
A result such as:
means that the wireless adapter has successfully negotiated an excellent 2Γ2 802.11ac connection.
The important point is that 866 Mbps is a Wi-Fi link rate, not guaranteed Internet throughput. If you want to measure the actual performance of the wireless network, use `iperf3` between two devices on the same LAN.For RPM-based Linux systems, the combination of:
provides a simple and portable toolkit for diagnosing and optimizing high-speed Wi-Fi without depending on a specific laptop model, router brand, or wireless chipset.
Explore More
βΊ Firefox vs Chrome on Linux: Why Firefox Remains the Default Choice
βΊ Building a Linux Command Search Tool with Java Swing
βΊ How to Stream Linux Command Output to a Swing JTextArea with ANSI Colors