From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Sat, 12 Nov 2016 12:52:13 +0100 From: Linus =?utf-8?Q?L=C3=BCssing?= Message-ID: <20161112115213.GG3151@otheros> Reply-To: bridge@lists.linux-foundation.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Subject: Re: [Bridge] Force IGMP membership List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Corey Melanson Cc: "bridge@lists.linux-foundation.org" 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 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