#3732 HIGH 8.2.1: 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:  8.2.1
          Component:  power manager (OHM)  |     Version:       
         Resolution:                       |    Keywords:       
        Next_action:  code                 |    Verified:  0    
Deployment_affected:                       |   Blockedby:  6993 
           Blocking:                       |  
-------------------------------------------+--------------------------------

Comment(by carrano):

 I am having trouble setting the wol filter to wake up the XO on the
 receiving of arp requests destined to its IP address.

 In this example, the XO has eth0 address 192.168.11.14 and is set to
 sleep.

 This is a captured frame that should wake up the XO:

 {{{
 0000  00 00 18 00 ee 58 00 00  10 02 9e 09 a0 00 ac 9c   .....X.. ........
 0010  46 00 00 10 4d 7d 34 63  08 02 00 00 ff ff ff ff   F...M}4c ........
 0020  ff ff 00 16 01 84 2b 0f  00 17 c4 0d 5e 11 30 d8   ......+. ....^.0.
 0030  aa aa 03 00 00 00 08 06  00 01 08 00 06 04 00 01   ........ ........
 0040  00 17 c4 0d 5e 11 c0 a8  0b 08 00 00 00 00 00 00   ....^... ........
 0050  c0 a8 0b 0e 4d 7d 34 63
 }}}


 As per my understanding of the signature based wol filter, the rule to
 achieve so would be:

 {{{
 iwpriv eth0 set_wol_filter "b 00000806 at 4 && 0ca80b0e at 20"
 }}}

 Which *seems* to work, but it does not do what we want, as I explain
 bellow:

 The following works (wakes up the XO)
 {{{
 iwpriv eth0 set_wol_filter "b 00000806 at 4"
 }}}

 While the following doesn't work (does not wake up the XO as it should)
 {{{
 iwpriv eth0 set_wol_filter "b 0ca80b0e at 20"
 }}}

 Javier,

 Apart from the above, I still suspect that there is an issue with the
 evaluation of the expression with AND (&&), since:

 The following works:
 {{{
 iwpriv eth0 set_wol_filter "b 00000806 at 4 && 0ca80b0e at 20"
 }}}

 While the following does not:
 {{{
 iwpriv eth0 set_wol_filter "b 0ca80b0e at 20 && 00000806 at 4"
 }}}

 It seems that if the first term is true, the second is not evaluated. In
 short, 'iwpriv eth0 set_wol_filter "b 00000806 at 4 && 0ca80b0e at 20"' is
 actually waking up the XO to *any* ARP request (tests confirmed this).

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