Re: Mesh Dreams = OLSR

2010-08-25 Thread Ed McNierney
Folks - Thanks for getting the discussion rolling. Although it may be obvious, I want to point out one aspect of OLPC's mesh needs that has complicated matters. Our XO laptops are used at home, in a sparse network environment, and at school, in a dense network environment, and all levels of

Re: Mesh Dreams = OLSR

2010-08-24 Thread Chris Ball
Hi Reuben, Consider the benefits of using open source software versus our closed source firmware and partnering with communities like Freifunk whose network is ~ 800 node, guifi.net is almost 10k nodes in Barcelona, Athens Wireless is 5k nodes. The fact that a custom mesh

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 10:13 AM, Reuben K. Caron wrote: Consider the benefits of using open source software versus our closed source firmware and partnering with communities like Freifunk whose network is ~ 800 node, guifi.net is almost 10k nodes in Barcelona, Athens Wireless is 5k nodes. The

Re: Mesh Dreams = OLSR

2010-08-24 Thread Reuben K. Caron
On Aug 24, 2010, at 10:26 AM, Chris Ball wrote: The fact that a custom mesh algorithm would have to run on the CPU -- prohibiting any kind of idle-suspend -- makes it a non-starter for an XO deployment in my eyes. Did you have any thoughts on this? Hi Chris, Great point. Thank you for

Re: Mesh Dreams = OLSR

2010-08-24 Thread Jon Nettleton
In those scenarios we run into RF density issues even when using APs. I would think that under a close proximity scenario like this one we would want to reduce the power level of the wlan cards so they are operating in a much smaller space. Theoretically if kids are spaced out in a normal

Re: Mesh Dreams = OLSR

2010-08-24 Thread Reuben K. Caron
On Aug 24, 2010, at 11:24 AM, Richard A. Smith wrote: On 08/24/2010 10:13 AM, Reuben K. Caron wrote: Consider the benefits of using open source software versus our closed source firmware and partnering with communities like Freifunk whose network is ~ 800 node, guifi.net is almost 10k

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 11:39 AM, L. Aaron Kaplan wrote: On Aug 24, 2010, at 5:24 PM, Richard A. Smith wrote: On 08/24/2010 10:13 AM, Reuben K. Caron wrote: Consider the benefits of using open source software versus our closed source firmware and partnering with communities like Freifunk whose

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 11:44 AM, Reuben K. Caron wrote: From what I understand, OLSR has a better mechanism for maintaining the mesh information. If you recall any change in mesh was previously broadcasted to all listeners. OLSR is configurable. For instance, information would only be broadcasted to

Re: Mesh Dreams = OLSR

2010-08-24 Thread Reuben K. Caron
On Aug 24, 2010, at 12:08 PM, Richard A. Smith wrote: I'm not talking about comparison to our previous mesh. Thanks keeping me on track. I'm talking about comparison to an AP. Overall we currently don't have much need for mesh as most of our scenarios are a dense cloud of children in

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 11:45 AM, L. Aaron Kaplan wrote: On Aug 24, 2010, at 5:24 PM, Richard A. Smith wrote: On 08/24/2010 10:13 AM, Reuben K. Caron wrote: Consider the benefits of using open source software versus our closed source firmware and partnering with communities like Freifunk whose

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 12:11 PM, L. Aaron Kaplan wrote: The largest of our mesh problems did not have to do with scalability on sheer number of nodes but rather scalability in density. Is there any information available on how these networks perform when there are 50 - 100 of them next all in the

Re: Mesh Dreams = OLSR

2010-08-24 Thread Reuben K. Caron
On Aug 24, 2010, at 11:24 AM, Richard A. Smith wrote: The largest of our mesh problems did not have to do with scalability on sheer number of nodes but rather scalability in density. Is there any information available on how these networks perform when there are 50 - 100 of them next

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 01:01 PM, L. Aaron Kaplan wrote: Well - the issue is IMHO that OLPC always sold the public on the mesh idea. So it is somewhat of a bummer that the mesh is gone now. Let me re-phrase what I said before all the rumors start to fly and I get in trouble. The idea of mesh is

