Configure IPv6 Tunnel in Ubuntu Linux
Posted on July 30th, 2008 in Linux |
Configuring the IPv6 tunnel can be easily done in Derbian and Ubuntu Linux using Tunnel Setup Protocol Client (tspc). TSPC is a signalling protocol used to negotiate tunnel setup parameters between two tunnel end-points. Tunnel Setup Protocol Client allows you to connect and browse IPv6 network using IPv4. But before installing TSPC, you need to get IPv6 access through Freenet6. Just register at Freenet6 to obtain a username and password.
Now install tunnel setup prtocol client (tspc) with the following command.
sudo aptitude install tspc
or
sudo apt-get install tspc
This will install tspc.
Now its time to configure tspc. Open the default configuration file located at /etc/tsp/tspc.conf. Open this file in a text editor using a following command :
sudo gedit /etc/tsp/tspc.conf
Now you should give the username, password and hostname registered at Freenet6.
userid : itech
password : 12345678
server ; broker.freenet6.net
Search, userid, server, and passwd variable in file and set them as follows:
userid=your-name
server=broker.freenet6.net
passwd=your-password
Now save and close the file and restart tspc by using the following command :
sudo /etc/init.d/tspc restart
Now you can test the IPv6 connection. First check the IPv6 tunnel address with the help of the following command :
ifconfig tun
Test IPv6 connectivity using the following command
ping6 ipv6.google.com
ping6 www.kame.net
You can use the following commands to start and stop tunnel
sudo /etc/init.d/tspc stop
sudo /etc/init.d/tspc start

One Response
The IPv6 configuration in Ubuntu is brilliantly simple and Just Works™ the way you described it, but in the last line I see you start tspc manually, and so do I have to do in order to get IPv6 connectivity working.
But since the tspc package installed its own init-script, isn’t it supposed to start at boot time? As far as I can see, both tspc and radvd seem to get started *before* the IPv4 network is ready, and so their execution is aborted immediately.
Have you managed to get things right? Changing the sequence number didn’t work for me, and having the two scripts start in a runlevel looks plain wrong to me, as by that time networking should be up and running for the services to bind to.