Date: Mon, 22 Jan 2007 11:16:44 +0100 From: Dimitry Andric <dimitry@andric.com> To: "Bruce A. Mah" <bmah@freebsd.org> Cc: freebsd-net@freebsd.org, Hiroki Sato <hrs@freebsd.org>, freebsd-stable@freebsd.org, jhay@freebsd.org Subject: Re: IPv6 over gif(4) broken in 6.2-RELEASE? Message-ID: <45B48F0C.9090809@andric.com> In-Reply-To: <45B421D4.2050008@freebsd.org> References: <20070120162936.GA18104@tomcat.kitchenlab.org> <20070121.020741.59649277.hrs@allbsd.org> <45B251A5.4000209@freebsd.org> <45B3CA56.4040106@andric.com> <45B421D4.2050008@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce A. Mah wrote: >> and later I found out it was caused by commit 1.48.2.16: >> http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031853.html > > This isn't consistent with what I'm finding. For one thing, rev. > 1.48.2.16 of nd6.c isn't in 6.2-RELEASE but I saw the problem there > anyways. Also, that's not the change I made to my local sources to get > my gif(4) tunnel working. Are you sure about this? :-) I'm following -STABLE, and 1.48.2.16 is in there. Since it was committed on 29 Nov, I suspected it would end up in -RELEASE, but apparently not. :) I explicitly tried reverting just this one commit, and for me it solved the problem (i.e. the automagical addition of needed routing entries). So for you, reverting the combination of 1.48.2.14 and .15 works? Maybe there is something else involved too, for example the route command itself? I'll have to experiment a bit further, I guess.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45B48F0C.9090809>