OK, let's go through this and correct as needed:
>echo 1 > /proc/sys/net/ipv6/conf/all/accept_redirects
Do you really want redirects?
>$route -A inet6 add $PREFIX::0/48 dev eth0
Why 48 bits?
>$ifconfig sit1 inet6 add $PREFIX::$ADDRESS1
Remove the above line
Eliminate mrtd and radvd from the config until you get the basic tunnel
working... process of elimination, simplify
I _think_ everything else looks ok and I hope I have not missed anything.
The important thing now is to test connectivity. First, try your basic
ping6 ::1, then move to a ping6 ::ipv4addr where the addr is the other side
of the tunnel. Do any of those fail? If not, where do you see connectivity
fail? When attempting to ping6 other devices on the 6bone?
You can, if you'd like, reference the scripts I have placed online for use.
http://succubus.dhis.org/~coronach/ipv6 will have two scripts and a config
file. The first script is real rough and the second is an improvement but
hopefully it will help. These scripts are being used right now to connect
several machines to the 6bone here at Purdue. If you have suggestions about
the script, problems, etc, please e-mail the address in the header.
--Mike
-----Original Message-----
From: sarikaya@xxxxxxxxxxxxxxxxxxxxx
[mailto:sarikaya@xxxxxxxxxxxxxxxxxxxxx]
Sent: Saturday, February 12, 2000 3:38 AM
To: coronach@xxxxxxxxxxxxxxxxx; netdev@xxxxxxxxxxx;
sarikaya@xxxxxxxxxxxxxxxxxxxxx
Subject: sit configuration
Hello Michael,
I did like you said but it did not work!
Firstly, 1280 is required for tunnels to 6bone-jp, so I kept it at 1280.
I am attaching the v6 startup shell on tunnel endpoint machine
(163.143.180.107) which has two interfaces, so I create two prefixes
3ffe:501:427:1002 and 3ffe:501:427:1102 and I run mrtd, I am attaching
mrtd.conf as well.
On the tunnel provider host, I ran a script to create sit2 and I
include this script (ipv6.sh.tun2).
On this host too I ahve two interface and I am running mrtd with a
similar conf file (with network sit2 added on ripng).
Thanks in advance,
--
Behcet Sarikaya
Computer Communications Lab.
|