From: Pekka Savola <email@example.com>
To: "Alejandro Riveira Fernández" <firstname.lastname@example.org>
Cc: Todd Hayton <email@example.com>,
Subject: Re: IPv6 multicast forwarding
Date: Fri, 24 Oct 2008 13:12:29 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1070 bytes --]
On Fri, 24 Oct 2008, Alejandro Riveira Fernández wrote:
>> Let me apologize in advance for the length of this message - it is long!
>> I'm trying to test out IPv6 multicast forwarding on a 2.6.26 kernel
>> and I'm getting some strange values for the upcall messages from the
>> kernel. My code is below, but to give an overview, my setup is as
>> sender ------ ff15::1 -----> [eth1] linux 2.6.26 [eth0] ------> ...
Maybe this isn't the bug you're looking for but you shouldn't be using
ff1x multicast addresses in a test like this; ff1x means that the
multicast group is of "interface-local scope" and it isn't useful for
multicast forwarding. So the kernel might be correct in not
installing multicast forwarding state for a group address like this
(but if it's a conscious decision, maybe the failure mode should be
better). See S 2.7 of RFC4291.
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
next prev parent reply other threads:[~2008-10-24 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 22:11 IPv6 multicast forwarding Todd Hayton
2008-10-24 9:10 ` Alejandro Riveira Fernández
2008-10-24 10:12 ` Pekka Savola [this message]
2008-10-24 13:06 ` Todd Hayton
2008-10-26 10:26 ` Pekka Savola
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 12:04 ipv6 " Youngmin Kim
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).