#9896 HIGH Not Tri: Ad-hoc network fails when XO goes into sleep

[Zarro Boogs per Child]

#9896: Ad-hoc network fails when XO goes into sleep
------------------------------------+---------------------------------------
           Reporter:  edmcnierney   |       Owner:                
               Type:  defect        |      Status:  new           
           Priority:  high          |   Milestone:  Not Triaged   
          Component:  not assigned  |     Version:  1.5-B3        
         Resolution:                |    Keywords:  network ad-hoc
        Next_action:  never set     |    Verified:  0             
Deployment_affected:                |   Blockedby:                
           Blocking:                |  
------------------------------------+---------------------------------------

Comment(by mikus):

 Don't know if this is pertinent - but here's another situation:

 1) Booted XO-1 (Gaiss, os10).  Started ad-hoc network from XO-1 Frame
 (rightmost) icon.[[BR]]
 2) Booted XO-1.5 (Murga, os62).  Clicked on ad-hoc network icon in XO-1,5
 Neighborhood View.  The XO-1.5 connected to the network and was assigned
 an IP address.[[BR]]
 3) Took ("before") olpc-log on XO-1.5.[[BR]]
 4) Powered off XO-1.[[BR]]
 5) The XO-1.5 still has the "connected" ad-hoc network icon in its
 Neighborhood View and in its Frame.[[BR]]
 6) Took ("after") olpc-log on XO-1.5.

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