Changes IPv6

IPv6 Changes

We have begin the process of migrating our legacy IPv6 network into our /32 allocation, 2607:fe70::/32. Once this is complete, we will further enable other services with IPv6, such as incoming mail.

If you’d like to test it, you can use 2607:fe70::1 as a ping or traceroute destination.

5 replies on “IPv6 Changes”

Some day I’ll have a native v6 connection… someday…

Looking good from Chicago:

$ traceroute6 -n 2607:fe70::1
traceroute6 to 2607:fe70::1 (2607:fe70::1) from 2001:470::, 64 hops max, 12 byte packets
1 2001:470:: 103.045 ms 0.891 ms 1.533 ms
2 2001:470:: 43.303 ms 42.866 ms 43.540 ms
3 2001:470:0:6e::1 41.510 ms 42.700 ms 43.321 ms
4 2001:470:0:3c::1 100.525 ms 101.439 ms 103.131 ms
5 2001:470:0:2f::1 105.371 ms 99.803 ms 101.129 ms
6 2001:470:0:44::2 104.259 ms 103.597 ms 100.558 ms
7 2001:470:1f03:5a1::2 111.956 ms 112.298 ms 112.189 ms

I wonder why the latency is ten (10) times higher when I ping -6 vs. ping -4 The high latency really kicks in at the point where Sprint starts handling things. Ah yes, I recall how bad Sprint was from years (it seems like a lifetime) ago. They’re still bad I guess. Na, I’m sure there’s another explanation…

The Sprint connection is still a tunnel. They are expecting to convert us to dual stack in July or August, barring any unforeseen bugs on the GSR platform. Native service on AS1239 is currently available where they can deliver Ethernet or 10GE, which is unfortunately not in Nevada.

Comments are closed.