Skip to main content

Chasing a Wifi Ghost

For quite a while, I have not been so confused (and excited) by a technical issue.

The problem is: I got very slow download speed (~10Mbps) on my Windows laptop, when connected to Wifi.

To make it a bit more puzzling:

- The upload speed is much better (~60Mbps).

- Sometimes the download speed may reach ~100Mbps for a few seconds, before quickly fall back to ~10Mbps.

Having been suffering from it for a few months, I finally decide to take on this issue today.


Beginning of the Journey

As usual, there are some troubleshooting routine I should do. Also as usual, they don't help much.

- Try other devices with the same Wifi
- Try to connect to other Wifi
- Try to connect to Ethernet
- Reset the Wifi router
- Run Windows troubleshooter

Well, eventually I did get some information. The download & upload speed is actually normal for all my other devices, which includes Android/iOS phones, MacBook Pro etc. 

This pieced of info narrowd the root cause down to the laptop itself: The router must be working well, and I'm not throttle by my ISP.


The Chase1: Killer

My machine has a Killer wifi card, which had some issues before. At the beginning, I try to examine all Killer componenets thoroughly:

- Try the latest Wifi driver
- Try some older Wifi drivers
- Install / Uninstall Killer software & services

Not surprisingly, nothing worked.

The Chase2: Windows

Next, I tried to exhaust my knowledge about Windows networking,  in order to examine all relevant aspects:
- run sfc /scannow
- Reset TCP settings
- Reset network stack (run ipconfig, netsh etc.)
- Disable SmartByte service (which is actually not available on my machine)
- Disable WMM/QoS (which is actually not available for my router)
- Disable power saving move for the adapter
- Altering Wireless mode (802.11) of the adapter
- Disable network discover
- Disable firewall
- Remove custom DNS servers
- Disable features (e.g. ipv6) of the adapter
- Disable other network adapters
- Disable bluetooth
- Disable Windows TCP autotuning
- Dissable WAN miniport

Again. Nothing worked.

The Ghost

After reading the Killer troubleshooting pages for a few times (one, two), I finally noticed an instruction, to set the "channel width" to 20MHz. This is relevant since I'm using a 5GHz Wifi.

Having absolutely no expection, I changed the settings in the router, and that's how I captured the ghost.
Now I have ~100Mbps download speed, finally. Still not as fast as the Ehternet, but good enough.

Summary

Previously the router had been configured to use choose from 20/40/80MHz automatically. The router has been using 80MHz according to my Wifi scanner. If I understand correctly, changing to 20MHz helps because there are many other Wifi signals "nearby": both "physically close" and "similar channel frequencies). This probably can also explain why the download speed was unstable.

It is yet unsolved why my Killer wifi card is not able to handle the broader width, while others can.

Anyway, I'm happy to meet this new cute ghost, and keep it with its friends together.

Comments

Popular posts from this blog

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...

Installing Linux on Surface Pro 1g

Windows 10 will soon reach its end of life, and my 1-gen Surface Pro is not supported by Windows 11. I (finally) decided to install Linux to it. Fortunately, it's a not-so-easy nice adventure: The device has only one USB port, so I have to bring back my 10+-year old USB hub. My live USB drive cannot boot directly, I have to disable Secure Boot first, by holding Volume Up during boot. I think years ago I learned that booting on USB might not work through a USB hub, but fortunatelly it worked well with my setup. This is done by holding Volume Down during boot. Wifi adapter was detected in the live Linux environment, but not functional. And I don't have a USB-Ethernet adapter. Luckily, nowadays we have USB-tethering from Android phones, which works out-of-the-box. Originally I planned to following this guide to set up root on ZFS, however, the system froze when building the ZFS kernel module. Then I decided to just use EXT4, yet I still learned a lot from the guide about disk par...

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...