Google and IPv6 inverse?

Bjørn Mork bjorn at mork.no
Mon Jun 6 09:38:26 CDT 2011


Leo Bicknell <bicknell at ufp.org> writes:

> Quick question, which network providers were involved in that trace?
> Have fun hitting up whois to find out!

You can convince your traceroute to do that for you:

  -A  --as-path-lookups       Perform AS path lookups in routing registries and
                              print results directly after the corresponding
                              addresses



traceroute to ipv6.google.com (2a00:1450:4008:c00::93), 30 hops max, 80 byte packets
 1  canardo-br0-7.ipv6.mork.no (2001:4620:9:2::1) [AS2119]  1.174 ms  1.349 ms  1.373 ms
 2  2001:4600:10:101::1 (2001:4600:10:101::1) [AS2119]  14.623 ms  14.800 ms  14.956 ms
 3  * * *
 4  * * *
 5  * * *
 6  2001:4860::1:0:60d (2001:4860::1:0:60d) [AS15169]  60.938 ms  42.619 ms  42.614 ms
 7  2001:4860:1:1:0:847:: (2001:4860:1:1:0:847::) [AS15169]  27.633 ms  27.732 ms  27.886 ms
 8  2001:4860::1:0:26ec (2001:4860::1:0:26ec) [AS15169]  30.820 ms  30.873 ms  34.980 ms
 9  2001:4860::1:0:60d (2001:4860::1:0:60d) [AS15169]  54.459 ms  39.116 ms  43.212 ms
10  2001:4860:0:1::217 (2001:4860:0:1::217) [AS15169]  47.002 ms  44.100 ms  44.174 ms
11  2a00:1450:4008:c00::93 (2a00:1450:4008:c00::93) [AS15169]  43.446 ms  43.726 ms  40.642 ms

Now Juniper, it would be really nice if we also could see those
intermediate MPLS nodes at hop 3, 4 and 5, but I know those are AS2119
anyway :-)



Bjørn






More information about the NANOG mailing list