#9236 NORM Not Tri: (8.2.1) Reconnect to WEP AP is not immediate after suspend/resume

Zarro Boogs per Child bugtracker at laptop.org
Fri Feb 6 00:31:50 EST 2009


#9236: (8.2.1) Reconnect to WEP AP is not immediate after suspend/resume
----------------------+-----------------------------------------------------
 Reporter:  mikus     |                 Owner:  mbletsas                         
     Type:  defect    |                Status:  new                              
 Priority:  normal    |             Milestone:  Not Triaged                      
Component:  wireless  |               Version:  Development build as of this date
 Keywords:            |           Next_action:  never set                        
 Verified:  0         |   Deployment_affected:                                   
Blockedby:            |              Blocking:                                   
----------------------+-----------------------------------------------------
 (staging-26).  Had a connection to a wireless (WEP) AP.  Closed the XO's
 lid.  After opening the lid, did not have a connection.  Got impatient,
 took "noresume" olpc-log.

 Rebooted; the XO automatically connected to the AP.  Captured 'ifconfig'
 to file "before".  Closed the XO's lid; after a while re-opened lid.
 Waited.  Seemingly a long time afterward, the XO prompted me for the AP's
 key.  When I gave it the key, the XO reconnected to the AP.  Took "resume"
 olpc-log; ifconfig (to file "after") shows state same as before the
 shutdown/resume.

 [[BR]]Seems to me there were two things wrong:  (1) It should not take
 minutes after a resume for a wireless connection to be re-established;
 (2) Asking the user for the WEP key after a 'suspend/resume' seems like
 too much of a hassle.

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


More information about the Bugs mailing list