[stunnel-users] Failover behavior with stunnel
Michal.Trojnara at mirt.net
Sun Nov 15 20:58:38 CET 2015
-----BEGIN PGP SIGNED MESSAGE-----
On 15.11.2015 11:58, Thireus wrote:
> 1. I would like to know if there is a way to use failover with two
> servers with two different set of TLS cert/key.
No. Both client and server certificates are currently set way before
stunnel connects the target.
I guess what you really need is client certificate selection based on
the list of acceptable issuers sent by the stunnel server, because
each of your stunnel servers expects client certificates issued by a
separate CA. Am I right?
Client certificate autoselection currently works on Windows with the
CAPI engine. I have also added a new TODO item to implement client
certificate autoselection for certificates/keys stored in PEM files:
Alternatively, you may reconfigure your stunnel servers to accept
client certificates issued by the same CA.
> 2. On the same topic, I would like to know if there is an option
> that could open the local port (accept) only when the connection
> (connect) is established?
> The problem I'm facing is that I use a PAC profile with failover on
> several stunnel entries: "return PROXY 127.0.0.1:4441; PROXY
> 127.0.0.1:4442; PROXY 127.0.0.1:4443;".
Did you mean:
return "PROXY 127.0.0.1:4441; PROXY 127.0.0.1:4442; PROXY 127.0.0.1:4443
You are trying establish end-to-end failover across two (in fact
three, including connection between the stunnel server and the HTTP
proxy) separate TCP connections. It is not possible without a
> 3. Is there another way to tweak stunnel behavior when a remote
> server is down?
You could write a heartbeat service to periodically initiate short
connections to the remote services, and then reconfigure stunnel
accordingly. Still, this is a crude workaround and not the proper
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the stunnel-users