Like every other website on the planet, SmallNetBuilder uses cookies. Our cookies track login status, but we only allow admins to log in anyway, so those don't apply to you. Any other cookies you pick up during your visit come from advertisers, which we don't control.
If you continue to use the site, you agree to tolerate our use of cookies. Thank you!

Router Charts

Click for Router Charts

Router Ranker

Click for Router Ranker

NAS Charts

Click for NAS Charts

NAS Ranker

Click for NAS Ranker

More Tools

Click for More Tools

Wireless Features

Conclusion

As I said at the beginning of this piece, there are many reasons for changing the design of a product and I'm not criticizing that practice. But it's time that all consumer networking manufacturers gave consumers a better indication of what they are buying.

Despite what manufacturers would like us to believe, there are differences in wireless chipsets...especially in a technology as new, unfinished and complex as 802.11n. Hell, chipmakers spend a lot of marketing money and even buy expensive booth space at shows like CES to convince potential customers of the difference! And even when the same chipsets are used, hardware design, firmware and driver differences can produce products with noticeably different performance.

Some vendors, such as Belkin, D-Link and Trendnet, already clearly indicate product hardware revisions on their product packaging. So at least at retail, where you can pick up the product box and read it, you can tell that something is different. However, others, such as Linksys and Netgear, do not.

A very simple solution would be for manufacturers to add the FCC ID to product boxes and on-line marketing material. Manufacturers must resubmit products to the FCC whenever they make component changes. Minor changes ("Class II Permissive Changes") don't require a different FCC ID. But more significant changes, such as chipset changes, require a new FCC ID.

Unfortunately, most manufacturers don't put the FCC ID anywhere in their marketing information or on the product box. It must, however, be indicated on the product itself, and is usually found on or near the product's serial number label.

If manufacturers did provide FCC ID labeling, consumers who cared about the specifics of the wireless products they buy could visit the FCC ID database and enter the product FCC ID. The internal photos and test reports would tell them all they need to know to make an informed buying decision.

But information on the product box doesn't help if you are buying online, since the product model number and SKUs are the same for different-rev products. It's unlikely that manufacturers will ever change model numbers or SKUs to reflect hardware revisions, since that would probably play havoc with inventory management. And since all e-tailers now charge restocking fees (typically 15%), buying online is not the way to go if you need a specific revision.

Change is inevitable and even required to compete in today's world of razor-thin margins. Let's just make the process more transparent so that consumers can make more informed purchase decisions.

More Wireless

Wi-Fi System Tools
Check out our Wi-Fi System Charts, Ranker and Finder!

Support Us!

If you like what we do and want to thank us, just buy something on Amazon. We'll get a small commission on anything you buy. Thanks!

Over In The Forums

I’m trying to replace an old router. It’s not going very well for me since I’ve been literally trying the whole year, and I’m thinking with Black Frid...
I'm facing a problem with a recent setting my provider KPN (from the Netherlands) changed for their interactive IPTV boxes.Right now the setup is in b...
Between marketing jargon and technical descriptions, every time I turn around there's some new type of QOS. Please help my confused brain!Regardless o...
I have started this thread to document my journey in setting up a DIY NAS.I currently have a ReadyNAS RN212 which is a desktop model with 2x2Tb WD red...
Checking out the RT-AC68U's /dev/urandom and running some tests on it.I collected a few large chunks of entropy from the AC68U's /dev/urandom:Code: s...

Don't Miss These

  • 1
  • 2
  • 3