This is a discussion on Re: [stunnel-users] almost working within the Stunnel Users forums, part of the Networking and Network Related category; Please send me the output of netstat -tunap. Thanks > -----Original Message----- > From: Tom Allison [mailto:tom@tacocat.net] &...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Please send me the output of netstat -tunap.
Thanks > -----Original Message----- > From: Tom Allison [mailto:tom@tacocat.net] > Sent: 15 October 2007 03:15 AM > To: Craig Retief > Cc: stunnel-users@mirt.net > Subject: Re: [stunnel-users] almost working > > Craig Retief wrote: > >> netstat -ltp shows inetd is listening to port 993. > > > > If inetd is listening on port 993 then stunnel will not be able to > bind to > > that port since inetd has already bind to it. > > > > If you will only be connecting to the inetd via stunnel then I > recommend > > that you change your listening port for inetd to something else than > 993 on > > the inetd config itself and restart inetd. Then you change your > stunnel conf > > to reflect this. > > > > As I understood it, I was using inetd to start the stunnel session to > connection > from 993 to 143. > > > 143 works. I've already tested that completely. > > As a maybe related issue. If I start stunnel from the /etc/init.d > script from > debian -- it fails calling for a pid= to be defined. As you can see > from my > conf file, pid= is already defined. _______________________________________________ stunnel-users mailing list stunnel-users@mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users |