All of lore.kernel.org
 help / color / mirror / Atom feed
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] net: Allow any address multicast join for IP sockets
Date: Tue, 6 Jul 2021 15:28:03 +0200	[thread overview]
Message-ID: <YORaY83GiD56/su0@lunn.ch> (raw)
In-Reply-To: <20210706011548.2201-1-callum.sinclair@alliedtelesis.co.nz>

On Tue, Jul 06, 2021 at 01:15:47PM +1200, Callum Sinclair wrote:
> For an application to receive all multicast packets in a range such as
> 224.0.0.1 - 239.255.255.255 each multicast IP address has to be joined
> explicitly one at a time.
> 
> Allow the any address to be passed to the IP_ADD_MEMBERSHIP and
> IPV6_ADD_MEMBERSHIP socket option per interface. By joining the any
> address the socket will receive all multicast packets that are received
> on the interface. 
> 
> This allows any IP socket to be used for IGMP or MLD snooping.

Do you really want all multicast frames, or just IGMP and MLD
messages?

What is the advantage of this solution over using pcap with a filter
which matches on multicast?

      Andrew

  parent reply	other threads:[~2021-07-06 13:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  1:15 [PATCH] net: Allow any address multicast join for IP sockets Callum Sinclair
2021-07-06  1:15 ` Callum Sinclair
2021-07-06  5:18   ` kernel test robot
2021-07-06  5:18     ` kernel test robot
2021-07-06 13:28 ` Andrew Lunn [this message]
2021-07-07  2:00   ` Callum Sinclair
2021-07-07 14:56     ` Andrew Lunn
2021-07-06 19:01 kernel test robot
2021-07-07  7:26 ` [kbuild] " Dan Carpenter
2021-07-07  7:26 ` Dan Carpenter

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=YORaY83GiD56/su0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.