From owner-freebsd-java@FreeBSD.ORG Mon Nov 17 05:48:07 2003 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2134D16A4CE for ; Mon, 17 Nov 2003 05:48:07 -0800 (PST) Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19F8A43FBD for ; Mon, 17 Nov 2003 05:48:06 -0800 (PST) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Mon, 17 Nov 2003 13:47:51 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 1ALjir-0003ua-00; Mon, 17 Nov 2003 13:47:21 +0000 Date: Mon, 17 Nov 2003 13:47:20 +0000 (GMT) From: Jan Grant X-X-Sender: cmjg@mail.ilrt.bris.ac.uk To: Jean-Baptiste Quenot In-Reply-To: <20031117132001.GA96272@watt.intra.caraldi.com> Message-ID: References: <20031111160600.GA95499@misty.eyesbeyond.com> <20031117125107.GA96039@watt.intra.caraldi.com> <20031117132001.GA96272@watt.intra.caraldi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Jan Grant cc: freebsd-java@freebsd.org Subject: Re: 1.4.2 patchset 5 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2003 13:48:07 -0000 On Mon, 17 Nov 2003, Jean-Baptiste Quenot wrote: > * Jean-Baptiste Quenot: > > > * Greg Lewis: > > > > > I am pleased to be able to announce 1.4.2 patchset 5. > > > > It seems that the IP sockets do not work anymore. > > After issuing: > > # sysctl net.inet6.ip6.v6only=0 > > It works again... > > Why are IPv4 addresses like 127.0.0.1 no more recognized? It sounds like a combination of an IPv6-aware server and a client that's trying an IPv4 "localhost" first. There are potential problems associated with the "standard" v4-in-v6 addressing which the sysctl in question avoids, by turning off that operation. The last month or so has seen the default for this sysctl spasm back and forwards because there's angst about turning it on, which is arguable the "right thing" from a security standpoint, and turning it off, which is "the right thing" from the current state of the RFCs. Until the RFCs are amended, your fix works. You might try (as a hack) ensuring that the IPv6 localhost address (assuming "localhost" is causing the problems) appears before the IPv4 one in your /etc/hosts. Or alternatively flip the switch as you have done. jan -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ I shave with Occam's Razor.