Technical data

4. Packages
IPV6_TUNNEL_x_TYPE This variable determines the type of the tunnel. Currently, the
values “raw”, “static”, “sixxs” for dynamic heartbeat-tunnels by the provider SixXS and
“he” for tunnels of provider Hurricane Electric are supported. More about heartbeat-
tunnels in the next paragraph.
Example: IPV6_TUNNEL_1_TYPE='sixxs'
IPV6_TUNNEL_x_DEFAULT This variable determines whether IPv6 packets which are not
addressed to local networks are allowed to be routed through this tunnel. Only one
tunnel can do this (because there is only one default route). Possible values are “yes”
and “no”.
Important: Exactly one tunnel should be a default gateway for outbound IPv6 otherwise
no communication with IPv6 hosts on the Internet is possible! The use of only non-
default tunnels is only useful if outgoing IPv6 traffic is sent on a separately configured
default route, which is not related to a tunnel. See the introduction to the subsection
“Route Configuration” and the description of the variable IPV6_ROUTE_x below.
Default setting: IPV6_TUNNEL_1_DEFAULT='no'
IPV6_TUNNEL_x_PREFIX This variable contains the IPv6-subnet-prefix of the tunnel in
CIDR-Notation which means an IPv6-address is provided as well as the length of the
prefix. This settings are usually given to you by the tunnel provider. This setting is
not necessary for tunnel providers giving a new prefix each time a tunnel is established.
(Such providers are not supported at the moment.) This variable has to be empty with
“raw” tunnels as well.
Important: This variable may be empty if the tunnel has no subnet-prefix assigned.
But in turn the tunnel can not be assigned to a IPv6-subnet (IPV6_NET_x) because IPv6-
addresses in the subnet ca not be computed. Such a configuration makes only sense on
an interim basis if the tunnel has to be active for some time before the tunnel provider
assigns a subnet-prefix (this is the usual procedure for the tunnel provider SixXS).
Examples:
IPV6_TUNNEL_1_PREFIX='2001:db8:1743::/48' # /48-subnet
IPV6_TUNNEL_2_PREFIX='2001:db8:1743:5e00::/56' # /56-subnet
IPV6_TUNNEL_x_LOCALV4 This variable contains the local IPv4-address of the tunnel
or the value ‘dynamic’ if the dynamic IPv4-address of the active WAN-Circuits should
be used. The latter makes only sense for a heartbeat-tunnel (see IPV6_TUNNEL_x_TYPE
below).
Examples:
IPV6_TUNNEL_1_LOCALV4='172.16.0.2'
IPV6_TUNNEL_2_LOCALV4='dynamic'
137