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

 Ashish,

 You are right. I assumed that wake on multicast was activated because the
 node wakes to pings at 224.0.0.1, but it was a bad assumption. Once
 "ethtool -s msh0 wol um" was issued the suspended node began responding as
 expected, waking to:

 - multicast pings at 224.0.0.1

 - the inclusion of a new node in the mesh

 - the sharing of an activity

 Actually as presence information is periodic, the nodes wakes up every few
 minutes for them (independent of the conditions above).

 I believe this is the expected behavior. Any one?

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