Date: Tue, 13 Nov 2007 00:20:26 +0000 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Stunnel not working 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Nov 2007 16:02:59 +0200 Peter Pentchev <roam@ringlet.net> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071113002026.57b90cd9>