#7135 NORM Never A: NetworkManager eth0 sporadic (at least few times a day) dropout

[Zarro Boogs per Child]

#7135: NetworkManager eth0 sporadic (at least few times a day) dropout
-----------------------------+----------------------------------------------
 Reporter:  garycmartin      |       Owner:  dcbw          
     Type:  defect           |      Status:  new           
 Priority:  normal           |   Milestone:  Never Assigned
Component:  network manager  |     Version:  Update.1      
 Keywords:                   |    Verified:  0             
 Blocking:                   |   Blockedby:                
-----------------------------+----------------------------------------------
 While connected to a single AP (D-Link DSL-G604T) with just basic WEP
 encryption in a low noise environment (one other wireless laptop and a
 couple of other visible APs), !NetworkManager appears to 'randomly' decide
 to drop and then reattach the eth0 connection with the following log (all
 @ same second):

 {{{
  <info> eth0: link timed out.
  <info> SWITCH: found better connection 'eth0/myAP' than current
 connection 'eth0/myAP'.
         same_ssid=1, have_link=0
  <info> Will activate connection 'eth0/myAP'
  <info> Device eth0 activation scheduled...
  <info> Deactivating device eth0.
 }}}

 It then goes on to drop everything, and then reattach it all again (lots
 of log). Now I'd probably never notice this twitch, except for the fact
 that even though it knows the WEP password (it auto connects at boot-up
 with no intervention) it pops up the modal logon dialogue for the AP and
 makes me re-enter the security details again.

 This one's been bugging me for a long time. It's happened to some extent
 with every build version I've used (70x's and joyrides). If I have the XO
 (B4) running for a few hours or so there's a good chance this'll hit.
 It'll even happen several time in a row within 5 min of each other, on
 occasion.

 My first though about the error reported, is why does !NetworkManager not
 do a simple test and check to see if the 'better connection' device is
 actually the same as device it's already connected to? Then it can avoid
 the whole 'take it down, bring it back up again' merry-go-round, which
 would also avoid the need for re-authentication glitch.

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