A Quiet Day

Photo of author

Tim Higgins

The process of pulling all the data together, cross checking it for consistency and errors and making sense of it all reminds me of why I don’t do "round-ups" more often. And certainly not comparisons of six products that require so much testing! But I hope the results are worth it.

On another note, my thanks to those of you who have given some of your valuable time and taken our Site Survey. The results are used not only to try to better match advertisers to you, our audience, but some of the questions provide important feedback on our strengths and weaknesses, that I really do take to heart and act upon. If you haven’t taken the survey, please help SmallNetBuilder and take it and know that you have my sincere thanks.

Related posts

Waiting for Draft 2.0 updates

While the Wi-Fi Alliance's list of 802.11n Draft 2.0 certified products is growing longer, of course, there is still a catch. A product's appearance in the list doesn't necessarily mean that the products you can buy today are Draft 2.0 compliant. Nor does it mean that you can download firmware and drivers to bring them into compliance, either.

Why Build Your Own NAS?

Bill Meade's Build a Cheap and Fast RAID 5 NAS How To has continued to be one of our most popular articles, even though now it's almost two years old. But with the price of ready-to-buy RAID5 1 TB NASes as low as $500, does it still make sense to roll your own?

11n Draft 2.0 gear not working yet, but does anyone really care?

I share Glenn Fleishman's disappointment with this week's announcement by the Wi-Fi Alliance that they have only begun their certification testing. But judging from what I've seen so far, getting draft 11n gear up to spec is going to be a long, difficult process.

I spent a few days last week testing a D-Link DIR-655 router and DWA-652 Cardbus card, which are based on Atheros XSPAN silicon. These are the first products to have firmware and drivers posted that allegedly implement 11n Draft 2.0 compliance. My primary focus was to see whether the legacy protection mechanisms added in 802.11n Draft 2.0 were working in actual product.