IPv6 Routing Issues

[cmeerw]

Is anyone else seeing issues with IDNet's IPv6 connectivity - for about a week now I am unable to reach most of the IPv6 Internet via IDNet. Unfotunately, support hasn't been that helpful so far... :-(

BTW, I think SixXS's Distributed Looking Glass shows quite clearly that there are major routing issues with IDNet's IPv6 address space.

[dujas]

Are idnet officially supporting IPv6 now?

[Simon]

I wasn't aware that they'd implemented support for it yet, but I know it caused problems when they tried before.

[Rik]

It hasn't been implemented.

[Dangerjunkie]

Is there an approximate time frame for official IPv6 support please?

I don't need it yet but I can see it's going to be of relevance to my business. I'd like to get to play with it before I need to use it in anger (There's nothing quite like looking an idiot because you're trying to work something out for the first time when the customer is looking over your shoulder )

I saw a posting from someone in another forum that said he'd got 1024 of his own personal IPv6 addresses. When IPv6 comes do we get addresses from IDNet or can we get portable ones that are our own to keep for life?

Thanks,
Paul.

[Rik]

You'd need to ask IDNet, Paul, we haven't heard much on the subject. It was, briefly, implemented, but it caused problems with the name servers so, afaik, the network is IPv6 ready, but it won't be implemented in the immediate future. I've heard nothing on policy regarding IP addresses.

[cmeerw]

It hasn't been implemented.

Now I am confused - is it just an illusion?

Code Select Expand


traceroute to he.net (2001:470:0:76::2), 30 hops max, 16 byte packets
1  2a02:390:ffff:ffff:ffff:ffff:ffff:fffe (2a02:390:ffff:ffff:ffff:ffff:ffff:fffe)  46.605 ms  26.631 ms  21.841 ms
2  2a02:390:0:ff00:204:4eff:feb3:741b (2a02:390:0:ff00:204:4eff:feb3:741b)  22.881 ms  22.778 ms  25.013 ms
3  2001:7f8:17::1b1b:1 (2001:7f8:17::1b1b:1)  21.908 ms  24.791 ms  22.852 ms
4  10gigabitethernet2-3.core1.nyc4.he.net (2001:470:0:3e::1)  94.016 ms  93.901 ms  100.888 ms
5  10gigabitethernet5-3.core1.lax1.he.net (2001:470:0:10e::1)  153.875 ms  154.124 ms  153.652 ms
6  10gigabitethernet1-3.core1.pao1.he.net (2001:470:0:34::1)  160.826 ms  160.984 ms  162.819 ms
7  10gigabitethernet1-2.core1.fmt1.he.net (2001:470:0:2e::1)  161.906 ms  172 ms  176.865 ms
8  he.net (2001:470:0:76::2)  161.859 ms  163.011 ms  161.852 ms


The problem is just that about half of the IPv6 Internet is currently not reachable, e.g.

Code Select Expand


traceroute to ipv6.l.google.com (2001:4860:a005::68), 30 hops max, 16 byte packets
1  2a02:390:ffff:ffff:ffff:ffff:ffff:fffe (2a02:390:ffff:ffff:ffff:ffff:ffff:fffe)  24.143 ms  53.289 ms  23.883 ms
2  2a02:390:0:ff00:204:4eff:feb3:741b (2a02:390:0:ff00:204:4eff:feb3:741b)  22.869 ms !N  22.664 ms !N  27.174 ms !N


[Rik]

I can only tell you what I've been told. It's implemented across the internal network, but not externally, so officially it's not yet available.