Technical data
B. Appendixes to optional packages
In addition the username and password have to be specified in the tunnel configuration in
variables IPV6_TUNNEL_1_USERID and IPV6_TUNNEL_1_PASSWORD.
Finally set the variable IPV6_TUNNEL_1_TYPE to reflect that the configured tunnel is a SixXS
tunnel:
IPV6_TUNNEL_1_TYPE='sixxs'
Example: If you got the PoP “deham01” with the IPv4-address 212.224.0.188 and tunnel
end points 2001:db8:900:551::1/64 (remote) and 2001:db8:900:551::2/64 (local) from
SixXS, the tunnel-ID is “T1234”, the username “USER1-SIXXS” and the password “sixxs”
(do not use this password!) then the resulting configuration will look like this:
IPV6_TUNNEL_N='1'
IPV6_TUNNEL_1_LOCALV4='dynamic' # or fixed local IPv4-address
IPV6_TUNNEL_1_REMOTEV4='212.224.0.188'
IPV6_TUNNEL_1_LOCALV6='2001:db8:900:551::2/64'
IPV6_TUNNEL_1_REMOTEV6='2001:db8:900:551::1'
IPV6_TUNNEL_1_TYPE='sixxs'
IPV6_TUNNEL_1_USERID='USER1-SIXXS'
IPV6_TUNNEL_1_PASSWORD='sixxs'
IPV6_TUNNEL_1_TUNNELID='T1234'
Test
If you accomplished this then update and restart the fli4l. After logging in to the router
(directly or e.g. via SSH) you should already be able to ping the tunnel endpoint. With the
example data above this will look as follows:
garm 3.6.0-revXXXXX # ping -c 4 2001:db8:900:551:0:0:0:1
PING 2001:db8:900:551::1 (2001:db8:900:551::1): 56 data bytes
64 bytes from 2001:db8:900:551::1: seq=0 ttl=64 time=67.646 ms
64 bytes from 2001:db8:900:551::1: seq=1 ttl=64 time=72.001 ms
64 bytes from 2001:db8:900:551::1: seq=2 ttl=64 time=70.082 ms
64 bytes from 2001:db8:900:551::1: seq=3 ttl=64 time=67.996 ms
--- 2001:db8:900:551::1 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 67.646/69.431/72.001 ms
Important is the part with the “0 % packet loss”. This means that response packets have
been received for all PING packets. If you get no response from the other end of the tunnel,
the result is different:
garm 3.6.0-revXXXXX # ping -c 4 2001:db8:900:551:0:0:0:1
PING 2001:db8:900:551::1 (2001:db8:900:551::1): 56 data bytes
--- 2001:db8:900:551::1 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
You may notice that not for a single ping a response packet was received (“100% packet
loss”). This either means that the configuration is incorrect or that the tunnel has not been
362