From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 18:29:30 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DDC4516A400; Sun, 11 Feb 2007 18:29:30 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (tensor.andric.com [213.154.244.69]) by mx1.freebsd.org (Postfix) with ESMTP id 9887513C481; Sun, 11 Feb 2007 18:29:30 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from [192.168.0.3] (kilgore.lan.dim [192.168.0.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTP id 3165CB80E; Sun, 11 Feb 2007 19:29:27 +0100 (CET) Message-ID: <45CF6089.3040700@andric.com> Date: Sun, 11 Feb 2007 19:29:29 +0100 From: Dimitry Andric User-Agent: Thunderbird 2.0pre (Windows/20070210) MIME-Version: 1.0 To: =?UTF-8?B?SklOTUVJIFRhdHV5YSAvIOelnuaYjumBlOWTiQ==?= References: <20070120162936.GA18104@tomcat.kitchenlab.org> <20070121.020741.59649277.hrs@allbsd.org> <45B251A5.4000209@freebsd.org> <45B3CA56.4040106@andric.com> <45B421D4.2050008@freebsd.org> <45B48F0C.9090809@andric.com> <45B63C3E.9010808@freebsd.org> <45B676A2.5090009@andric.com> <45CBD32E.40005@freebsd.org> <45CCF3ED.1090704@andric.com> In-Reply-To: X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "Bruce A. Mah" , freebsd-stable@freebsd.org, jhay@freebsd.org, freebsd-net@freebsd.org Subject: Re: IPv6 over gif(4) broken in 6.2-RELEASE? 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: Sun, 11 Feb 2007 18:29:31 -0000 JINMEI Tatuya / =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote: >> Confirmed. I've updated the machine on which I originally had this >> problem to -STABLE as of today, and the problem has disappeared. >=20 > I thought it was also planned to be incorporated to RELENG_6_2, right? I'm not sure if non-security related fixes are considered for release branches. Also, there's a workaround mentioned on the 6.2 errata page, under "Known Issues": http://www.freebsd.org/releases/6.2R/errata.html Then again, it's really up to the release engineering team whether they deem this critical enough. :)