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.
Labels:

Comments

Post a Comment

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

GameConqueror 0.09 -- Linux Game Hacking Tool

If you are a game hacker If you've been looking for a `CheatEngine for Linux` Then you can't miss this. ============================================== GameConqueror is a game hacking tool for linux, it's written in PyGTK and uses scanmem as its backend. It's supposed to be with most useful features of CheatEngine for Linux. Currently, I've implemented almost everything about scanning, involving variant data types and scan types: Data Types: int{8/16/32/64}, float{32/64}, unknown type(int or float) and unknown width(will try each of them), byte array and string Scan Types: equal, greater, less, changed, unchanged, increased(by), decreased(by) This should be enough for most cases, so I decided to release it at the current status. ============================================= Here's how you can get it PPA (for Ubuntu users) https://launchpad.net/~coolwanglu/+archive/scanmem (I've not test it in 32bit environments or Jaunty, do please inform me if it doe...
Post a Comment
Read More »

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...
Post a Comment
Read More »