[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170714144949.GG21743@lunn.ch>
Date: Fri, 14 Jul 2017 16:49:49 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Elad Raz <eladr@...lanox.com>, Ido Schimmel <idosch@...lanox.com>,
Jiri Pirko <jiri@...lanox.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Cc: netdev <netdev@...r.kernel.org>,
Vivien Didelot <vivien.didelot@...oirfairelinux.com>,
Florian Fainelli <f.fainelli@...il.com>
Subject: IGMP snooping, switchdev and local multicast receiver on br interface
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
Powered by blists - more mailing lists