Skip to main content

My Wireless Sucks!

The WiFi at my house has been somewhat slow and unreliable lately, so I decided to look into it. I did a lot of experiments with Speakeasy's Speed Test. I also upgraded my wireless access point from a Linksys WRT54GL to a ASUS RT-AC56U, although that wasn't strictly necessary. I fixed it to the point where my DSL connection is once again my bottleneck. Here's what I learned.

First of all, the "wireless neighborhood" I live in is very different these days than when I first setup my wireless access point. When I first set it up, I only had 1-2 devices connected to it, and there were no other wireless access points in the neighborhood. These days, I have 3 wireless devices connected to my TV, 7 Nexus 7s, 2 laptops, 2 phones, and a Rasberry Pi all connected to the same access point. Furthermore, there are 5-7 wireless access points in my neighborhood (which is still low compared to some neighborhoods). Since wireless bandwidth is a shared resource, I'm sure there's quite a lot of contention these days.

Another thing I noticed is that a lot of the APs were using channel 6. Simply switching to channel 11 made my wireless stop sucking. My guess is that newer APs are better at picking the best channel than older APs are, but I don't know that for certain.

Furthermore, I suspect that my Linksys WRT54GL was dying. Since I have a 100 year old house, devices tend to die from time to time. Hence, I've had to buy a couple Linksys APs over the years. Sometimes doing a factory reset and then reconfiguring it is enough to fix the problem. However, this time, even though I could log into the device, when I tried to do a factory reset, it didn't work. I wonder if that could possibly do with old flash memory.

