Linksys branding to be replaced by Cisco. No surprise here

Photo of author

Tim Higgins

Linksys’ mission as an entry-level line for Cisco was revealed in 2004 with the introduction of the Linksys to Cisco Trade-Up Program. And its recent re-launch of its Linkys One / Connected Office initiative just served to underscore the company’s real focus: to get businesses too small to be served by normal Cisco sales channels away from Best Buy, CDW and the like and into the orbit of Cisco VARs.

This is not to say that Linksys has conceded consumer networking to Netgear, D-Link, Buffalo, etc. One look at the shelf space devoted to Linksys products at any networking product retailer confirms that the company still intends to dominate that space as long as it makes sense (cents?) to do so. And Linksys has been as aggressive as any of its rivals at going after the draft 11n wireless market, which is still squarely aimed at getting consumers to upgrade their wireless gear.

So don’t start lighting candles for those blue and gray Linkies yet. That name won’t go until Cisco has squeezed every bit of value from it, and it looks like there is still plenty of juice yet to be had.

Related posts

Wireless Intruder Alert Systems

Something I'm surprised I don't get more questions about is how to tell when someone (who you don't want there) is trying to use your wireless LAN. I swear there used to be a simple application that came with early Macintoshes called "Knock Knock" that would pop up a dialog when someone attempted to connect to your Mac. I'm looking for something similar, preferably free, that runs on Windows.

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.

Draft 11n getting neighborly

Updated with corrections from Bill McFarland 1/29/07

In both private discussions and during the Intel draft 11n chipset webcast, I have been hearing hints about 11n's "bad neighbor" problem having been addressed in draft 1.10. I was able to get Atheros' CTO, Bill McFarland on the phone to bring me up to speed on what actually got into the 1.10 draft. Note that some of these mechanisms were being debated back when Draft 1.0 was being finalized. But since consensus couldn't be reached, the 11n task force punted and didn't include any of them in 1.0.