[Sugar-devel] Sugar + OLPC mesh network selection logic

[Benjamin M. Schwartz]

Tomeu Vizoso wrote:
> On Mon, Jun 22, 2009 at 16:44, Benjamin M.
> Schwartz<bmschwar at fas.harvard.edu> wrote:
>> Tomeu Vizoso wrote:
>>> 2009/6/10 Benjamin M. Schwartz <bmschwar at fas.harvard.edu>:
>>>> 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 APs are available or if
>>>>> we've never connected to any (e.g. on first boot), try the mesh.
>>>> I'm not quite clear on your exact intention here.  I'd just like to
>>>> suggest that unknown unencrypted infrastructure APs get higher priority
>>>> than mesh.
>>> Even if the user never connected to that AP before?
>> Yes.  I suspect that even the pay-for-access APs in internet cafes and
>> airports still allow link-local connections for free, and it will likely
>> be much faster than the mesh.  It also provides the best chance of getting
>> an internet connection.
> 
> And there aren't security risks?

I can't think of any.  If the mesh is on the same frequency as the AP,
then the AP will hear you whether or not you are subscribed to it.  All
forms of 802.11 are completely vulnerable to eavesdropping, jamming, or
packet forgery at Layer 1.  If you want security, you have to use
encryption either way.

--Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
Url : http://lists.sugarlabs.org/archive/sugar-devel/attachments/20090622/1c66df4c/attachment.pgp