#4402 HIGH First D: In link-local(salut) an XO shows in neighbour view but cannot share with

[Zarro Boogs per Child]

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

Comment(by yani):

 Replying to [comment:1 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 ?

 I didnt express it properly. Assume xo1,xo2,xo3,xo4 share activities.
 xo5's screen shows all laptops, but does not show activities of xo2 for
 example. instead the _presence._ list gave a "cannot resolve" error for
 xo2. But, if xo2 shares it is fine.

 > 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)..
 >
 ok i see.

 in fact i binded two issues in one, because i didnt know how the thing
 worked.
 the two issues:
 1. some xos leave the mesh, but still show, which as i see it is done on
 purpose, and related to 3657.
 2. some xos that are alive and sharing, but their activities is unresolved
 ONLY TO SOME other xos. But i dont have the logs for thatone.

 Unfortunately, i mixed two different things. I will post a different
 ticket when I have the proper log files.

 thanks all for your replies

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