netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Elad Raz <eladr@mellanox.com>, Ido Schimmel <idosch@mellanox.com>,
	Jiri Pirko <jiri@mellanox.com>,
	Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev <netdev@vger.kernel.org>,
	Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: IGMP snooping, switchdev and local multicast receiver on br interface
Date: Fri, 14 Jul 2017 16:49:49 +0200	[thread overview]
Message-ID: <20170714144949.GG21743@lunn.ch> (raw)

Hi Folks

I've been testing IGMP snooping support with DSA, putting MDB entries
into the switch so that traffic only goes out ports where there has
been an interest indicated via IGMP. It mostly works, but i've come
across one use case which does not.

I have a multicast listener running on the host, performing a
setsockopt(IP_ADD_MEMBERSHIP) on the bridge interface. It is not an
unreasonable thing to want to do, e.g. a WiFi access point listening
to mDNS, or running other multicast protocols, a STB wanting to
receive a multicast video stream to display on the set, etc.

I'm not seeing any switchdev operations when the IP_ADD_MEMBERSHIP is
called. So there is no indication that the switch should add an MDB
entry to forward traffic to the host.

Im i missing something, or is this not implemented?

Thanks
	Andrew

             reply	other threads:[~2017-07-14 14:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 14:49 Andrew Lunn [this message]
2017-07-14 15:30 ` IGMP snooping, switchdev and local multicast receiver on br interface Vivien Didelot
2017-07-16  8:17   ` Yotam Gigi

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=20170714144949.GG21743@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=eladr@mellanox.com \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=vivien.didelot@savoirfairelinux.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).