Re: Possible stunnel 5.43 bug ?
James Brown <[email protected]>
| Newsgroups | gmane.network.stunnel.user |
|---|---|
| Message-ID | <[email protected]> |
On 14 Nov 2017, at 11:33 pm, Bezspam <[email protected]> wrote: > > Hello, > I use stunnel on FreeBSD 11.1. I install it from ports. Yesterday I updated to stunnel 5.43. However it stopped working. I investigated the problem and found the issue- instead on all network interfaces, "accept" listens on 127.0.0.1 : > > sockstat -4 > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS > stunnel stunnel 43945 7 tcp4 127.0.0.1:2222 *:* > stunnel stunnel 43945 8 tcp4 127.0.0.1:3128 *:* > stunnel stunnel 43945 9 tcp4 127.0.0.1:8080 *:* > stunnel stunnel 43945 10 tcp4 127.0.0.1:1616 *:* > > A workaround is to modify "accept = 0.0.0.0:3128" explicitly to listen on 0.0.0.0. > Is this a bug or expected behaviour? > > Best regards, > Bez Spam I had the same issue after upgrading to 5.43 - nothing could connect. No information about connections was in the log. It started up OK, but nothing happened. Didn’t get to investigate it like you did Bez, I had to quickly go to back to version 5.42 to get things working again. Compiled same way, same configuration - only difference was upgraded to version 5.43. Mac OS X 10.7.5 James. _______________________________________________ stunnel-users mailing list [email protected] https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
smime.p7s
(application/x-pkcs7-signature, 8.3 KB) - not displayed