Date: Tue, 5 May 2009 15:24:47 +0530 From: Srinidhi Gopal <srinidhigopal@gmail.com> Subject: [users:01188] Reg Multicast Routing support in IPv6 Ready - Core Logo Phase 2 To: users@tahi.org Message-Id: <3f9723c40905050254u5277d69h5b26e91234c40149@mail.gmail.com> In-Reply-To: <3f9723c40904290414sea02118l8849bd8be6dd1825@mail.gmail.com> References: <3f9723c40904220232y15295ad6r3340ea059346660f@mail.gmail.com> <20090423102844.4612ac74.akisada@tahi.org> <3f9723c40904290414sea02118l8849bd8be6dd1825@mail.gmail.com> X-Mail-Count: 01188Hi, I am using mrd6-0.9.6.tar.gz package to enable mcast on the target router (Linux 2.6). Also i have applied the following kernel patch "*patch*-*linux2 *.*6.9*-*ipv6*-*mforwarding*-0.1d" to our kernel. Out of 7 multicast tests, 6 of them are passing expect the one under ICMPv6 Category - *Test v6LC.5.1.4: Packet Too Big Message Generation (Routers Only) - Part B * I observe that the mrd package does the entire multicast routing in the user space. The Kernel stack is used only for socket operations and the control never flows into ip6_mr_forward function in the kernel for mcast operations. The idea behind IPv6 Ready logo is to test the kernel IPv6 stack of the target. If mrd package doesn'ty make use of the kernel for multicast forwarding, and does everything in the userspace, I am not clear as what is the use of executing these test cases under Mcast routing category using this package. Kindly clarify. Thanks in advance. -- Regards, Srinidhi Gopal1188_2.html (attatchment)(tag is disabled)