#7144 HIGH Never A: Serious issue with medialab AP and salut

[Zarro Boogs per Child]

#7144: Serious issue with medialab AP and salut
------------------------------+---------------------------------------------
  Reporter:  yani             |       Owner:  Collabora     
      Type:  defect           |      Status:  new           
  Priority:  high             |   Milestone:  Never Assigned
 Component:  telepathy-salut  |     Version:  Update.1      
Resolution:                   |    Keywords:                
  Verified:  0                |    Blocking:                
 Blockedby:                   |  
------------------------------+---------------------------------------------
Changes (by yani):

 * cc: kim (removed)
 * cc: kimquirk (added)


Comment:

 Replying to [comment:2 mbletsas]:

 > This brings us back to another long-standing request that we should be
 able to bind the collaboration stack with specific interfaces.

 what does this mean? that we collaborate with eth0 when associated to an
 AP?

 In g1g1 scenario with a home AP and a couple of XOs under the same roof,
 salut is the only way of private communication.
 (unless the parents build a home jabber)

 also in an under-the-tree topology, it is possible that 1-2 kids might
 find an AP to associate with.
 again if they wanna share with each other, they would need salut.
 so the ones associated with the AP would have AP/salut simultaneously.

 Of course in these "home" scenarios the XOs would be probably associated
 to a single-channel AP(unless the g1g1 kids leave in a castle with 5
 floors!)

 So it useful(or essential) that eth0 association would coexist with a msh0
 collaboration.

-- 
Ticket URL: <http://dev.laptop.org/ticket/7144#comment:3>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system