Technical data

B. Appendixes to optional packages

B.11.2. Tunnel Conﬁguration

Preparation

At ﬁrst you have to apply for the tunnel. This happens after registration via the menu item

“request tunnel”. It is important to select “Dynamic IPv4 Endpoint using Heartbeat protocol”

as the type of the tunnel in the second entry because this conﬁguration is supported directly

by the ﬂi4l. The third variant “Static IPv4 Endpoint” is also possible if you own a dedicated

IPv4 address that never changes. The tunnel variant “Dynamic NAT traversing IPv4 endpoint

is using AYIYA” currently is not supported by the IPv6 package.

Once you’ve ﬁlled in the details for the location of the router into the other ﬁelds the next

step is going to the second page via “changed”. Here one or multiple PoPs (Points of Presence)

have to be chosen. They are important for the tunnel construction later. You should take the

one which is closest to you in order to make tunneling of IPv6 packets as eﬃciently as possible.

If all details are ﬁlled in and sent via “Place request for new tunnel” you will receive an

e-mail with the necessary tunnel data. This includes:

1. Identiﬁcation number of the tunnel (T...)

2. Name of the associated PoP

3. IPv4-address of the associated PoP (“SixXS IPv4”)

4. Local IPv6-address and subnet mask of the tunnel (typically /64 for SixXS) - this rep-

resents the address of your router (“Your IPv6”)

5. Remote IPv6 address of the tunnel including subnet mask (identical with the subnet

mask of the local IPv6 address), ie the address of the (PoPs SixXS “ IPv6”)

Conﬁguration

Now the tunnel can be conﬁgured! First, the variable IPV6_TUNNEL_N has to be set to “1”

because exactly one tunnel should be built:

IPV6_TUNNEL_N='1'

The details SixXS provided have to be ﬁlled in the IPv6 conﬁguration as follows:

1. The identiﬁcation number of the tunnel is put in

IPV6_TUNNEL_1_TUNNELID.

2. The name of the associated PoP is not needed

3. The IPv4-address of the associated PoP has to be speciﬁed in

IPV6_TUNNEL_1_REMOTEV4.

4. The local IPv6-address and subnet mask of the tunnel is ﬁlled in the variable

IPV6_TUNNEL_1_LOCALV6.

5. The remote IPv6 address of the tunnel without subnet mask goes to variable

IPV6_TUNNEL_1_REMOTEV6.

361