> -----Original Message----- > From: Linus Lüssing [mailto:linus.luessing@xxxxxxxxx] > Sent: Saturday, November 12, 2016 6:52 AM > To: Corey Melanson <cmelanson@xxxxxxxxxxxxxx> > Cc: bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx > Subject: Re: Force IGMP membership > > On Fri, Nov 04, 2016 at 08:44:48PM +0000, Corey Melanson wrote: > > After the live migration, multicast traffic to 239.236.15.150 stops as > expected. If I try to manually add the multicast group membership: > > # bridge mdb add dev br.128 port vnet3 grp 239.236.15.150 temp > > # bridge mdb list | grep vnet3 > > dev onebr.128 port vnet3 grp 239.236.15.150 temp > > > > The multicast traffic does not resume until the VM sends a IGMP > membership report after receiving an IGMP query from the switch, which > takes too long most of the time (over a minute). > > Hm, sounds weird. Have you verified with tcpdump that > on <brport-multicast-in> you see the according frame and on vnet3 > it is missing then? > > Does it make a difference when instead of adding a group > explicitly to mark the whole port as a router port? > > ($ echo 2 > /sys/class/net/vnet3/brport/multicast_router > - not a solution proposal but just to narrow things down) > > Regards, Linus Hi Linus, During these tests I have another VM on the same bridge/vlan joined to the same multicast group, and it is receiving/sending multicast traffic, so tcpdump shows that the upstream bond vlan interface sees the multicast group traffic. It seems the traffic is just is not being sent to the VM when it is manually joined via: $ bridge mdb add dev onebr.128 port vnet3 grp 239.236.15.150 temp When I set the vnet port as a router: $ echo 2 > /sys/class/net/vnet3/brport/multicast_router The VM starts receiving multicast traffic immediately. Please let me know if there is any other information that would be helpful. Thank you, Corey
