Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 29 Sep 2002 13:21:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 29 Sep 2002 13:21:31 -0400 Received: from mail.scram.de ([195.226.127.117]:50377 "EHLO mail.scram.de") by vger.kernel.org with ESMTP id ; Sun, 29 Sep 2002 13:21:29 -0400 Date: Sun, 29 Sep 2002 19:26:37 +0200 (CEST) From: Jochen Friedrich X-X-Sender: jochen@alpha.bocc.de To: Andi Kleen cc: jbradford@dial.pipex.com, , Subject: Re: v2.6 vs v3.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1809 Lines: 43 Hi Andi, > Actually current IPv6 is stable and has been for a long time, it's just not > completely standards compliant (but still quite usable for a lot of people) For end systems (no router) with static IPv6 definitions this seems to be true. However, for machines which use autoconfiguration (stateless as there isn't a usable IPv6 capable DHCP server AFAIK) or act as routers, the current state of the implementation of the default route can best be described as buggy. (Autoconfigured machines seem to loose their default route after some time, e.g.). Also, there could be a better communication between the kernel and the resolver to check if if IPv6 is available, at all. Currently, on IPv4 only kernels, we often see dialogs like this: ssh -v mail.scram.de OpenSSH_3.4p1 Debian 1:3.4p1-2.1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: ssh_connect: needpriv 0 debug1: Connecting to mail.scram.de [3ffe:400:470:1::1:1] port 22. socket: Address family not supported by protocol debug1: Connecting to mail.scram.de [195.226.127.117] port 22. debug1: Connection established. So IPv6 is returned by the resolver even though IPv6 isn't available in the kernel. The default of the resolver options should be dependent on the presence or absence of IPv6 in the currently running kernel IMHO. Finally, IPv6 sockets which also communicate over IPv4 using mapped addresses are considered bad nowadays ;-) Cheers, --jochen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/