Hi,
This bug was fixed upstream in version 4.27. Stunnel now tries to connect
all IP addresses returned by the resolver.
$ stunnel3 -D 7 -f -c -r hydra.gt.owl.de:443
[cut]
2010.07.02 11:25:27 LOG6[19463:3075217072]: connect_blocking: connecting
2001:6f8:1173:2::1:443
2010.07.02 11:25:27 LOG7[19463:3075217072]: connect_blocking: s_poll_wait
2001:6f8:1173:2::1:443: waiting 10 seconds
2010.07.02 11:25:37 LOG3[19463:3075217072]: connect_blocking: s_poll_wait
2001:6f8:1173:2::1:443: timeout
2010.07.02 11:25:37 LOG7[19463:3075217072]: FD=6 in non-blocking mode
2010.07.02 11:25:37 LOG6[19463:3075217072]: connect_blocking: connecting
195.71.99.218:443
2010.07.02 11:25:37 LOG7[19463:3075217072]: connect_blocking: s_poll_wait
195.71.99.218:443: waiting 10 seconds
2010.07.02 11:25:37 LOG5[19463:3075217072]: connect_blocking: connected
195.71.99.218:443
2010.07.02 11:25:37 LOG5[19463:3075217072]: Service stunnel connected
remote server from 207.192.69.165:44998
Best regards,
Michal Trojnara
upstream maintainer
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
