#6463 BLOC Never A: Invites don't work in simple mesh mode

[Zarro Boogs per Child]

#6463: Invites don't work in simple mesh mode
------------------------------+---------------------------------------------
  Reporter:  wad              |       Owner:  Collabora         
      Type:  defect           |      Status:  new               
  Priority:  blocker          |   Milestone:  Never Assigned    
 Component:  telepathy-other  |     Version:                    
Resolution:                   |    Keywords:  mesh collaboration
  Verified:  0                |    Blocking:                    
 Blockedby:                   |  
------------------------------+---------------------------------------------

Comment(by wad):

 Replying to [comment:12 bemasc]:

 > Maybe.  The log in #6774 says "Connecting failed: No route to host".
 I'm not sure if that's consistent with the observed behavior here, in
 which TCP connections fail but multicast sharing continues to work fine.
 >
 > Where is TCP implemented in this stack?
 >

 It won't be hard to reproduce once we get the collaboration testbed back
 up, but inability to establish a route for TCP (unicast) connections is
 one of the symptoms of a congested mesh.

 One way of thinking about it is that multicast information goes out as a
 single frame, broadcast to everyone.   For a unicast connection to be
 established, the broadcast happens, then (while everyone is echoing the
 broadcast) the receiver sends unicast frames back to the sender.  THEN
 they can get about the business of actually starting to establish the TCP
 connection.  Many more frames are involved...

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