• A
    bonding: fix broken multicast with round-robin mode · a2fd940f
    Andy Gospodarek 提交于
    Round-robin (mode 0) does nothing to ensure that any multicast traffic
    originally destined for the host will continue to arrive at the host when
    the link that sent the IGMP join or membership report goes down.  One of
    the benefits of absolute round-robin transmit.
    
    Keeping track of subscribed multicast groups for each slave did not seem
    like a good use of resources, so I decided to simply send on the
    curr_active slave of the bond (typically the first enslaved device that
    is up).  This makes failover management simple as IGMP membership
    reports only need to be sent when the curr_active_slave changes.  I
    tested this patch and it appears to work as expected.
    
    Originally reported by Lon Hohberger <lhh@redhat.com>.
    Signed-off-by: NAndy Gospodarek <andy@greyhouse.net>
    CC: Lon Hohberger <lhh@redhat.com>
    CC: Jay Vosburgh <fubar@us.ibm.com>
    Signed-off-by: NJay Vosburgh <fubar@us.ibm.com>
    Signed-off-by: NDavid S. Miller <davem@davemloft.net>
    a2fd940f
bond_main.c 133.1 KB