From owner-freebsd-current Mon Nov 2 22:53:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26939 for freebsd-current-outgoing; Mon, 2 Nov 1998 22:53:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from SIMULTAN.CH (eunet-gw.simultan.ch [194.191.191.82] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26929 for ; Mon, 2 Nov 1998 22:53:37 -0800 (PST) (envelope-from tseidmann@simultan.ch) Received: from simultan.ch (wsaltis-053.SIMULTAN.CH [192.92.128.53]) by SIMULTAN.CH (8.9.1a/8.9.1) with ESMTP id HAA13991; Tue, 3 Nov 1998 07:53:19 +0100 (CET) Message-ID: <363EA85E.8CB9A118@simultan.ch> Date: Tue, 03 Nov 1998 07:53:18 +0100 From: Thomas Seidmann X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Sebastian Lederer CC: current@FreeBSD.ORG Subject: Re: IPv6 in -current References: <199811012217.OAA16854@mordred.cs.ucla.edu> <363CE849.B76F70FF@simultan.ch> <363DF9C6.45C26C7C@bonn-online.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sebastian Lederer wrote: > FWIW, the last time I tried INRIA IPv6 (about four months ago), it broke > some userland IPv4 stuff. I had some NIS problems/crashes, also NFS export > control lists and /etc/lpd.hosts didn't work anymore. KAME IPv6 does not > have these problems (but INRIA's kernel code might be more stable). I encuntered problems with NFS exports from a INRIA IPv6 enable machine during the time of the relaease for 2.2.5-RELEASE (about 6 moths ago). No problems with NIS nor hosts.lpd, however (YMMV). The above mentioned problems are gone in the present release according to my experiences. Regards, Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message