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

Zarro Boogs per Child bugtracker at laptop.org
Fri May 30 22:57:31 EDT 2008


#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      
 Keywords:                   |    Verified:  0             
 Blocking:                   |   Blockedby:                
-----------------------------+----------------------------------------------
 Although not recommended, an XO connected to an AP can run salut.

 In fact, this always occurs when
 1)jabber is not set
 2)XO hasnt registered
 3)the AP has no internet connectivity

 Salut uses the msh0 interface, which is over the same channel as the AP
 connection.

 However, at 1cc the medialab AP is available in 2 channels (6,11).
 It happen that the XO switches from one to the other very frequently:
 ...
 02:40:38   2.437 GHz
 02:42:28   2.462 GHz
 02:51:08   2.437 GHz
 02:53:18   2.462 GHz
 02:59:47   2.437 GHz
 03:01:57   2.462 GHz
 03:06:18   2.437 GHz
 03:08:28   2.462 GHz
 03:12:48   2.437 GHz
 03:14:58   2.462 GHz
 ....

 Generally, when you switch channel in the mesh view, the avahi/salut XO
 list is cleared and refreshed.

 Now in this case, the switch occurs silently in the background, so the
 mesh view is clogged with unusable XOs continuously.

 Since the switching time is less than 5min,
 whereas the neighbourhood updates every 10min,
 the user does observe XOs leaving!

 *But* at 50% of the time he want be able to collaborate

 This may explain alot of collaborating trouble in the past.

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


More information about the Bugs mailing list