I have been using the IPv6 tunnel service from Hurricane Electric and tonight I decided to switch to native Linode IPv6. The HE tunnel has worked beautifully, but I cannot get the Linode configuration to come up.
I am running Centos 5.8.
According to the Linode site, my IP's are:
74.207.230.94/255.255.255.0 ( atlanta.wx4akq.org )
2600:3c02::f03c:91ff:fe96:a6f7/64
Default gateways:
74.207.230.1
fe80::1
I have-- as best I can tell-- removed all traces of the HE.net tunnel from the system. Part of this was changing /etc/sysconfig/network to reflect "IPV6_DEFAULTDEV=eth0" instead of "=sit0" as configured during the HE.net tunnel setup.
When my Linode boots, eth0 finds the link address, but is not populating with the IPv6 address:
Code:
eth0 Link encap:Ethernet HWaddr F2:3C:91:96:A6:F7
inet addr:74.207.230.94 Bcast:74.207.230.255 Mask:255.255.255.0
inet6 addr: fe80::f03c:91ff:fe96:a6f7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5612 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:714964 (698.2 KiB) TX bytes:696392 (680.0 KiB)
Interrupt:48
I can manually add the address using the "ip" command:
Code:
ip -6 addr add 2600:3c02::f03c:91ff:fe96:a6f7/64 dev eth0
...and then "ifconfig eth0" shows the address, as expected:
Code:
eth0 Link encap:Ethernet HWaddr F2:3C:91:96:A6:F7
inet addr:74.207.230.94 Bcast:74.207.230.255 Mask:255.255.255.0
inet6 addr: 2600:3c02::f03c:91ff:fe96:a6f7/64 Scope:Global
inet6 addr: fe80::f03c:91ff:fe96:a6f7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5765 errors:0 dropped:0 overruns:0 frame:0
TX packets:4462 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:733888 (716.6 KiB) TX bytes:722654 (705.7 KiB)
Interrupt:48
...however, I still cannot pass any traffic out to the Internet over IPv6:
Code:
ping6 ipv6.google.com
connect: Network is unreachable
At various points in playing with the system, bringing interfaces up and back down and tinkering with configuration files and routing I have gotten it working *briefly* but upon cycling the interface down and back up, or rebooting the Linode, it stops working again, and even repeating the steps which previously worked do not appear to fix it, so I think it's more of a fluke that it ever worked at all.
I'm sure there's something still lurking in the system relating to the HE.net tunnels that needs to be removed, but I have no idea where to begin looking. Any suggestions?