#6872 NORM -: 703 and 702 builds - network manager keeps trying to connect to mesh network even after associated w/ AP

[Zarro Boogs per Child]

#6872: 703 and 702 builds - network manager keeps trying to connect to mesh
network even after associated w/ AP
-------------------------------+--------------------------------------------
   Reporter:  BryanBerry       |       Owner:  dcbw
       Type:  defect           |      Status:  new 
   Priority:  normal           |   Milestone:      
  Component:  network manager  |     Version:      
 Resolution:                   |    Keywords:      
Next_action:  never set        |    Verified:  1   
  Blockedby:                   |    Blocking:      
-------------------------------+--------------------------------------------
Changes (by mtd):

  * next_action:  => never set


Comment:

 Replying to [comment:1 wad]:
 > Believed to be an similar problem to #5459
 >
 > We aren't sure that NM is actually trying to make the connections here.

 If the mesh icon that's flashing changes, I think NM must be doing
 something.  The feedback/state of the wireless icon is probably wrong, and
 that's #5459, #6944, and/or #6995.  But mesh icons "continually flashing
 round-robin style" is different.  The only thing I've seen that's similar-
 ish is if I 1) associate with an AP successfully; 2) click on its icon in
 the Neighborhood view again, triggering a re-association; 3) re-
 association fails; 4) NM state machine starts searching for meshes again;
 5) 60-120 seconds later (20 seconds * 3 channels * 2, or * 1) NM will try
 to connect to the AP again, or just start a link-local mesh (I can't
 remember which I've seen but it's certainly one of them :)).  This could
 look in the frame/Neighborhood view like what Bryan's seen.

 Bryan, have you seen this recently?  If you happen to see it and can grab
 some logs, that'd be great.  I know this is really old now, and I've done
 some work on #2866, #6995, and #6944 that should make this less of a
 problem in the future, and we've got NM 0.7 coming up which should cause
 us to revisit that code as well, so...not sure what you want to do on
 this, if anything.

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