From owner-freebsd-net@FreeBSD.ORG Fri Dec 31 16:20:26 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E81D5106564A for ; Fri, 31 Dec 2010 16:20:26 +0000 (UTC) (envelope-from kevlo@kevlo.org) Received: from ns.kevlo.org (kevlo.org [220.128.136.52]) by mx1.freebsd.org (Postfix) with ESMTP id 800688FC12 for ; Fri, 31 Dec 2010 16:20:26 +0000 (UTC) Received: from [127.0.0.1] (kevlo@kevlo.org [220.128.136.52]) by ns.kevlo.org (8.14.3/8.14.3) with ESMTP id oBVGKKrR025567; Sat, 1 Jan 2011 00:20:21 +0800 (CST) From: Kevin Lo To: "Bjoern A. Zeeb" In-Reply-To: <20101231161337.P6126@maildrop.int.zabbadoz.net> References: <200912071020.nB7AK77I023054@freefall.freebsd.org> <4B1CDEE5.6080507@incunabulum.net> <3e2b8dd90912070305t6ffc08a6gf7acd8890d028854@mail.gmail.com> <4B1D07C3.6090005@incunabulum.net> <3e2b8dd90912080114x31d962acqf2c8a360e7b5a83d@mail.gmail.com> <4B1E1EF0.8040503@incunabulum.net> <3e2b8dd90912080155s544a7a50j17882b35f1343750@mail.gmail.com> <4B1E2574.8010704@incunabulum.net> <3e2b8dd90912080247s247bd878ud9fe4b234ff83f84@mail.gmail.com> <3e2b8dd90912090037v6c8e13e1v869471d4e03ecfd5@mail.gmail.com> <1293809938.2126.12.camel@nsl> <20101231161337.P6126@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset="UTF-8" Date: Sat, 01 Jan 2011 00:20:19 +0800 Message-ID: <1293812419.2126.14.camel@nsl> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: kern/138666: [multicast] [panic] not working multicast through igmpproxy X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2010 16:20:27 -0000 Bjoern A. Zeeb wrote: > On Fri, 31 Dec 2010, Kevin Lo wrote: > > > This issue is easily reproduced on 9.0 -CURRENT as well. > > I got kernel panic after running mrouted, igmpproxy, or xorp. > > Was it the same as reported in the PR? Yes.