: Operating Controls"> Meanwhile, with more than 500 working meshes around the globe, engineer Anderson has already has QoS (quality-of-service) controls set up on his low-cost standard PC hardware, so that every mesh access point you set up can be an Asterisk phone exchange, automatically linking to every other mesh network in the world over the Internet with free calls, but also enabling the creation of low-cost village sub-exchanges.
Intel faces severe challenges technically. According to www.incidents.org, the 11s standard "is a wonderful application of wireless technology, allowing organizations to cover large areas without significant investment in infrastructure. I predict security to be a problem here, since the design of a mesh network is the same as that of a man-in-the-middle attack."
But this is not a prediction. Its history. Anderson worked out the threat three years ago, and solved it in 2002 with full cryptographic, certificated meshing–that is, all routing data and each IP address is signed.
He commented: "You cannot simulate this sort of research in the lab or on paper. No amount of theory will work. Ive been out on my bicycle for the past few years, actually installing and fixing mesh networks, and Im really not that impressed by people who say we need another IEEE standard, because we have one."
Proprietary? No: You can download the mesh code and source from LocustWorld, install it on your own PC and make your own mesh access point.
Only small-scale? Hardly! Have a look at Andersons clustering PDF file (hell mail it to you if you ask!) and see how you can join boxes together and route over multiple media.
"You can make a three-radio meshbox by joining three ordinary meshboxes together," Anderson said. "Any device can replace the radio, too. So, just plug in lasers, power-line adapters–even proprietary Intel meshes if you like."
If you need more bandwidth, "just add another link–it aggregates the bandwidth. This technology gives us access to WiMax or any 802.11g device and so on, without needing to fiddle with drivers."
Theres a simple, obvious explanation for this. Intel simply never heard about LocustWorld, right?
Wrong. As long ago as 2003, I wrote a widely read analysis of what Intel was doing with mesh networking. I wrote: "There is one mesh technology which has been creating [commercial] neighborhood networks for 18 months now; a new mesh is set up somewhere in the world every day using it, and it is fully Wi-Fi-compatible. Intel and Cisco have dismissed it as being nonstandard."
No, that wasnt the first time theyd heard of it. In February 2003, I remarked: "It looks as if Intel has decided to ignore everything that has been done in linking wireless network nodes into a "mesh"–and has, nonetheless, impressed observers with its originality of research!"
Thats more than two years ago, for anybody in Santa Clara, Calif., who has lost their calendar.
Anderson himself has spoken with members of Connors IEEE group, who say he should be talking to them. He takes the (possibly uncharitable) view that if they want consulting services, they should pay him for them, rather than asking him to pay them a subscription and waste his time in Disneyland twice a year.
This would, obviously, be a good idea for Intel. If they are as far behind LocustWorld as Connors announcement reveals they are, they need that help.
LocustWorld has written to Connor himself–so have I, by the way, Steven, so do feel free to reply, any day before I collect my pension. And somehow, Connor still feels free to go on telling the world that the mesh he will come out with—perhaps in 2006, maybe in 2007, which links only 25 static nodes—will be an advance over the mesh that is globally available, installed, working and tested, and has been fully functional for well over two years.
I cant understand why Connor feels he can get away with this. Maybe, after all, it is because there are some people who will, honestly, print whatever Intel tells them?
Check out eWEEK.coms for the latest news, reviews and analysis on mobile and wireless computing.