#4402 NORM Never A: In link-local(salut) an XO shows in neighbour view but cannot share with

Zarro Boogs per Child bugtracker at laptop.org
Tue Oct 23 05:37:17 EDT 2007


#4402: In link-local(salut) an XO shows in neighbour view but cannot share with
------------------------------+---------------------------------------------
  Reporter:  yani             |       Owner:  sjoerd        
      Type:  defect           |      Status:  new           
  Priority:  normal           |   Milestone:  Never Assigned
 Component:  telepathy-salut  |     Version:                
Resolution:                   |    Keywords:                
  Verified:  0                |  
------------------------------+---------------------------------------------

Comment(by sjoerd):

 ``cannot be shared with'' is a little bit unclear to me. Does it mean that
 if one XO shares it's activity others don't see it or if you see one XO
 share it's activity you can't join it ? Or that something goes completely
 wrong ?

 In general if you see people in the mesh view for which avahi-browse logs
 ``cannot resolve'', this means that you avahi-daemon still has the info
 that the presence was there cached. But it can't retrieve the extra info
 (Either because the node has gone without saying bye or there is a lot of
 packet loss).

 Salut used to drop the presence of people for which it couldn't resolve
 the extra information, but this seemed to give a lot of problems in the
 mesh (people appearing and disappearing all the time). So as a workaround
 we switched to only dropping presence iff all info about a node has gone.
 Which has the downside the nodes that are really gone can still appear on
 the mesh view for some time (specifically when they didn't send a proper
 mdns bye packet or when that was dropped).

 It's impossible to fully get rid of the issue of having xo's that aren't
 there anymore in the meshview (As it's impossible to instantanously know
 when a node has gone).  With the current mdns usage i can potentially make
 the a bit window smaller if needed though (but it will always be in the
 order of at least several minutes)..

-- 
Ticket URL: <https://dev.laptop.org/ticket/4402#comment:1>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system



More information about the Bugs mailing list