Date: Thu, 08 Feb 2007 17:49:34 -0800 From: "Bruce A. Mah" <bmah@freebsd.org> To: Dimitry Andric <dimitry@andric.com> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org, jhay@freebsd.org Subject: Re: IPv6 over gif(4) broken in 6.2-RELEASE? Message-ID: <45CBD32E.40005@freebsd.org> In-Reply-To: <45B676A2.5090009@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>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF6089CF940E21F2E6AA5806B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable If memory serves me right, Dimitry Andric wrote: > Bruce A. Mah wrote: > I mean that it may be that between -RELEASE and -STABLE, other things > have changed, e.g. network rc scripts, /sbin/route itself, etc, which > may also influence this behaviour. I'm sure more than only nd6.c > changed. :) The testing I did doesn't require any of that stuff, only a kernel, a shell, and ifconfig(8). I'm not aware of anything relevant. (As one of the RE types, I do follow commit mails pretty closely, especially during and just after a release cycle.) > However, for me, with the whole system at -STABLE (as of Jan 11), I > verified the following results again just now: >=20 > nd6.c rev state > --------- ----- > 1.48.2.12 works > 1.48.2.13 works > 1.48.2.14 works > 1.48.2.15 works > 1.48.2.16 doesn't work 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. Testing reports from people who were having problems would be appreciated= =2E Bruce. --------------enigF6089CF940E21F2E6AA5806B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFy9My2MoxcVugUsMRAp5NAKC7+ik0mksLdVyNSUPaB/vlRuYVjgCg5wWD 4bgeibxwy1LGUijmNSAF4zo= =4R4l -----END PGP SIGNATURE----- --------------enigF6089CF940E21F2E6AA5806B--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45CBD32E.40005>