Powerline Pessimism
Powerline networking, for both LAN and WAN applications, is once again a hot topic after years' worth of periodic hype. Cisco's Linksys division, Intel and Motorola have joined the HomePlug Industry Alliance board of directors, and Intel and Motorola have both invested in dominant powerline networking silicon provider Intellon. The HomePlug AV standard, touting a 200 Mbps PHY rate, is finalized, and the HomePlug Conference 'lovefest' was held just two weeks ago.
Friday, at a digital audio networking panel held here at the Audio Engineering Society Conference, a Microsoft representative extolled the promise of HomePlug AV (along with 802.11e/n) as a means of easily and reliably distributing high bit-rate data streams around consumers' homes. The city of Manassas, Virginia just announced that powerline would be the means by which it distributed broadband Internet access to its citizens; so did the state of Tazmania in Australia, and Google's even investing in BPL (then again, what isn't Google investing in?). And, judging from the abundance of comments to Maury's ongoing blog post series, powerline networking is a topic that you're closely following, too.
Call me a wet blanket, if you want, but I feel compelled to inject some pragmatic hands-on perspective into the debate. Summertime arrived in Sacramento four months ago and, just as in years past, the HomePlug-based spurs of my LAN started flaking out again. Before you continue, please read (or re-read) my short article 'A Man, A LAN, a Plan' originally published last August; specifically, peruse the floorplan of my network's topology (link is to a PDF). And keep in mind that mine is a single-story home of less than 2,000 square foot size, built in the mid-1950s. Not some sprawling mansion with ancient, degraded wiring.
Throughout June, the powerline link between my office and our backyard 'hut' would be working fine when I got up in the morning, but by mid-afternoon the connection would be severed. By July, the office-to-hut link was dead 24 hours a day. And the link between my office and the AC (more accurately, evaporative cooler, commonly known as 'swamp cooler') closet got flaky every time the fan kicked on; pings to Yahoo's server that normally returned within 10 msec randomly stretched to a second or more, and occasional packets completely disappeared. The Cogency Connection Manager utility verified that whereas one half of the bidirectional office-to-closet link remained essentially solid, the opposing direction's data flow was severely compromised. And I saw the same problem with both Belkin and Maverick Power Systems v1.0 (14 Mbps) HomePlug hardware.
Last September, Intellon announced its first v1.0 Turbo (85 Mbps) HomePlug chipset and, when I met with the company at January's Consumer Electronics Show, they promised me a few v1.0 Turbo-based Ethernet-to-HomePlug adapters to test. In early June I received word that the adapters were nearing shipment, although it took two more months for the first two Aztech Turbo adapters to arrive (minus a configuration utility) and another month for the third (along with software) to show up. Fortunately, I was able to configure their passwords using the Cogency software (v1.0 and v1.0 Turbo adapters were also able to communicate with each other), although Connection Manager wasn't able to measure the data bandwidth running to and from the v1.0 Turbo units.
Good news: the v1.0 Turbo units didn't function any worse than their v1.0 predecessors. Bad news: they didn't function any better. Let me clarify that last statement; when the link was solid, the v1.0 Turbo bandwidth was approximately 30 Mbps, versus 7 Mbps with v1.0 units. But in any situation where a v1.0 device failed to establish or hold a reliable link to its peer, a v1.0 Turbo device would also fail. Also, I discovered that Aztech's units wouldn't interoperate with an old Kingston Technologies 10 Mbit hub I'd been successfully using with the v1.0 adapters; if I plugged a LAN client directly into the Aztech adapter, it'd establish network connectivity, but not if the hub was the intermediary. This was maddening to figure out; practically speaking, however, it was a non-issue. I'd already planned to replace the hub with a 100 Mbit switch, and the 802.11b access point in the hut with an 802.11g AP, reflective of the v1.0 Turbo HomePlug adapter's higher bandwidth capability.
Continued with 'Powerline Pessimism: Partial Progress and Pending Plans'….
urbarsese commented:
Damn!!! A Couple of days ago I got a call from 9722840600 - 972-284-0600 and was pretty sure the caller was a scam. I’m so sick and tired of promotional calls - I decided to complain to the gov and bitch. Check this out… Gulf Coast Western — the oil drilling company- contacted me We’re contacting me about employment. Apparently I got the job Wow, I really feel dumb. But I think I’ve lost my chance…???
urbarsese commented:
OMFG! This morning I received a message from 972-284-0600 & 9722840600 and I thought the the person calling was a scammer. So I decided to complain and dialed Gulf Coast Western and went nuts. You will never believe it… Gulf Coast Western -an oil corporation- was calling who I interviewed with last month - we’re calling to tell me I got the job! Any advice or help on how I can fix the complaint - and get the job?!!!
NonoIrrassy commented:
Avampibia commented:
Lagsexels commented:
pisiodsSisa commented:
XRumerTest commented:
RH commented:
James Borran commented:















