From: Stephen Hemminger <stephen@networkplumber.org>
To: Madhu Challa <challa@noironetworks.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 net-next 2/2] Enable configuring multicast group join / leave at IP level.
Date: Sun, 15 Mar 2015 12:43:17 -0700 [thread overview]
Message-ID: <20150315124317.6a01a542@urahara> (raw)
In-Reply-To: <1425493810-2537-3-git-send-email-challa@noironetworks.com>
On Wed, 4 Mar 2015 10:30:10 -0800
Madhu Challa <challa@noironetworks.com> wrote:
> Joining multicast group on ethernet level via "ip maddr" command would
> not work if we have an Ethernet switch that does igmp snooping since
> the switch would not replicate multicast packets on ports that did not
> have IGMP reports for the multicast addresses.
>
> Linux vxlan interfaces created via "ip link add vxlan" have the group option
> that enables then to do the required join.
>
> By extending ip address command with option "autojoin" we can get similar
> functionality for openvswitch vxlan interfaces as well as other tunneling
> mechanisms that need to receive multicast traffic.
>
> example:
> ip address add 224.1.1.10/24 dev eth5 autojoin
> ip address del 224.1.1.10/24 dev eth5
Applied, but please update manual pages as well.
next prev parent reply other threads:[~2015-03-15 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 18:30 [PATCH iproute2 net-next 0/2] Extend ip address command to enable multicast group join/leave on IP level Madhu Challa
2015-03-04 18:30 ` [PATCH iproute2 net-next 1/2] Header rebase for IFA_F_MCAUTOJOIN Madhu Challa
2015-03-15 19:42 ` Stephen Hemminger
2015-03-04 18:30 ` [PATCH iproute2 net-next 2/2] Enable configuring multicast group join / leave at IP level Madhu Challa
2015-03-15 19:43 ` Stephen Hemminger [this message]
2015-03-16 17:59 ` Madhu Challa
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=20150315124317.6a01a542@urahara \
--to=stephen@networkplumber.org \
--cc=challa@noironetworks.com \
--cc=netdev@vger.kernel.org \
/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