HE.net IPv6 tunnel trouble
I've set the IPv4 endpoint to my Linode's IP, tried the suggested configuration options (from tunnelbroker.net).
From browsing through the linode forums I found the following script:
#!/bin/sh
#
# Tunnel from HE - www.tunnelbroker.net
#
export IPV4="65.19.178.122"
export IPV6="2001:470:1F00:FFFF::E77"
#
ip tunnel add sixbone mode sit remote 64.71.128.82 local $IPV4 ttl 255
ip link set sixbone up
ip addr add $IPV6 dev sixbone
ip route add ::/0 dev sixbone
The linode is a clean install of Ubuntu 6.06. After running the script, I can't ping6 any ipv6 host. Can't even ping6 the server endpoint of the tunnel 2001:470:1F00:FFFF::E76.
Traceroutes to the linode's ipv6 get as far as tserv1.fmt.ipv6.he.net (2001:470:1fff:0:2e0:feef:fe07:c000).
I can ping the IPv4 address of the tunnel broker server (64.71.128.82) with no problem.
I had my linode working fine before with the Sixxs AICCU client connected to the atlanta tunnel, but have sense migrated to the west coast for the improved latency to asia-pacific.
I'll post some other network info at the end of this post.
Can anybody shed some light on what I'm doing wrong?
Many thanks!
root@none:~ # ifconfig
eth0 Link encap:Ethernet HWaddr FE:FD:41:13:B2:7A
inet addr:65.19.178.122 Bcast:65.19.178.255 Mask:255.255.255.0
inet6 addr: fe80::fcfd:41ff:fe13:b27a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2331 errors:0 dropped:0 overruns:0 frame:0
TX packets:1607 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:216297 (211.2 KiB) TX bytes:271590 (265.2 KiB)
Interrupt:5
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:832 (832.0 b) TX bytes:832 (832.0 b)
sit0 Link encap:IPv6-in-IPv4
inet6 addr: ::65.19.178.122/96 Scope:Compat
inet6 addr: ::127.0.0.1/96 Scope:Unknown
UP RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
sit1 Link encap:IPv6-in-IPv4
inet6 addr: fe80::4113:b27a/64 Scope:Link
inet6 addr: 2001:470:1f00:ffff::e77/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:64 (64.0 b) TX bytes:5084 (4.9 KiB)
sixbone Link encap:IPv6-in-IPv4
inet6 addr: fe80::4113:b27a/128 Scope:Link
inet6 addr: 2001:470:1f00:ffff::e77/128 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
2 Replies
You can also check the Ipv6 page on the wiki:
I tried following the FAQ instructions with no luck. Here's what I added to the interfaces file (I'm using ubuntu dapper). Numbers are different from before because I signed up for a new tunnel.
auto hetunnel
iface hetunnel inet6 v4tunnel
address 2001:470:1F03:ED8::2
netmask 64
endpoint 64.71.128.83
up ip route add ::/0 dev hetunnel
up ip tunnel change hetunnel ttl 64
The result after boot is:
root@panda:~ # ifconfig
eth0 Link encap:Ethernet HWaddr FE:FD:40:3E:E7:9D
inet addr:65.19.178.122 Bcast:65.19.178.255 Mask:255.255.255.0
inet6 addr: fe80::fcfd:40ff:fe3e:e79d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4685 errors:0 dropped:0 overruns:0 frame:0
TX packets:4310 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:963162 (940.5 KiB) TX bytes:302161 (295.0 KiB)
Interrupt:5
eth0:1 Link encap:Ethernet HWaddr FE:FD:40:3E:E7:9D
inet addr:64.62.231.157 Bcast:64.62.231.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:5
hetunnel Link encap:IPv6-in-IPv4
inet6 addr: 2001:470:1f03:ed8::2/64 Scope:Global
inet6 addr: fe80::4113:b27a/64 Scope:Link
inet6 addr: fe80::403e:e79d/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:448 (448.0 b) TX bytes:448 (448.0 b)
No firewall (shorewall turned off):
root@panda:~ # iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Tunnel endpoint is set properly at tunnelbroker.net (triple checked this….and have tried with both ipv4 addresses on the linode).
Am I doing something wrong?
Can someone else that uses HE tunnel with a linode verify that HE tunnel system is actually up and working?