Reputation: 163
I know that STunnel can be set up as either server or client with the "client = no" or "client = yes" lines in the config file. Is there a way for a machine to be BOTH a server and client?
Upvotes: 6
Views: 4183
Reputation: 129
[client]
client = yes
accept = 7777
connect = 127.0.0.1:7777
"accept" will act as server
"connect" will act as client
[server]
accept = 7777
connect = 127.0.0.1:7777
"accept" will act as client
"connect" will act as server
Upvotes: 0
Reputation: 434
As /etc/stunnel/README
file says,
"Files found under the /etc/stunnel directory that end with .conf are used by stunnel4 service as configuration files, and each will be used to start a daemon process setting up a tunnel with the given configuration..."
I assume you can keep 2 separate config files there: one for server and another one for client. Than you'll have 2 daemons started.
You can find config file examples in a file /usr/share/doc/stunnel4/examples/stunnel.conf-sample
Upvotes: 0
Reputation: 51
It is much easier you can simply You just have to set client=no under the [] (service) where stunnel works as a server and client=yes otherwise. You should also put service specific parameters like certificates where they belong.
Something like:
[server1]
..
client=no
[client1]
..
client=yes
Upvotes: 5
Reputation: 84189
You can specify the configuration file path on the command line, see stunnel(8)
.
Upvotes: 1