#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:            |  
-----------------------+----------------------------------------------------
Changes (by ashish):

 * cc: rchokshi at marvell.com (added)


Comment:

 I did the following to confirm wakeup with two XOs, running 703 patched
 kernel (mesh_mcast_v2.patch) firmware 22.p10.
 XO1

 {{{
 ethtool -s msh0 wol m
 ip maddr
 echo mem > /sys/power/state
 }}}
 on XO2 populated static ARP entries for the multicast addresses listed by
 ip maddr command above.
 e.g.,

 {{{
 arp -s 10.0.0.144 01:00:5e:00:00:fb
 ping 10.0.0.144 -c1
 }}}

 And it waked up XO1.

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