I'm not 100% certain we've pulled in members of the OLSR mailing lists
on this thread yet.
But they've actually got a number of very impressive *real world*
demonstrations of OLSRd in the wild. You'll have to search the devel@
archives for 'olsr' to find the emails I sent years ago with all the
d
Mike,
Thank you for the information!
To be clear, from what I understand from our discussions in the past
you're topology looks like
AP(802.11A + OLSRD) - AP (802.11B/G) - XO
You have several AP(802.11A + OLSRD) acting as your backbone and they
drop down to standard AP (802.11B/G) f
On Tue, Aug 24, 2010 at 11:13 AM, Reuben K. Caron wrote:
> Where Mesh != 802.11s but rather an adhoc, self healing, self
> organizing routable network.
Cerebro gave a great working demo of what you describe. Don't know how
they compare.
I think it is perfectly feasible to achieve what you want..
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
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 ne
On Tuesday, August 24, 2010 11:26:23 am Chris Ball wrote:
> 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 Bar
(...)
>>
>>
>> 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 t
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 childre
>>>
>>> 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?
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 alm
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 al
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 alm
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 brin
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 algo
Where Mesh != 802.11s but rather an adhoc, self healing, self
organizing routable network.
Imagine a world where Sugar on a Stick machines can communicate on the
same network as an XO laptop. A world where mesh capabilities are
hardware agnostic allowing anyone to bring up a mesh network by
15 matches
Mail list logo
