From: Andrew Lunn <andrew@lunn.ch>
To: Callum Sinclair <callum.sinclair@alliedtelesis.co.nz>
Cc: dsahern@kernel.org, nikolay@nvidia.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linus.luessing@c0d3.blue
Subject: Re: [PATCH 1/1] net: Allow all multicast packets to be received on a interface.
Date: Thu, 17 Jun 2021 16:18:26 +0200 [thread overview]
Message-ID: <YMtZspsYH0wd9SVf@lunn.ch> (raw)
In-Reply-To: <20210617095020.28628-2-callum.sinclair@alliedtelesis.co.nz>
On Thu, Jun 17, 2021 at 09:50:20PM +1200, Callum Sinclair wrote:
> To receive IGMP or MLD packets on a IP socket on any interface the
> multicast group needs to be explicitly joined. This works well for when
> the multicast group the user is interested in is known, but does not
> provide an easy way to snoop all packets in the 224.0.0.0/8 or the
> FF00::/8 range.
>
> Define a new sysctl to allow a given interface to become a IGMP or MLD
> snooper. When set the interface will allow any IGMP or MLD packet to be
> received on sockets bound to these devices.
Hi Callum
What is the big picture here? Are you trying to move the snooping
algorithm into user space? User space will then add/remove Multicast
FIB entries to the bridge to control where mulitcast frames are sent?
In the past i have written a multicast routing daemon. It is a similar
problem. You need access to all the join/leaves. But the stack does
provide them, if you bind to the multicast routing socket. Why not use
that mechanism? Look in the mrouted sources for an example.
Andrew
next prev parent reply other threads:[~2021-06-17 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 9:50 [PATCH 0/1] Create multicast snooping sysctl option Callum Sinclair
2021-06-17 9:50 ` [PATCH 1/1] net: Allow all multicast packets to be received on a interface Callum Sinclair
2021-06-17 12:33 ` Linus Lüssing
2021-06-18 0:07 ` Callum Sinclair
2021-06-17 14:18 ` Andrew Lunn [this message]
2021-06-18 0:09 ` Callum Sinclair
2021-06-17 19:31 ` kernel test robot
2021-06-17 20:17 ` kernel test robot
2021-06-17 21:14 ` kernel test robot
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=YMtZspsYH0wd9SVf@lunn.ch \
--to=andrew@lunn.ch \
--cc=callum.sinclair@alliedtelesis.co.nz \
--cc=dsahern@kernel.org \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.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).