From: Hannes Frederic Sowa <hannes@stressinduktion•org>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6•org>
Cc: Erik Hugne <erik.hugne@ericsson•com>,
netdev@vger•kernel.org, YOSHIFUJI Hideaki <yoshfuji@wide•ad.jp>
Subject: Re: [IPv6] interface-local multicast escapes the local node
Date: Sun, 10 Feb 2013 00:08:06 +0100 [thread overview]
Message-ID: <20130209230806.GA16640@order.stressinduktion.org> (raw)
In-Reply-To: <5116595E.2080601@linux-ipv6.org>
On Sat, Feb 09, 2013 at 11:12:46PM +0900, YOSHIFUJI Hideaki wrote:
> Hi,
>
> Hannes Frederic Sowa wrote:
> > On Wed, Feb 06, 2013 at 05:54:15PM +0100, Hannes Frederic Sowa wrote:
> >> On Thu, Feb 07, 2013 at 12:24:14AM +0900, YOSHIFUJI Hideaki wrote:
> >>> NAK. I think we should select routes via loopback device here.
> >>
> >> Will try your idea, thanks.
> >
> > Does this patch look reasonable? Btw. i am pleased to see this kind of
> > things work out as expected most of the time (addrtype checking etc. all
> > in place). :)
> >
>
> Well, I rethink of what "interface-local" means.
>
> It seems applications will join ff01::/16%eth0 instead of ff01::/16%lo.
> If so, your original patch seems better. My bad, sorry.
No problem, will do. I have not checked carefully, but this would mean we have
to do changes to glibc to have a correct behaving getaddrinfo?
> Would you update original one, with minor modification that defers
> kfree_skb() after incrementing MIB, please?
Yes. Will send the patch tomorrow at the latest.
>
> If you think we should join ff01::{1,2} by default, you can send another
> patch for it. (BTW, why don't we join ff05::2, then? ;-))
Ok, I'll split it up. You are right about ff05::2, seems like the right thing
to do, somehow. I hope this won't impact any multicast routing daemons.
Thanks,
Hannes
next prev parent reply other threads:[~2013-02-09 23:08 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
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 [this message]
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=20130209230806.GA16640@order.stressinduktion.org \
--to=hannes@stressinduktion$(echo .)org \
--cc=erik.hugne@ericsson$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yoshfuji@linux-ipv6$(echo .)org \
--cc=yoshfuji@wide$(echo .)ad.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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