netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: opurdila@ixiacom.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next PATCH] ip: fix mc_loop checks for tunnels with multicast outer addresses
Date: Wed, 06 Jan 2010 20:37:18 -0800 (PST)	[thread overview]
Message-ID: <20100106.203718.180097165.davem@davemloft.net> (raw)
In-Reply-To: <201001041248.26095.opurdila@ixiacom.com>

From: Octavian Purdila <opurdila@ixiacom.com>
Date: Mon, 4 Jan 2010 12:48:25 +0200

> On Monday 04 January 2010 07:58:55 you wrote:
> 
>> This won't compile with IPV6 disabled.  Switch closing brace is
>> erroneously inside of the ifdef test.
>> 
> 
> Oops... Here is a new version:
> 
> [PATCH] ip: fix mc_loop checks for tunnels with multicast outer addresses
> 
> When we have L3 tunnels with different inner/outer families
> (i.e. IPV4/IPV6) which use a multicast address as the outer tunnel
> destination address, multicast packets will be loopbacked back to the
> sending socket even if IP*_MULTICAST_LOOP is set to disabled.
> 
> The mc_loop flag is present in the family specific part of the socket
> (e.g. the IPv4 or IPv4 specific part).  setsockopt sets the inner
> family mc_loop flag. When the packet is pushed through the L3 tunnel
> it will eventually be processed by the outer family which if different
> will check the flag in a different part of the socket then it was set.
> 
> Signed-off-by: Octavian Purdila <opurdila@ixiacom.com>

Applied to net-2.6, thanks!

      reply	other threads:[~2010-01-07  4:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 20:01 [net-next PATCH] ip: fix mc_loop checks for tunnels with multicast outer addresses Octavian Purdila
2010-01-04  5:58 ` David Miller
2010-01-04 10:48   ` Octavian Purdila
2010-01-07  4:37     ` David Miller [this message]

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=20100106.203718.180097165.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=opurdila@ixiacom.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).