Firstly, I think that I was a very early adopter of both residential broadband and wifi. Linksys was the obvious leader in devices for this market. I bought a Linksys WAP-11 when they were brand new and fairly pricey. I wired it into my trusty Linksys BEFSR-41 4-port wired router. That device was fed by a Time-Warner Road Runner cable modem back in 1998.
Later, when the new 802.11g type wifi was starting to become available I migrated to a Linksys WAP-54G.
When we started to use Vonage I also moved to using a Linksys BEFSR-81 wired router specifically for its QoS feature. You will see this mentioned specifically in my early post called “The Beginners Guide To Successful VOIP Over DSL”. Clearly, I’ve had my fair share of Linksys consumer products.
However, a lot of my later experience with Linksys support was less than stellar. The Linksys BEFSR-81 had some serious firmware issues that went unacknowledged by the manufacturer for a long time. In public forums the problems were well known and documented, but the company newly acquired by Cisco, was slow to act.
This sort of thing eventually caused me to steer away from Linksys. While I might have selected another retail brand of network devices I ended up curious to try the combination of m0n0wall and a Soekris Net4501/4801 embedded single board computers. That pairing has proved to be simply fantastic!
Having just RMA’d the Cisco WAP I was left pondering what to try next. I thought it only logical to ask around and see what other people had used successfully. So I posed the question to various folks via e-mail, Facebook and Twitter. The results were, at least to me, a bit surprising.
I expected to hear a variety of people offer advice about their experience with a range of products. I thought that I’d hear about names like Linksys/Cisco, Netgear, SMC, Asus, Draytech, Buffalo, Hawking, etc. While there was the occasional mention of devices from such manufacturers, by far the most common recommendation was to use a Linksys WRT-54GL router loaded with a third-party firmware like DD-WRT, OpenWRT or Tomato.
I find this to be amazing on a couple of different levels.
That there was such widespread recommendation of such an approach is very curious. People actually buy the hardware, then going to considerable trouble to re-flash it with something like DD-WRT. It’s an odd kind of condemnation of the firmware that Cisco/Linksys is themselves providing.
Cisco/Linksys has to keep developing their own firmware since taking the decision to not use Linux as the basis of the WRT-54G series hardware that doesn’t bear the “GL” suffix. These non-GL devices can be manufactured with just a little less memory, different processor, etc. The result is a device that’s slightly cheaper to manufacture. It might only be a dollar or two difference, but when they’re selling millions of units it certainly adds up.
In a Twitter exchange @phoneboy noted that Cisco should probably just use DD-WRT as their default firmware. Others suggested that Cisco just buy the company behind DD-WRT. I wonder if such a move would be the beginning of the end for DD-WRT. Is their independence a significant source of what makes DD-WRT attractive?
I can’t help but find the through of buying a WRT-54GL and then loading third party firmware vaguely offensive. It’s as if I’d be rewarding Cisco/Linksys for not delivering upon the promise of the hardware that they’re offering.
While I appreciate the feedback from everyone who made a recommendation, I don’t think that particular route is a path that I will follow.
In part 3: Considering the role of router vs wifi AP