From: "Todd Hayton" <todd.hayton@gmail.com> To: "Pekka Savola" <pekkas@netcore.fi> Cc: "Alejandro Riveira Fernández" <ariveira@gmail.com>, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: IPv6 multicast forwarding Date: Fri, 24 Oct 2008 09:06:49 -0400 [thread overview] Message-ID: <50a66e370810240606ncb3dcd6gc949b734b1dcf488@mail.gmail.com> (raw) In-Reply-To: <alpine.LRH.2.00.0810241307360.1106@netcore.fi> On Fri, Oct 24, 2008 at 6:12 AM, Pekka Savola <pekkas@netcore.fi> wrote: > 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 >>> follows: >>> >>> 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. > Hey there, thanks for the response! I may be misinterpreting the RFC but I thought ff15::1 was a site-local address. As in I break down ff15::1 as follows - 0xff : identifies the address as multicast 0x15 : 4-bits flags and 4-bits scope where flags = 0x1 meaning that the T bit is set as this address is not a permanently assigned address scope = 0x5 indicating site-local scope Todd H > -- > 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 13:07 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-23 22:11 Todd Hayton 2008-10-24 9:10 ` Alejandro Riveira Fernández 2008-10-24 10:12 ` Pekka Savola 2008-10-24 13:06 ` Todd Hayton [this message] 2008-10-26 10:26 ` Pekka Savola -- strict thread matches above, loose matches on Subject: below -- 2003-07-25 12:04 ipv6 " Youngmin Kim
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=50a66e370810240606ncb3dcd6gc949b734b1dcf488@mail.gmail.com \ --to=todd.hayton@gmail.com \ --cc=ariveira@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=pekkas@netcore.fi \ --subject='Re: IPv6 multicast forwarding' \ /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
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).