#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 gnu):

 "Wake up on multicast" is ALREADY "wake up on certain multicasts".  The
 kernel loads in a set of multicast addresses that the chip should be
 listening for.  If a multicast comes along that isn't in that set, don't
 listen for it and don't wake up for it.  (Most chips do this in hardware.)
 This is totally standard on every Ethernet chip made, by every vendor.

 If you do "/sbin/ip maddr" it will list you the (link level, IPv4 and
 IPv6) multicast addresses that each interface is listening to.  What gets
 loaded into the chip is the link level addresses, which are the 802.11 MAC
 addresses that correspond to each of those higher level addresses.

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