[Trac #951] Unable to ping some 1-hop neighbors in a mesh

[Zarro Boogs per Child]

#951: Unable to ping some 1-hop neighbors in a mesh
----------------------+-----------------------------------------------------
 Reporter:  jcardona  |        Owner:  jcardona
     Type:  defect    |       Status:  assigned
 Priority:  blocker   |    Milestone:  BTest-3 
Component:  wireless  |   Resolution:          
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by jcardona):

  * status:  new => assigned

Comment:

 We have found the cause for this problem.  An internal message queue was
 improperly dimensioned and it was causing the corruption of the
 destination address
 that was sent in RREQs.  The consequence of this was that at some point
 the mesh interface would lose the ability to discover new routes.

 This was a bug introduced in the latest release, when we implemented
 deferred route discovery.

 Currently testing the fix on meshy1 and meshy2, on the OLPC testbed.  As
 soon as the fix is confirmed, we will make a new development release.

-- 
Ticket URL: <http://dev.laptop.org/ticket/951#comment:1>
One Laptop Per Child <http://laptop.org/>