[lkml]   [2012]   [Mar]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH net V4] bonding: send igmp report for its master
    From: Weiping Pan <>
    Date: Sun, 18 Mar 2012 11:23:27 +0800

    > Liang Zheng( found that in the following topo,
    > bonding does not send igmp report when we trigger a fail-over of bonding.
    > eth0--
    > |-- bond0 -- br0
    > eth1--
    > modprobe bonding mode=1 miimon=100 resend_igmp=10
    > ifconfig bond0 up
    > ifenslave bond0 eth0 eth1
    > brctl addbr br0
    > ifconfig br0 up
    > brctl addif br0 bond0
    > Add into a multicast group, like,
    > then trigger a fali-over in bonding.
    > You can see that parameter "resend_igmp" does not work.
    > The reason is that when we add br0 into a multicast group,
    > it does not propagate multicast knowledge down to its ports.
    > If we choose to propagate multicast knowledge down to all ports for bridge,
    > then we have to track every change that is done to bridge, and keep a backup
    > for all ports. It is hard to track, I think.
    > Instead I choose to modify bonding to send igmp report for its master.
    > Changelog:
    > V2: correct comments
    > V3: move this check into bond_resend_igmp_join_requests()
    > V4: only send igmp reports if bond is enslaved to a bridge
    > Signed-off-by: Weiping Pan <>


     \ /
      Last update: 2012-03-19 23:09    [W:0.043 / U:3.216 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site