To get around this problem, there are two solutions that I see:
1) Don't do multicasting for bonding devices
While this works (I've tested) some peple might call this a serious
2) Keep track of the slave's multicast list
This would require keeping a copy of the slave's pointer and restoring
it when the bonding
device is downed. Not sure if this would even work since the slave's
multicast list might
be stale by the time it is restored.
I'd like to get this fixed in the best possible way. What are your
folks comments in regard to the matter?
-- Jeff Golds firstname.lastname@example.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/