On Wed, 2009-07-01 at 12:18 -0400, Dan Williams wrote:
> > http://dev.laptop.org/~sjoerd/NM0.7/olpc-mesh.fdi
>
> Though you're really not going to want to use HAL fdi files for this,
> since master now uses only udev. You'll either want to hardcode the
> Marvell device IDs into nm-hal-manager (or
On Wed, 2009-07-01 at 12:18 -0400, Dan Williams wrote:
> If other APs appear later, it may well trigger the
> schedule_activate_check() which might cause NM to try to connect to that
> new network. To combat that, I'd suggest that the mesh device block the
> wifi device from activating if it alrea
On Mon, Jun 22, 2009 at 10:08 PM, Chris Ball wrote:
> Hi Gary,
>
> > Hmmm, how about when a class of kids first boot up and
> > _automatically_ connect to some random, unfiltered, strangers
> > open/public wifi next to the school, rather than following the
> > teachers instructions to attac
Chris Ball a écrit :
> I don't think I've ever been in a situation where connecting to an
> open access point would have displeased me, when it was the only
> connectivity available.
OK.
On the other hand, how much would you have been displeased to simply have to
explicitly click
on the open A
On Tue, Jun 23, 2009 at 08:38, Peter Robinson wrote:
>> >>> But, auto attach to any old public AP with no prior user selection?
>> >>> That's just asking for trouble...
>> >>
>> >> What trouble is that asking for?
>> >
>> > A very fair question:
>>
>> I think that Sugar should prioritiz
> >>> But, auto attach to any old public AP with no prior user selection?
> >>> That's just asking for trouble...
> >>
> >> What trouble is that asking for?
> >
> > A very fair question:
>
> I think that Sugar should prioritize what its user might want over
> what the potential wishes o
Hi Gary,
> Hmmm, how about when a class of kids first boot up and
> _automatically_ connect to some random, unfiltered, strangers
> open/public wifi next to the school, rather than following the
> teachers instructions to attach to an encrypted school AP running
> through a firewall
On 23 Jun 2009, at 02:11, Chris Ball wrote:
Hi Gary,
But, auto attach to any old public AP with no prior user selection?
That's just asking for trouble...
What trouble is that asking for?
A very fair question:
I think that Sugar should prioritize what its user might want over
what the po
Hi Gary,
>>> But, auto attach to any old public AP with no prior user selection?
>>> That's just asking for trouble...
>>
>> What trouble is that asking for?
>
> A very fair question:
I think that Sugar should prioritize what its user might want over
what the potential wishes of
On 23 Jun 2009, at 00:10, Benjamin M. Schwartz wrote:
> Gary C Martin wrote:
>> But, auto attach to any old public AP with no prior user selection?
>> That's just asking for trouble...
>
> What trouble is that asking for?
A very fair question:
1) Many Public APs do not provide internet access an
Gary C Martin wrote:
> But, auto attach to any old public AP with no prior user selection?
> That's just asking for trouble...
What trouble is that asking for?
--Ben
signature.asc
Description: OpenPGP digital signature
___
Sugar-devel mailing list
On 22 Jun 2009, at 15:44, Benjamin M. Schwartz wrote:
> Tomeu Vizoso wrote:
>> 2009/6/10 Benjamin M. Schwartz :
>>> Daniel Drake wrote:
And now the logic I want to implement, which is similar to that in
previous OLPC OS releases:
- First, attempt to connect to any known access point
Tomeu Vizoso wrote:
> On Mon, Jun 22, 2009 at 16:44, Benjamin M.
> Schwartz wrote:
>> Tomeu Vizoso wrote:
>>> 2009/6/10 Benjamin M. Schwartz :
Daniel Drake wrote:
> And now the logic I want to implement, which is similar to that in
> previous OLPC OS releases:
> - First, attempt to
On Mon, Jun 22, 2009 at 16:44, Benjamin M.
Schwartz wrote:
> Tomeu Vizoso wrote:
>> 2009/6/10 Benjamin M. Schwartz :
>>> Daniel Drake wrote:
And now the logic I want to implement, which is similar to that in
previous OLPC OS releases:
- First, attempt to connect to any known access p
Tomeu Vizoso wrote:
> 2009/6/10 Benjamin M. Schwartz :
>> Daniel Drake wrote:
>>> And now the logic I want to implement, which is similar to that in
>>> previous OLPC OS releases:
>>> - First, attempt to connect to any known access points that are in range
>>> using saved credentials. Always prefer
2009/6/10 Benjamin M. Schwartz :
> Daniel Drake wrote:
>> And now the logic I want to implement, which is similar to that in
>> previous OLPC OS releases:
>> - First, attempt to connect to any known access points that are in range
>> using saved credentials. Always prefer known APs to mesh.
>> - As
Daniel Drake wrote:
> And now the logic I want to implement, which is similar to that in
> previous OLPC OS releases:
> - First, attempt to connect to any known access points that are in range
> using saved credentials. Always prefer known APs to mesh.
> - As a fallback if those APs fail, or if no
Hi,
I'm looking to implement network selection logic in sugar-0.84 using the
NetworkManager D-Bus API to implement something similar to what was
present in NetworkManager-0.6 for OLPC's mesh device. (the logic is now
being moved out of NetworkManager into sugar)
My work in progress is:
NM-0.7 wit
18 matches
Mail list logo
