bridge.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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: Mon, 21 Nov 2016 22:44:52 +0100	[thread overview]
Message-ID: <20161121214452.GA10227@otheros> (raw)
In-Reply-To: <E5B11A06AD89DB429345609918715652FBF54303@XMB121CNC.rim.net>

On Wed, Nov 16, 2016 at 05:24:36PM +0000, Corey Melanson wrote:
> Please let me know if there is any other information that would be helpful.
> 
> Thank you,
> Corey

Hi Corey,

I tried to reproduce your issue in a similar VM setup, but was
unsuccessful so far. For me things seem to work with 4.9-rc3
kernels.


What I tried:
            
    [vm-s] -- [vm-br] == [vm-r]

vm-s and vm-br are connected via one interface pair. vm-br and
vm-r share two interfaces.

On vm-r's 1st interface there is socat running which joins
239.236.15.150 [1]. On vm-r's 2nd interface there is a tcpdump
listening for UDP packets.
-> vm-br with a "bridge mdb show dev br0" shows one entry for
   239.236.15.150 for the 1st interface towards vm-r

vm-s sends multicast traffic to 239.236.15.150 via socat [2].
-> Is received successfully in socat on vm-r,
   tcpdump on 2nd interface stays empty


Then I did not do the full interface hotplugging, but instead
typed your "bridge mdb add..." command on vm-br for the 2nd
interface towards vm-r.

Finally I redid the socat transmission on vm-s. And vm-r received
this packet successfully both in socat running on its 1st
interface and in tcpdump running on its 2nd one.


Could you retry with a recent kernel, too, Corey?

Regards, Linus


[1]: $ socat -u UDP4-RECV:1234,reuseaddr,ip-add-membership="239.236.15.150:ens3" -
[2]: $ socat - UDP4-DATAGRAM:"239.236.15.150:1234"

      reply	other threads:[~2016-11-21 21:44 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
2016-11-16 17:24   ` Corey Melanson
2016-11-21 21:44     ` Linus Lüssing [this message]

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=20161121214452.GA10227@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).