From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: Corey Melanson <cmelanson@blackberry.com>
Cc: "bridge@lists.linux-foundation.org" <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] Force IGMP membership
Date: Sat, 12 Nov 2016 12:52:13 +0100 [thread overview]
Message-ID: <20161112115213.GG3151@otheros> (raw)
In-Reply-To: <E5B11A06AD89DB429345609918715652FBF2FF58@XMB121CNC.rim.net>
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
next prev parent reply other threads:[~2016-11-12 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 20:44 [Bridge] Force IGMP membership Corey Melanson
2016-11-12 11:52 ` Linus Lüssing [this message]
2016-11-16 17:24 ` Corey Melanson
2016-11-21 21:44 ` Linus Lüssing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161112115213.GG3151@otheros \
--to=linus.luessing@c0d3.blue \
--cc=bridge@lists.linux-foundation.org \
--cc=cmelanson@blackberry.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).