Mesh Potatos and OLPCs?

[Luiz Magalhaes]

I worked extensively with mesh networks and tested OLPC mesh network
under the auspices of the Brazilian government. I should clarify that,
most of the actual work was done by my then student, Ricardo Carrano,
who is now a professor in my department. I think most of the published
papers about the OLPC take on 802.11s are by us. We came to the
conclusion that a dense and a sparse mesh networks have different
needs, but as OLPC lost interest in supporting its mesh and a lack of
interest of the Brazilian government in funding research in that area
(also because the current testbed of 150.000 laptops are classmates,
which do not use 802.11s), our work in that area has been in the back
burner.

We still have plans for MAD (the Mesh Adaptation Daemon, which would
find out which environment - dense or sparse - the XO was in, and
adapt its parameters to it), but no progress has been made, and its
impact may be very small now, even if it is ever out of the drawing
board.

I agree that successful mesh networks are mostly static, but we
thought that the very mobility of the network (which in Brazil could
have 54 million nodes) would make it interesting.

  --luiz

2011/3/23 Ed McNierney <ed at laptop.org>:
> John -
>
> While I am not familiar with the Mesh Potato, I have spent some time trying to figure out whether wireless mesh networking is really as hard as the OLPC universe seems to find that it is.
>
> I have come to believe that both wired and wireless mesh networks are really doing pretty well out there in the world, *provided* the nodes are immobile, or relatively so.
>
> The examples you point to seem to fall into the "immobile wireless" category, and I think one is likely to find reasonable success in that field.  And I don't mean *really* immobile, but rather "don't move about very much".  The wireless multi-room music systems from Sonos, for example, seem to use wireless mesh pretty successfully, but the nodes are pretty stable.  And they don't get very dense (you don't put 30 sets of stereo speakers in one room).
>
> I have not found any examples of either (a) dense wireless mesh or (b) highly mobile wireless mesh.  In case (a) I assume that is normally not a problem, so it's not being solved.  In case (b) one encounters the classic OLPC mesh problem - 50 laptops scattered about in children's homes at night all want to act as mesh nodes, while those same 50 laptops all go into the same classroom the next day where they DON'T want to all act as mesh nodes (i.e. they create case (a)).  I don't know of anyone who has successfully solved that problem, other than by the less-than-satisfactory route of giving the users a switch and expecting them to turn mesh on and off as they move.
>
> So I believe many people are having successes with relatively static wireless mesh networks, but I also believe that no one is having success in the scenario OLPC has always wanted to support.  If my latter perception is wrong I would love to know of a counterexample (using any hardware, not just XO laptops).
>
>        - Ed
>
>
> On Mar 23, 2011, at 7:38 PM, John Gilmore wrote:
>
>> Has anyone used the "Mesh Potato" devices from villagetelco.org to
>> provide mesh connectivity to a network of OLPCs?
>>
>> Eben Moglen's "Freedom Box" mailing list has been exploring whether to
>> include mesh in their boxes.  My experience with OLPC's mesh has led
>> me to question the risk/reward payoff of doing wireless mesh, though I
>> think a wired mesh of Ethernet cables could be very interesting.  But
>> others have turned up who are building wireless meshes, who claim to be
>> making them work in production.
>>
>> Here's one such, the "Mesh Potato" from http://www.villagetelco.org.
>> It's a $119 (retail) box with 802.11b/g and a wired phone jack, plus
>> Ethernet.  It meshes over 802.11, provides an access point, and lets
>> you make phone calls to other Mesh Potatos or any SIP phone reachable
>> on the net.  It is open hardware, runs open software, and is designed
>> to live outdoors and run on rough rural power.  It unfortunately needs
>> detailed sysadmin with Linux shell commands now.  This 1-minute
>> embedded YouTube video explains their goals:
>>
>>  http://www.villagetelco.org/2011/02/in-a-village-telco-minute/
>>
>> I've edited the enclosed message down to the relevant part:
>>
>>  Date: Mon, 21 Mar 2011 14:51:59 -0500
>>  From: Charles N Wyble <charles at knownelement.com>
>>  To: freedombox-discuss at lists.alioth.debian.org
>>  List-Archive: <http://lists.alioth.debian.org/pipermail/freedombox-discuss>
>>
>>  On 3/20/2011 8:44 AM, James Vasile wrote:
>>> Meshing is hard.  Nobody I met knows anybody who is nailing mesh
>>> networks.  I'm going to get all the mesh heads together soon for a
>>> real conversation to see if we can work towards a recommendation on
>>> the most promising avenue.
>>
>>  Um.... *waves*.  I guess I need to get out more. I've built a few mesh
>>  networks over the past year. It's not that hard (it used to be quite
>>  difficult, but the underlying bits have really matured).  Us mesh
>>  heads hang out at villagetelco.org and a few other places (olsr.org,
>>  batman.org) :) We have an annual gathering already,
>>  http://battlemesh.org/
>>
>>  Join the mailing list and say hi. Mesh is moving along, slowly and
>>  steadily.  Mesh is the underpinning of an open network. Open networks
>>  are the underpinning of everything else.
>>
>>  I feel that mesh networks have reached the point of maturity, that
>>  they can stand on their own. I feel they are readily and rapidly
>>  deployable (plug and play) due to the work of villagetelco.org.
>>
>> Has OLPC seen these before?  If so, what's your experience?
>>
>>       John
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>