Technical data

4. Packages
Hint: Despite to earlier versions of the documentation the rules were restricted
to the nets really needed. If IPTV does not work as exepected feel free to provide
additional information concerning the nets used.
Important! By the end of May 2013 the Telekom introduced new classless
routes for Entertain (http://www.onlinekosten.de/forum/showthread.php?t=116415&page=
38). This seems to be caused by the use of more than 256 stations resp. addresses.
The DHCP server now transfers routes not contained in the subnet used before.
As long as the Telekom does not change its iptv-server-subnet (193.158.34.0/23)
a static route may be defined for the vlan8 interface to adapt these changes, oth-
erwise Multicast would not work anymore.
Solution: specify an additional route in base.txt.
IP_ROUTE_N='1'
IP_ROUTE_1='193.158.34.0/23 eth1.8'
4.17.7. OPT_STUNNEL - Tunneling Connections Over SSL/TLS
The program “stunnel” allows to encapsulate connections otherwise unencrypted in an en-
crypted SSL/TLS tunnel. This allows safe data exchange over otherwise insecure cleartext
protocols. Due to the possibilities of the SSL/TLS protocol, various forms of Client/server
validation are possible.
Configuration
OPT_STUNNEL This variable activates support for SSL/TLS tunnels.
Default setting: OPT_STUNNEL='no'
Example: OPT_STUNNEL='yes'
STUNNEL_DEBUG This variable can be set to configure the logging settings for “stunnel”.
Available settings are “yes” (everything is logged), “no” (warnings and errors are logged)
or a value between zero and seven indicating the severity of messages whith zero for
highest and seven for lowest severity. The setting “yes” corresponds to severity seven,
while “no” corresponds to severity four.
Default setting: STUNNEL_DEBUG='no'
Example 1: STUNNEL_DEBUG='yes'
Example 2: STUNNEL_DEBUG='5'
STUNNEL_N This variable configures the number of tunnel instances. Each tunnel instance
“listens” on a network port “A” and connects to another network port “B” when a
connection is established (may as well be on a different machine), then forwards all
traffic from “A” to “B”. Whether the data, that arrives at “A” encrypted via SSL/TLS
will be decrypted by “stunnel” before forwarding unencrypted to “B” or vice versa is
decided by the variable setting in STUNNEL_x_CLIENT (Page 200).
Default setting: STUNNEL_N='0'
Example: STUNNEL_N='2'
199