Technical data

4. Packages
STUNNEL_1_CERT_VERIFY='both'
STUNNEL_2_NAME='remote-imond2'
STUNNEL_2_CLIENT='yes'
STUNNEL_2_ACCEPT='any:50001'
STUNNEL_2_ACCEPT_IPV4='yes'
STUNNEL_2_ACCEPT_IPV6='yes'
STUNNEL_2_CONNECT='@remote2:50000'
STUNNEL_2_CERT_FILE='client.pem'
STUNNEL_2_CERT_CA_FILE='ca+server2.pem'
STUNNEL_2_CERT_VERIFY='both'
Configuration of the first remote fli4l (server tunnel):
OPT_STUNNEL='yes'
STUNNEL_N='1'
STUNNEL_1_NAME='remote-imond'
STUNNEL_1_CLIENT='no'
STUNNEL_1_ACCEPT='any:50000'
STUNNEL_1_ACCEPT_IPV4='yes'
STUNNEL_1_ACCEPT_IPV6='yes'
STUNNEL_1_CONNECT='127.0.0.1:5000'
STUNNEL_1_CERT_FILE='server1.pem'
STUNNEL_1_CERT_CA_FILE='ca+client.pem'
STUNNEL_1_CERT_VERIFY='both'
Configuration of the second remote fli4l (server tunnel):
OPT_STUNNEL='yes'
STUNNEL_N='1'
STUNNEL_1_NAME='remote-imond'
STUNNEL_1_CLIENT='no'
STUNNEL_1_ACCEPT='any:50000'
STUNNEL_1_ACCEPT_IPV4='yes'
STUNNEL_1_ACCEPT_IPV6='yes'
STUNNEL_1_CONNECT='127.0.0.1:5000'
STUNNEL_1_CERT_FILE='server2.pem'
STUNNEL_1_CERT_CA_FILE='ca+client.pem'
STUNNEL_1_CERT_VERIFY='both'
A connection to the remote “imond” is established by initiating a connection to the local
fli4l on port 50000 (first remote fli4l) resp. 50001 (second remote fli4l). This fli4l then connects
via SSL/TLS-Tunnel to each of the remote fli4l’s which in turn forward their data over a third
(host internal) connection to the remote “imond” in the end. The settings of the validation
ensure that each fli4l only accepts the other fli4l as the connecting counterpart.
4.18. QoS - Quality of Service
By QoS the available bandwidth can be regulated and for example be distributed to several
ports, IP addresses and more.
204