Here's another trick. My buddy at work, Chris Dudte, pointed out that almost everyone has 2.4Ghz devices and APs these days, whereas very few people use 5Ghz, even though the 802.11a standard has been around forever. If you're confused by the different frequencies and the different 802.11 wireless standards (as I was), check out this useful overview. I was able to setup a 5Ghz network for my wife and I (since we have laptops and phones that support 5Ghz), whereas the kids are on a 2.4Ghz network (since their Nexus 7s don't support 5Ghz).

As I mentioned, I upgraded my wireless access point and router from a Linksys WRT54GL to an ASUS RT-AC56U. The guy at work who's in charge of wireless gave me a thumbs up when I told him that, so I assume it was the right decision. Although I was able to fix my problems with the Linksys WRT54GL simply by changing channels, I'm excited about the ASUS RT-AC56U for a few reasons. My favorite feature is that I can use one device to run a 5Ghz protected network, a 2.4Ghz protected network, and a completely open, but segregated guest network. Previously, I was only using a 2.4Ghz completely open network (because I'm a fan of open networks). It's nice to be able to continue to provide an open network, while segregating and protecting the rest of my house. There are a ton of other features as well, such as the ability to plug in USB hard drives and USB printers, but I haven't tried any of those features yet. I'm also excited to try the new 802.11ac wireless standard that it supports, but I don't have any other devices that support it yet.

Since DSL is still the bottleneck, you might wonder why faster wireless speeds matter. When all of your devices only talk to the internet and rarely talk to each other, it probably doesn't matter. However, once in a while, I need to transfer things from one laptop to another. With the Linksys WRT54GL, transferring files between laptops over wireless was ridiculously slow. With the ASUS RT-AC56U, it's much better. Of course, I prefer to keep a cross-over cable handy when I move large amounts of data between laptops, but it's nice to have the wireless network if I only need to transfer a couple gigs.

Since I've mentioned DSL multiple times, you might wonder why I don't switch to cable. One reason is that I don't want to run cable to my house. I just spent a lot of money putting new siding on my house, and I don't want the cable guy to mess it up trying to punch a whole through it. However, the biggest reason I don't want to switch to cable is that Comcast cable is well known for being one of the most disliked companies out there. It routinely has the lowest customer satisfaction ratings. Hence, I stick with DIRECTV and AT&T DSL (which was originally SBC Yahoo DSL).

By the way, one thing that surprised me was that I can actually get faster download speeds over my T-Mobile phone (while on BART) than I can over DSL. However, the T-Mobile coverage at my house sucks, as does AT&T, Sprint, and Verizon.

If you're interested in the raw data for all of my tests, here it is:

Linksys WRT54GL (several years old):
  Download: 5.13Mbps
  Upload: 0.59Mbps
 Wireless (originally channel 6):
  Download: 1.33Mbps
  Upload: 0.43Mbps
 Wireless (changed to channel 11):
  Download: 5.13Mbps
  Upload: 0.60Mbps
 Downloading 1.1GB from one laptop to another over wireless: 15-20mins
ASUS RT-AC56U ($200, new at Frys):
 Wireless 5Ghz (with QoS enabled, on top of my microwave):
  Download: 5.19Mbps
  Upload: 0.58Mbps
 Same on 2.4Ghz.
 Downloading 1.1GB from one laptop to another over 5Ghz wireless: 2-3mins
Using my T-Mobile Android phone as a personal HotSpot (over 3G, I think):
 Download: 8.35Mbps
 Upload: 0.53Mbps


Ian Bicking said…
Do you really need to be on 2.4ghz to talk to a device on the network? I thought generally these devices could talk to anything that was on the same local network, i.e., no NAT in between the devices. If you actually have two different routers then it'd be a problem, but even then only if you haven't set one of them up in bridge mode.

I sometimes suspect there are 2.4ghz non-wifi devices that really mess things up (we have a baby monitor that can be problematic), but it's hard to debug, and it doesn't effect signal strength only reliability of the packets. Also walls, damn walls.
jjinux said…
Thanks for the comment, Ian.

Chris Dudte asked the same thing. He was wondering if somehow there were UDP broadcasts that weren't making it from one network to the other. He told me to make sure they were bridged. I'll put my two laptops on separate frequencies and see what the IPs are and if they can talk. I'll also try ping.

Chris also said I need to try out two useful Android apps WiFiFoFum and Amped Wireless.
Matt Singer said…
I actually have a better experience when the streaming receiver (Chromecast, AppleTV) are on the other band from the transmitter (Tablet, laptop)

This really reduces the latency and increases the throughput because the AP.

You should be able to talk to any device regardless of where it's connected unless you managed to turn on some feature like AP isolation, etc.

I have an Asus RT-N66U and have no problems.
Joe Fernandez said…
Ha! Sounds a lot like what I went through about 18 months ago with my old Linksys WRT54GS. It suddenly started sucking. Why? Old hardware? OK, replaced it with a well-reviewed Netgear WNDR3700. Still sucks.

I believe the biggest problem had to do with my neighbors all piling on to the same 2.4Ghz WiFi channel, which became obvious after doing some sniffing with Wifi Analyzer (Android app). I switched the Netgear to a less-used channel, and the complaints from my wife dropped off dramatically. :-) Success! I took it a couple steps further by repositioning the new router to a higher location (fewer physical objects between it and my devices), and then adding a 24-port, 1Gigabit Ethernet central switch and wiring a bunch of rooms with wall jacks to where network a connection was needed.

Anyway, glad to hear you solved your wireless woes and relieved to know I'm not the only one sweating my wireless connections. Cheers, JJ!
Leon Atkinson said…
Check out Wifi Analyzer for Android. It will show you a graph of which channels are being used by everyone near you along with the strengths. Even better than just picking a different channel.

I recently had a DSL outage and used my Sprint phone as a hotspot. Yeah, 4G speeds from the phone shared via wifi to the laptop beat DSL. It's expensive, though.

My Netgear router does both 2.4 and 5 at the same time. I thought I understood that newer cards would switch between frequencies as needed. The 5Mhz version does have a unique SID if you want to force 5Mhz. And everyone's on the same LAN. No trouble using my chromecast.
Gorno said…
I agree. Your DSL connection is a bottleneck. Maybe it's time you upgraded.
zippy said…
Are you on Speakeasy? I switched from Speakeasy to Sonic (also DSL) and about doubled my speed. Sonic also has great frontline techs. Not as fast as cable, but they're my favorite area ISP.
jjinux said…
Thanks for all the comments, guys. You've given me a lot of ideas to try out!
jjinux said…
I got rid of the section on Chromecast. I don't know what I was doing wrong initially, but it's a non-issue.

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p