Automatic Wireless Network Organisation
babycakes writes "Interesting article over at the BBC about the future of wireless networks. Researchers at Intel are developing mesh networking technology that automatically organizes the best routes between wireless devices for better bandwidth control, now that the number of wireless devices is set to explode." Neat stuff, but they've yet to implement any sort of security controls. Until they do, it's going to be a real party for wireless eavesdroppers. timothy adds: La Camiseta writes "Wired has an article discussing the extent that some people will go to in order to stay connected. My favorite is their 4-way SMP system that fits into a briefcase."
I wonder what the security implications are. If every device is able to route, a malicious device could claim to have great connections to other devices in the mesh and then drop packets. Unless there is some way of authentication in the mesh (so that only authenticated devices can participate), it would need some trust/rating system so devices can exchange information about the reliability of other devices...
So they intend on doing away with the traditional hub/switch/router layout, in which someone administers the network and decides what amount of bandwidth goes where, and instead embed these functions into the wireless devices themselves? Seems a bit ambitious.
I have to assume those are the 800mhz versions from the CPU fan, but still, these things have very little power from my experience with them. Cool little toys, maybe enough for a low-end workstation or terminal, but I wouldnt think of using one in a server situation.
I actually used one to run my squid-based proxy, and it was outperformed by the P200/MMX I wanted to replace.
Why cluster 4 of those? I'd think a 2 gig Celeron (of course P4 would be preferred) would have more power, faster DDR Ram, be as cheap (if not cheaper).
I cant fathom why one would cluster those little Eden boards, unless they were going for redundancy; a poor mans fault tolerant server.
Anyone?
I don't need no instructions to know how to rock!!!!
The company I work for has been doing this for over 2 years. Seems like Intel is way behind the curve on this one. You can see what we've been doing @ http://www.meshnetworks.com .
"Maybe this world is another planet's Hell" Aldous Huxley
If they're all working for the same task, like distributed compiling, or just running the same OS, then I think it can be called SMP. If it's just 4 redundant servers, I'd say not.
I dont think SMP means all the procs need be on the same sheet of fiberglass.
Then again, I may be wrong and will be shouted down by some nitpicking geek.
I don't need no instructions to know how to rock!!!!
...when the modern nerd can hack from low-flying aircraft passing over your house! Ars Technica have done it already - twice, no elss: War Flying, 1 and War Flying, 2
This is just too cool.
exactly - I was going to say there doesn't look to be any use of shared memory (not even sure how they would).
I'm curious if they are writing stuff with something like PVM for a beowulf type thing, or the more likely OpenMosix option.
Also curious as to what they are using it for. (didn't read the article but checked out that briefcase b/c it sounded and looked cool)
There are some odd things afoot now, in the Villa Straylight.
Why not? You get something in return for the resources you have to give up: a network.
It sounds like Freenet to me. In order for the network to work well people need to run nodes. Yes, they will transfer stuff for other people, something that doesn't benefit your directly. But it also keeps the network ticking, which is what you want.
I suppose it will work this way: If you want the advantages of the network then you have to contribute with your battery.
--zawada
(*) By cooperative environment, I'm talking about mesh networks that are built by many independent entities, with each node carrying the traffic of multiple participants. e.g., your laptop participates in a cloud of laptops that ultimately carries all participants' Internet traffic back to an access point somewhere.
In Soviet Russia, the Beowulf cluster imagines you!
Mesh Routing links.
MeshAP/MeshBox from LocustWorld is based on AODV routing module. There are also userspace versions of AODV. Plus there are at least two other competing mesh routing algorithms, and there are other hardware mesh solutions, but MeshAP has a lot going for it.