Stage 3: 6Bone-connected PC
Create a Tunnel:
NOTE: This document assumes you have completed the configuration steps
from Stage 2 and that you have not rebooted or made any other networking
changes since it.
NOTE: All steps will be performed on PC 2 only
Disconnect the crossover cable
Connect Adaptor 1 (eth0) to your network jack (DSL modem, in my case)
Log in as root
Modify the IPv4 configuration using linuxconf. Enter your own
addresses and hostnames where appropriate:
Config->Networking->Client tasks->Basic Host Information:
Host name: hal9001.dyndns.org
Config->Networking->Client tasks->Name server specification:
DNS Usage: on
Config->Networking->Client tasks->Routing and gateways->Set Defaults:
Default domain: dyndns.org
IP of name server 1: 184.108.40.206
(All other fields): blank
Default gateway: 220.127.116.11
NOTE: The rest of the settings must be as they were in Stage 2
Enable routing: off
Activate the changes and quit linuxconf
You must now undo the damage linuxconf has done to /etc/hosts.
Add the lines you added to it in stage 2 again.
Linuxconf does not restart the network interfaces with the new parameters
unfortunately. You will have to do this yourself by restarting the network
# /etc/rc.d/init.d/network restart
Try pinging an outside address. If this fails, you might have to set the
default IPv4 route manually:
# route add default gw 18.104.22.168 dev eth0
Browse to the following page: http://www.freenet6.net
From here, you can set up a tunnel to the 6Bone. Choose the links "Get
your own IPv6 tunnel" and "Linux Debian GNU". Click the "Registration Form"
button and fill in your IPv4 address (22.214.171.124 in this case), an arbitrary
name that will be used in their DNS for your computer, and your country.
When you click "Submit", a perl script will be downloaded to your computer.
Save it anywhere; you won't need it later.
The page you will see now has your IPv6 tunnel configuration. Take note
of the following addresses:
||What it is:
|"Your IPv6 address"
||The address of your side of the tunnel
|"Freenet6 IPv6 address"
||The address of their side of the tunnel
|"Freenet6 IPv4 address"
||The IPv4 address of their tunnel server
Configure Tunnel Connection:
For the purposes of this section, the addresses will be referred to by
the following "variables":
||How to determine it:
||Example using addresses from above:
||First four numbers of your IPv6 address
||Last number of your IPv6 address
||Last number of the Freenet6 IPv6 address
||"Freenet6 IPv4 address"
You are now ready to enable the tunnel. Enter the following commands as
# ifconfig sit0 up
# ifconfig eth0 add PREFIX::SUFFIX/64
# ifconfig sit0 tunnel ::TUNNEL
# ifconfig sit1 up
# route -A inet6 add 3ffe::0/15 gw ::TUNNEL dev sit0
Now test the tunnel. First, ping the IPv6 address of your side of the tunnel:
Now try to ping the remote side of the tunnel:
It can take a minute or two of pinging the remote side of the tunnel to
start working. Be patient.
If you still cannot ping the remote side of the tunnel, bring the sit0
and sit1 interfaces down, restart the network service, create a new tunnel,
and configure it.
To make sure that the 6Bone and name resolution are working, we will ping
a few hosts. Don't be alarmed if they don't all work; about half of the
well-known 6Bone sites are down on the average!
# ping6 www.6bone.net
# ping6 www.normos.org
# ping6 www.ipv6.uni-muenster.de
Many of these sites are both IPv4 and IPv6 accessible and ping6
supports both protocols (but it will try IPv6 first). If you are only seeing
pings coming back from IPv4 addresses, double-check your configuration
with ifconfig and route.
Now use Chimera to browse to the sites you just pinged. If you like, you
can use tcpdump to watch the traffic on the eth0, sit0, and sit1
interface to see what is going on.