From owner-freebsd-current Thu Apr 3 07:32:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA27831 for current-outgoing; Thu, 3 Apr 1997 07:32:04 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA27787 for ; Thu, 3 Apr 1997 07:31:55 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.5/8.8.5) id KAA04612; Thu, 3 Apr 1997 10:29:08 -0500 (EST) Date: Thu, 3 Apr 1997 10:29:08 -0500 (EST) From: Garrett Wollman Message-Id: <199704031529.KAA04612@khavrinen.lcs.mit.edu> To: Andrzej Bialecki Cc: freebsd-current@freebsd.org Subject: IPv6 && -current In-Reply-To: References: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk < said: > What is the status of IPv6 implementation under -current? I'd be probably > interested in setting up a machine and a tunnel to 6bone, so I would > gladly use FreeBSD for this, if it's possible... I am aware of two implementations out there, and the unfortunate truth is that both of them suck, in different ways. (Although at least one of them, I am told, is getting significantly better stylistically.) Until this situation changes a bit more (or we find someone interested in doing an IPv6 implementation that obeys style(9) and isn't altogether bletcherous), there should not be IPv6 code in the -current kernel. However, having said that, I certainly see no bar to making whatever changes in the rest of the kernel are necessary to support the drop-in of one of these stacks (probably the NRL one). -GAWollman --