Hi there,
I set up my tunnel on Fedora 16 using the linux-route2 instructions, and I can now ping the remote server but not anything else, e.g., google.
# ifconfig he-ipv6
he-ipv6 Link encap:IPv6-in-IPv4
inet6 addr: fe80::1831:ae7f/128 Scope:Link
inet6 addr: 2001:470:c:871::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:1499 (1.4 KiB)
#ip -6 route show
unreachable ::/96 dev lo metric 1024 error -101
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101
2001:470:c:871::/64 via :: dev he-ipv6 proto kernel metric 256
unreachable 2002:a00::/24 dev lo metric 1024 error -101
unreachable 2002:7f00::/24 dev lo metric 1024 error -101
unreachable 2002:a9fe::/32 dev lo metric 1024 error -101
unreachable 2002:ac10::/28 dev lo metric 1024 error -101
unreachable 2002:c0a8::/32 dev lo metric 1024 error -101
unreachable 2002:e000::/19 dev lo metric 1024 error -101
unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 via :: dev he-ipv6 proto kernel metric 256
default dev he-ipv6 metric 1024
I can now ping the remote router:
#ping6 -c3 2001:470:c:871::1
PING 2001:470:c:871::1(2001:470:c:871::1) 56 data bytes
64 bytes from 2001:470:c:871::1: icmp_seq=1 ttl=64 time=23.7 ms
64 bytes from 2001:470:c:871::1: icmp_seq=2 ttl=64 time=17.3 ms
64 bytes from 2001:470:c:871::1: icmp_seq=3 ttl=64 time=16.4 ms
--- 2001:470:c:871::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 16.459/19.197/23.797/3.275 ms
But I can't ping or connect to anything else, e.g. google:
#ping6 -c3 www.google.com
PING www.google.com(lax02s02-in-x11.1e100.net) 56 data bytes
--- www.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
Any ideas?
-Bob
2001:470:c:871::2 doesn't respond to pings. Try specifying 2000::/3 as default route and not ::/0. That bug shouldn't exist anymore in Fedora/CentOS/RHEL kernels since 2.6.18, but since you cannot get beyond the tserv, and I cannot reach you beyond it either, either the default route is incorrect, or the tunnel should get rebuilt on HE's side to verify it is correct and there are no dupe tunnels or something.
Also if that machine is behind NAT, make certain you used the RFC1918 IP as local when running the iproute2 commands. Although since you can ping upstream, I don't think that is the issue.
no joy adding 2000::/3 as a gateway route.
I'm running a relatively recent kernel:
# uname -r
3.4.11-1.fc16.i686.PAE
The machine is connected directly to the internet.
Route to IPV6 router:
#ip -6 route get to 2001:470:c:871::1
2001:470:c:871::1 from :: via :: dev he-ipv6 src 2001:470:c:871::2 metric 0
Route to www.google.com:
# ip -6 route get to 2001:4860:4007:801::1012
2001:4860:4007:801::1012 from :: via 2001:4860:4007:801::1012 dev he-ipv6 src 2001:470:c:871::2 metric 0
-Bob
You're not running from your /48 are you?
email ipv6@he.net, ask them to verify your tunnel is built correctly, and no other dupe configs, etc.
I contacted support and they fixed it. Thanks for your help.
-Bob