From owner-freebsd-net@FreeBSD.ORG Sun Feb 11 16:25:00 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 EF6D616A406; Sun, 11 Feb 2007 16:24:59 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.freebsd.org (Postfix) with ESMTP id B01B913C4A7; Sun, 11 Feb 2007 16:24:59 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (t050096.ppp.asahi-net.or.jp [203.189.50.96]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 4F3597301D; Mon, 12 Feb 2007 01:25:04 +0900 (JST) Date: Mon, 12 Feb 2007 01:24:49 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Dimitry Andric In-Reply-To: <45CCF3ED.1090704@andric.com> 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> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII 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 16:25:00 -0000 >>>>> On Fri, 09 Feb 2007 23:21:33 +0100, >>>>> Dimitry Andric said: > Bruce A. Mah wrote: >> I've convinced myself that this problem needs to be tested in isolation >> (i.e. you have complete control over both ends of the tunnel) because >> incoming packets over the tunnel cause the host route to get added >> automatically if it wasn't there already. >> >> After reading the code and discussing this with a couple folks, I've >> managed to convince myself that 1.48.2.14 and 1.48.2.15 (and their >> analogues on HEAD) need to go away. I've committed diffs that back >> these out, and they solve the problem for me in my testing (which I've >> done with two VMs in isolation). The applicable revisions for nd6.c are >> 1.74 (HEAD) and 1.48.2.18 (RELENG_6). Updating up to (or beyond) these >> revisions should clear up the problem. > Confirmed. I've updated the machine on which I originally had this > problem to -STABLE as of today, and the problem has disappeared. I thought it was also planned to be incorporated to RELENG_6_2, right? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp