#4616 NORM Update.: Mesh doesn't resume from suspend on reciept of multicast packets

[Zarro Boogs per Child]

#4616: Mesh doesn't resume from suspend on reciept of multicast packets
----------------------------------+-----------------------------------------
  Reporter:  gnu                  |       Owner:  cjb                              
      Type:  defect               |      Status:  new                              
  Priority:  normal               |   Milestone:  Update.1                         
 Component:  power manager (OHM)  |     Version:  Development build as of this date
Resolution:                       |    Keywords:                                   
  Verified:  0                    |  
----------------------------------+-----------------------------------------

Comment(by mbletsas):

 Excuse our ignorance, we are kind of slow here...

 We can currently wake up the host upon receipt of a frame addressed to its
 unicast address, a broadcast address and a range of anycast addresses. You
 are also asking to wakeup the host when certain multicast frames are
 received.

 The purpose of that would be to wake up a subset of hosts and not all of
 the hosts present in the local mesh network (as a wakeup on broadcast
 would do).

 Every XO right now listens to 4 link-level multicast layer-2 addresses:
 3 of them are common among all of them and 1 is derived from its own MAC
 address.

 The piece that I am missing, is how are we going to wake up specific XOs
 using multicast frames (without keeping track of them a priori to the
 wakeup request).

 M.

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