From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, aviad.yehezkel5@gmail.com
Subject: Re: [Bugme-new] [Bug 13443] New: Scope 1 in multicast addresses in IPV6 should be node local
Date: Wed, 3 Jun 2009 14:40:31 -0700 [thread overview]
Message-ID: <20090603144031.2945f24d.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-13443-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Wed, 3 Jun 2009 16:06:29 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13443
>
> Summary: Scope 1 in multicast addresses in IPV6 should be node
> local
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.27
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV6
> AssignedTo: yoshfuji@linux-ipv6.org
> ReportedBy: aviad.yehezkel5@gmail.com
> Regression: No
>
>
> I think scope 1 in multicast addresses in IPV6 should be node local (according
> to all the documentation + rfc I found on the web) and therefore pkt's with
> such destination address should not go on the wire.
> When I try to send a udp pkt with sock_dgram to such ipv6 address with scope 1
> I see the pkt is going on the wire and I can catch it on the other side by
> joining this multicast address.
next parent reply other threads:[~2009-06-03 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-13443-10286@http.bugzilla.kernel.org/>
2009-06-03 21:40 ` Andrew Morton [this message]
2009-06-04 4:37 ` [Bugme-new] [Bug 13443] New: Scope 1 in multicast addresses in IPV6 should be node local David Miller
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=20090603144031.2945f24d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aviad.yehezkel5@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--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).