From owner-freebsd-net@freebsd.org Mon Nov 30 09:17:21 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68152A3C65F for ; Mon, 30 Nov 2015 09:17:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 31369145B for ; Mon, 30 Nov 2015 09:17:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAU9HL1u044519 for ; Mon, 30 Nov 2015 09:17:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 204831] mld_v2 listener report does not report all active groups to the router Date: Mon, 30 Nov 2015 09:17:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.3-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2015 09:17:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204831 --- Comment #3 from Andrey V. Elsukov --- (In reply to scheffler from comment #2) > are you sure you are reading the traces correctly? > > 1.) Maximum Response Code (Delay) is set to 10000 (10s) by the router. Which > is the default value given by RFC3810. Ah, yes, you are right. I read it incorrectly. > 2.) The Query Intervall (QQIC) is set to the (default) value of 125, but the > unit of this value is seconds. > > The router is a Cisco 2811 running IOS 15.1-4.M10, the latest IOS for this > platform supported by Cisco. The router has a basic MC configuration, no > timer values have been changed from the default. The behaviour starts as > soon as I enable 'IPv6 multicast-routing'. I also reproduced the behaviour > on a 2901. > > Your description of 4-packet burts makes sense - I was wondering about the > 500ms delay between packet groups. The 510 groups need 8 packets to report. > So, the kernel should stop after the second packet group (having reported > all 510 groups to the router for this reporting period). However, it does > not! Yes it looks strange to me too. But I think it should repeat these packets once again due to QRV equal to 2. > The trace clearly shows that it keeps on reporting the same groups over and > over again until it suddenly starts losing groups from the report. > So to me it looks like 2 bugs: > 1.) Reporting should stop after having reported all 510 groups. > 2.) We should not lose groups from the report which are still active. > > In the meantime I found a Linux-Box to run my MC code on and connected it to > the very same router. Here the behaviour is very different. The router sends > a General Query very 125 seconds. Linux reports the 510 groups (using 8 > packets) and stays silent until it receives the next General Query. It also > never reports less than the full 510 groups. > If you think it helps, I can also attach the Linux-trace. Yes, it is interesting. Thanks. -- You are receiving this mail because: You are the assignee for the bug.