#3732 HIGH 9.1.0: arp broadcasts don't wake up autosuspended laptop

[Zarro Boogs per Child]

#3732: arp broadcasts don't wake up autosuspended laptop
-------------------------------------------+--------------------------------
           Reporter:  wad                  |       Owner:  cjb        
               Type:  defect               |      Status:  new        
           Priority:  high                 |   Milestone:  9.1.0      
          Component:  power manager (OHM)  |     Version:             
         Resolution:                       |    Keywords:  cjbfor9.1.0
        Next_action:  code                 |    Verified:  0          
Deployment_affected:                       |   Blockedby:  6993       
           Blocking:                       |  
-------------------------------------------+--------------------------------

Comment(by carrano):

 Replying to [comment:39 ashish]:
 [...]
 > Could you please confirm if the rule for IP 192.168.11.14 was
 > {{{
 > c0a80b0e at 20
 > }}}
 >  instead of
 > {{{
 > 0ca80b0e at 20
 > }}}
 >  (which is anyway incorrect)? I remmber we did verify this simple test.
 Thanks

 You're right, of course: c0, not 0c. Stupid mistake.

 Also, I repeated the tests that uncovered the bounding limit issue with
 good results.

     - iwpriv msh0 reset_wol_rule; iwpriv msh0 set_wol_rule "u ef at 40"
     will make the XO wake up for "ping -p ef" [OK]

     - iwpriv msh0 reset_wol_rule; iwpriv msh0 set_wol_rule "u ef at 60"
     will *not* make the XO wake up for "ping -p ef" [OK]

     - iwpriv msh0 reset_wol_rule; iwpriv msh0 set_wol_rule "u ef at 60
     && ef at 40" will *not* make the XO wake up for "ping -p ef" [OK]

     - iwpriv msh0 reset_wol_rule; iwpriv msh0 set_wol_rule "u ef at 40
     && ef at 60" will *not* make the XO wake up for "ping -p ef" [OK]


 So it seems that the "Boundary condition for WOL rule has been fixed".

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