Meraki reworks product line, drops new sales of community flavor: The cheap mesh router company has mutated slightly once again. The partly-Google-backed firm founded by MIT RoofNet “graduates” built the company on the notion that they could sell $50 routers that could mesh with each other, and use a robust central management system they developed. Over time, the $50 price didn’t hold up for commercial networks of scale. Last October, the company mishandled a change in its business model when they abruptly announced a $100 increase in price for newly purchased nodes under their Meraki Pro level for any network that wanted to control whether or not ads appeared, have user accounts, and charge for service. (They eventually recovered, apologized, and reworked some of the transition details.) The company continued to offer a $50 indoor and $100 outdoor Standard level nodes for networks that required ads and had other limits. As of a few days ago, Standard is dead, and the Meraki mini has been upgraded to the Meraki Indoor ($150). The Indoor has signal strength LEDs on the side for better help in placing units, an internal antenna, and better resilience against power fluctuations. The company explains its move in eliminating Standard by noting that most customers moved to Pro. It’s not precisely the end of idealism (nor did that happen last October), as Meraki is still one of the major commercial mesh vendors, and their products are still vastly easier and a fraction of the cost of higher-end competitors. (Update: On Friday, Meraki upgraded all its original user to the Pro edition at no cost. They’re also continuing to sell the lower-priced Standard nodes to existing network customers until January 2009.)
New life for dead Tempe network? Another firm has expressed interest in buying the pennies on the dollar assets that remain of the former Kite Networks installation in Tempe from the firm that financed the venture as long as they can negotiate a new, more favorable deal with the city for mounting and removal rights. CTC, Inc., which the East Valley Tribune reports runs networks in the Kansas City, Mo., area, thinks there’s an opportunity. The article notes that reception problems were due in part to the prevalence of stucco in Tempe, common in the southwest. Stucco walls layer plaster or other materials on a wire mesh for strength that turns a house into a bit of an accidental Faraday cage, partially shielding the home from electromagnetic radiation. (Could I go so far to say that Tempe’s network could be a phoenix? Ouch.)
Wake up, you darn computer: Intel’s new Remote Wake motherboards won’t work with Wi-Fi, it’s important to note. The feature, announced today, will let an incoming VoIP call (the articles all say “phone call over the Internet”) to wake a computer, as long as the call comes from a particular source. Of course, the standard SIP protocol for VoIP doesn’t have the kind of security and integrity that would allow this; Intel has to overcome the problem with network address translation that renders most computer unreachable from outside the local network without a separate service like GoToMyPC or LogMeIn; and it will only work for computers connected via Ethernet to a local network, because Wi-Fi is off when a computer sleeps, while Ethernet can remain lightly active. I don’t have the protocol details yet, but there’s long been a Wake on LAN protocol that required support in a router, operating system, and Ethernet card; Intel may be leveraging this.
Wee-Fi: Houston-Fi, ASCII WPA Passphrases, Green Wi-Fi
American Launches In-Flight Broadband Pilot
IDF: More ‘Nehalem’ Details, 6-cores
Atom Feed (xml)