From owner-freebsd-ports@FreeBSD.ORG Tue Nov 13 00:43:54 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3F7616A468 for ; Tue, 13 Nov 2007 00:43:54 +0000 (UTC) (envelope-from fbsd06+QG=a6299a4d@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id 7989713C49D for ; Tue, 13 Nov 2007 00:43:54 +0000 (UTC) (envelope-from fbsd06+QG=a6299a4d@mlists.homeunix.com) Received: from mxout-04.mxes.net (mxout-04.mxes.net [216.86.168.179]) by turtle-in.mxes.net (Postfix) with ESMTP id D45701640E1 for ; Mon, 12 Nov 2007 19:21:37 -0500 (EST) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 8F81DD05BB for ; Mon, 12 Nov 2007 19:20:28 -0500 (EST) Date: Tue, 13 Nov 2007 00:20:26 +0000 From: RW To: freebsd-ports@freebsd.org Message-ID: <20071113002026.57b90cd9@gumby.homeunix.com.> In-Reply-To: <20071112140259.GA1046@straylight.m.ringlet.net> References: <20071108220658.7d657b47@gumby.homeunix.com.> <1194562755.1094.26.camel@ikaros.oook.cz> <20071112140259.GA1046@straylight.m.ringlet.net> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Stunnel not working X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 00:43:54 -0000 On Mon, 12 Nov 2007 16:02:59 +0200 Peter Pentchev wrote: > On Thu, Nov 08, 2007 at 11:59:15PM +0100, Pav Lucistnik wrote: > > RW p??e v ?t 08. 11. 2007 v 22:06 +0000: > > > > > Stunnel doesn't seem to be working correctly on my 6.2 desktop, > > > I'm getting the following in /var/log/messages, and I have no > > > stunnel process > [snip] > > > stunnel: LOG3[926:134660096]: local socket: Protocol not > > > supported (43) stunnel: warning: can't get client address: Bad > > > file descriptor > [snip] > > > > On my machines, I noticed 4.21 no longer understands domain names in > > connect statement of configuration file. > > > > Try replacing that secure.new.seasynews.com by it's IP. > > Could you try the attached patch? According to the stunnel > developers, it should fix the problem. > > It has been submitted to the portmgr@ team for commit approval. > I apologize for the apparently insufficient testing before the port > update to version 4.21. I tried it and it didn't solve my problem, but I rebuilt my kernel with IPv6 and now it works.