[Sugar-devel] meshing XOs with netbooks (WAS: Re: [Bugs] #79 NORM: SOAS should mesh network when possible)
Gary C Martin
gary at garycmartin.com
Sun Jun 14 20:32:17 EDT 2009
On 10 Jun 2009, at 10:18, Tomeu Vizoso wrote:
> On Wed, Jun 10, 2009 at 03:16, Andrés
> Ambrois<andresambrois at gmail.com> wrote:
>> On Tuesday 09 June 2009 10:07:19 pm Martin Dengler wrote:
>>> On Wed, Jun 10, 2009 at 01:46:07AM +0100, Gary C Martin wrote:
>>>> There's another 'non-mesh' option possible for the '3 kids under
>>>> a tree'
>>>> case. They will likely have no AP/infrastructure to connect to, so
>>>> blanking the jabber server is not an option. For them the existing
>>>> local-link config would be very viable solution, but there's no
>>>> Sugar UI
>>>> for it yet.
>>> Would this be as simple as a "ad-hoc" device in the frame that put
>>> wireless into ad-hoc mode?
>> As usual, Tomeu beat us all there :P
> This is already in git HEAD, but the patch should apply cleanly to any
> 0.84 such as Soas. If people would like to give it a try and provide
> feedback, would be awesome.
Beep. Just to note my interest on this...
If we chose a fixed network name, rather than based on buddy name
(much like olpc-mesh was), how would this behave when the actual
network owner/creator shutdown while others were connected? I'm
guessing at best it would trigger NM to recycle through the possible
network connections again, hopefully landing back on the same (or re-
creating if you happen to be first/only) named network.
Any one know if existing collaboration sessions would manage to stay
up, or all die during this?
I guess this needs testing... so if I have time will explore your
patch with the 3 XO's here (sugar-jhbuild is not playing well for me
just now with salute for testing this).
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel