netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: Erik Hugne <erik.hugne@ericsson.com>,
	netdev@vger.kernel.org,
	YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
	erik.hugne@ericsson.com
Subject: Re: [IPv6] interface-local multicast escapes the local node
Date: Thu, 07 Feb 2013 00:24:14 +0900	[thread overview]
Message-ID: <5112759E.90104@linux-ipv6.org> (raw)
In-Reply-To: <20130206121248.GC10290@order.stressinduktion.org>

Hannes Frederic Sowa wrote:
> On Wed, Feb 06, 2013 at 09:49:49AM +0100, Erik Hugne wrote:
>> It seems that packets sent to interface-local scoped multicast
>> addresses (ff01::/16) escape out on the network.
>> According to RFC4291 (section 2.7):
>>     Interface-Local scope spans only a single interface on a node
>>     and is useful only for loopback transmission of multicast.
>>
>> Example program here:
>> https://gist.github.com/Hugne/4721151
> 
> Fixing the output path should be relatively straightforward, please test
> the following patch.
> 
> Looking at the input path, I think there is also no input protection
> for ff01::/16 addresses from the wire if you bind such an address.
> 
> [PATCH net-next] ipv6: don't let node/interface scoped multicast traffic escape on the wire
> 
> Reported-by: Erik Hugne <erik.hugne@ericsson.com>
> Cc: Erik Hugne <erik.hugne@ericsson.com>
> Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
> Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
> ---
>  net/ipv6/ip6_output.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/net/ipv6/ip6_output.c b/net/ipv6/ip6_output.c
> index 906b7e6..b21ff3d 100644
> --- a/net/ipv6/ip6_output.c
> +++ b/net/ipv6/ip6_output.c
> @@ -118,6 +118,12 @@ static int ip6_finish_output2(struct sk_buff *skb)
>  			}
>  		}
>  
> +		if (IPV6_ADDR_MC_SCOPE(&ipv6_hdr(skb)->daddr) <=
> +		    IPV6_ADDR_SCOPE_NODELOCAL) {
> +			kfree_skb(skb);
> +			return 0;
> +		}
> +
>  		IP6_UPD_PO_STATS(dev_net(dev), idev, IPSTATS_MIB_OUTMCAST,
>  				skb->len);
>  	}
> 

NAK.  I think we should select routes via loopback device here.

--yoshfuji

  parent reply	other threads:[~2013-02-06 15:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  8:49 [IPv6] interface-local multicast escapes the local node Erik Hugne
2013-02-06 12:12 ` Hannes Frederic Sowa
2013-02-06 13:07   ` Erik Hugne
2013-02-06 13:49     ` Hannes Frederic Sowa
2013-02-06 15:06       ` Erik Hugne
2013-02-06 15:12         ` Hannes Frederic Sowa
2013-02-06 15:32       ` YOSHIFUJI Hideaki
2013-02-06 16:04         ` Hannes Frederic Sowa
2013-02-06 16:18           ` Eric Dumazet
2013-02-06 16:25             ` Hannes Frederic Sowa
2013-02-06 16:49           ` YOSHIFUJI Hideaki
2013-02-07  1:00             ` Hannes Frederic Sowa
2013-02-07  7:28               ` Erik Hugne
2013-02-07 15:41                 ` YOSHIFUJI Hideaki
2013-02-06 15:24   ` YOSHIFUJI Hideaki [this message]
2013-02-06 16:54     ` Hannes Frederic Sowa
2013-02-09 12:10       ` Hannes Frederic Sowa
2013-02-09 14:12         ` YOSHIFUJI Hideaki
2013-02-09 23:08           ` Hannes Frederic Sowa
2013-02-10  9:59           ` Hannes Frederic Sowa
2013-02-10 10:57             ` YOSHIFUJI Hideaki
2013-02-10 15:32           ` Hannes Frederic Sowa
2013-02-10 18:42             ` YOSHIFUJI Hideaki
2013-02-10 18:49               ` Hannes Frederic Sowa
2013-02-11 11:13                 ` [PATCH RFC 1/2] ipv6: introdcue __ipv6_addr_needs_scope_id and ipv6_iface_scope_id helper functions Hannes Frederic Sowa
2013-02-11 13:36                   ` YOSHIFUJI Hideaki
2013-02-11 11:13                 ` [PATCH RFC 2/2] ipv6: use newly introduced helper functions __ipv6_addr_needs_scope_id and ipv6_iface_scope_id Hannes Frederic Sowa
2013-02-09 15:50         ` [IPv6] interface-local multicast escapes the local node YOSHIFUJI Hideaki

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=5112759E.90104@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=erik.hugne@ericsson.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;
as well as URLs for NNTP newsgroup(s).