From owner-freebsd-stable@FreeBSD.ORG Fri Feb 9 22:21:36 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7FFB916A412; Fri, 9 Feb 2007 22:21:36 +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 3EF1F13C4B4; Fri, 9 Feb 2007 22:21:36 +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 0BDE2B80E; Fri, 9 Feb 2007 23:21:33 +0100 (CET) Message-ID: <45CCF3ED.1090704@andric.com> Date: Fri, 09 Feb 2007 23:21:33 +0100 From: Dimitry Andric User-Agent: Thunderbird 2.0pre (Windows/20070129) MIME-Version: 1.0 To: "Bruce A. Mah" 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> In-Reply-To: <45CBD32E.40005@freebsd.org> X-Enigmail-Version: 0.94.1.2 Content-Type: text/plain; charset=windows-1250 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, jhay@freebsd.org Subject: Re: IPv6 over gif(4) broken in 6.2-RELEASE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2007 22:21:36 -0000 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. Thanks!