Re: Mesh Dreams = OLSR

2010-08-24 Thread Reuben K. Caron
On Aug 24, 2010, at 1:29 PM, L. Aaron Kaplan wrote: Hm well, you at least got me thinking how we can make a small dense indoor mesh working without APs interesting challenge. Like think about replacing those smart APs by a distributed version. Interesting... a. Maybe a

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 01:11 PM, Reuben K. Caron wrote: http://dev.laptop.org/~reuben/Elsevier2008_OLSR_compare.pdf This differs from most other papers that I have read that use theoretical simulations. Thank you. That's the sort of data I'm talking about. Unfortunately, its not quite real world

Re: Mesh Dreams = OLSR

2010-08-24 Thread Reuben K. Caron
On Aug 24, 2010, at 1:34 PM, Richard A. Smith wrote: They are only able to achieve this with 30dB attenuators on the signal. We would want to see what one can do with stock cards without an attenuator. Can we adaptively get the signal down in driver/software?

Re: Mesh Dreams = OLSR

2010-08-24 Thread Richard A. Smith
On 08/24/2010 01:43 PM, Reuben K. Caron wrote: On Aug 24, 2010, at 1:34 PM, Richard A. Smith wrote: They are only able to achieve this with 30dB attenuators on the signal. We would want to see what one can do with stock cards without an attenuator. Can we adaptively get the signal down in

Re: Mesh Dreams = OLSR

2010-08-24 Thread L. Aaron Kaplan
On Aug 24, 2010, at 5:24 PM, Richard A. Smith wrote: On 08/24/2010 10:13 AM, Reuben K. Caron wrote: Consider the benefits of using open source software versus our closed source firmware and partnering with communities like Freifunk whose network is ~ 800 node, guifi.net is almost 10k

Re: Mesh Dreams = OLSR

2010-08-24 Thread L. Aaron Kaplan
On Aug 24, 2010, at 5:24 PM, Richard A. Smith wrote: On 08/24/2010 10:13 AM, Reuben K. Caron wrote: Consider the benefits of using open source software versus our closed source firmware and partnering with communities like Freifunk whose network is ~ 800 node, guifi.net is almost 10k

Re: Mesh Dreams = OLSR

2010-08-24 Thread L. Aaron Kaplan
The largest of our mesh problems did not have to do with scalability on sheer number of nodes but rather scalability in density. Is there any information available on how these networks perform when there are 50 - 100 of them next all in the same room or in adjacent rooms? Yes! And the

Re: Mesh Dreams = OLSR

2010-08-24 Thread L. Aaron Kaplan
(...) BTW Richard, as far as I remember the problems with 802.11s seemed to be: 1) the standard is not a standard and it was intentionally crippled 2) the drivers were very b0rked and broken (and Marvel did a terrible job with the driver software) Scalability to less than 30 laptops

Re: Mesh Dreams = OLSR

2010-08-24 Thread L. Aaron Kaplan
On Aug 24, 2010, at 7:11 PM, Reuben K. Caron wrote: On Aug 24, 2010, at 11:24 AM, Richard A. Smith wrote: The largest of our mesh problems did not have to do with scalability on sheer number of nodes but rather scalability in density. Is there any information available on how these

Re: Mesh Dreams = OLSR

2010-08-24 Thread L. Aaron Kaplan
On Aug 24, 2010, at 7:20 PM, Richard A. Smith wrote: On 08/24/2010 01:01 PM, L. Aaron Kaplan wrote: Well - the issue is IMHO that OLPC always sold the public on the mesh idea. So it is somewhat of a bummer that the mesh is gone now. Let me re-phrase what I said before all the rumors

Re: Mesh Dreams = OLSR

2010-08-24 Thread L. Aaron Kaplan
On Aug 24, 2010, at 7:32 PM, Reuben K. Caron wrote: On Aug 24, 2010, at 1:29 PM, L. Aaron Kaplan wrote: Hm well, you at least got me thinking how we can make a small dense indoor mesh working without APs interesting challenge. Like think about replacing those smart APs by a