Sunday, February 20, 2005

Arrg!!

Setting an IPv6-over-IPv4 tunnel up and running via OpenWRT on a WRT54G
can be a frustrating experience. I know I have the tunnel part up and
running as I can "ping6 www.kame.net" from the 54G. Tcpdump shows the
packets going out and coming back. The ping6 output looks okay.

The
problem is when I "ping6 www.kame.net" from the computer. Tcpdump shows
the packets going out but not coming back. I suspect the problem is in
the radvd configuration (i.e., the wrong prefix is being
assigned??).

Maybe someone can reading this can tell me what I'm doing
wrong, so I'll post the data here. I use Hurricane Electric's tunnel
broker (http://www.tunnelbroker.net).

Tunnel Information:

Server IPv4
address:
64.71.128.82
Server IPv6
address:
2001:470:1F00:FFFF::656/127
Client
IPv4 address:
My IP Address
Client
IPv6
address:
2001:470:1F00:FFFF::657/127
Assigned /64:none
ASN:none
Last Ping6:Sun, Feb 20 3:07 pm PST
Last Inbound Packet:none
Registration Date:Sun, Feb 20, 2005

Update: You have to click on the "Submit" button on the "/64 Allocation" page, whether or not you fill in the DNS entries. Otherwise, you don't get the /64 allocation. So, "Assigned /64:" in the table above should read: 2001:470:1F00:911::/64

From /etc/init.d/S99done:

insmod ipv6
insmod ip6_tables
insmod ip6table_filter
echo 1 > /proc/sys/net/ipv6/conf/all/forwarding

From /etc/init.d/rcS:

# set up the IPv6 tunnel
ip tunnel add he.net mode sit remote 64.71.128.82 local MYIPADDRESS ttl 255
ip link set he.net up
ip addr add 2001:470:1F00:FFFF::657/127 dev he.net
ip route add ::/0 dev he.net
ip -f inet6 addr
ip -6 addr add 2001:470:1F00:CAFE::1/64 dev eth1
radvd

Am I missing something?