#6818 NORM Never A: Driver does not set link level multicast addresses into firmware when ip address assigned to mesh interface

[Zarro Boogs per Child]

#6818: Driver does not set link level multicast addresses into firmware when ip
address assigned to mesh interface
-----------------------+----------------------------------------------------
  Reporter:  shailen   |       Owner:  dwmw2         
      Type:  defect    |      Status:  new           
  Priority:  normal    |   Milestone:  Never Assigned
 Component:  wireless  |     Version:                
Resolution:            |    Keywords:                
  Verified:  0         |    Blocking:                
 Blockedby:            |  
-----------------------+----------------------------------------------------

Comment(by gnu):

 Yes, the real test will be how it integrates in the whole system:  With
 the presence service running, with "ethtool -s msh0 wol uma", and with
 auto-suspend:  Will we drop the unicast or multicast packet that wakes us
 up (#6528), or will it actually reach the application that's awaiting it?

 And, secondarily, can we stay suspended long enough to save power?  Or
 will the application level multicast traffic be so constant that we always
 wake a few seconds after we suspend (in which case we need to fix the
 applications so they aren't so chatty)?

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