1 Reply Latest reply on Dec 7, 2008 6:27 PM by Andy McBride

    IPV6 Tools

      I do miss IPV6 tools.


      Like a netwok browser and traceroute for IPv6 would be fine.


       Here is a tracert and ping from command line to ipv6.goolge.com


       


      C:\Users\admin>tracert ipv6.google.com


      Tracing route to ipv6.l.google.com [2001:4860:0:1001::68]
      over a maximum of 30 hops:


        1     2 ms    <1 ms    <1 ms  2002:3e10:a1d7:1::1
        2   161 ms    80 ms    84 ms  2002:82f4:1f::1
        3   424 ms    27 ms     *     2a00:800:0:1::89:1
        4   185 ms   204 ms   204 ms  2a00:800:0:1::78:2
        5   225 ms   204 ms   204 ms  2a00:800:0:1::e:2
        6   224 ms   204 ms   204 ms  2a00:800:0:1::4:1
        7   225 ms    51 ms   152 ms  pr61.ams04.net.google.com [2001:7f8:1::a501:5169:1]
        8     *        *        *     Request timed out.
        9    94 ms   116 ms   291 ms  2001:4860:0:1001::68


      Trace complete.


      C:\Users\admin>ping ipv6.google.com


      Pinging ipv6.l.google.com [2001:4860:0:1001::68] from 2002:3e10:a1d7:1:989b:2e75:4796:758f with 32 bytes of data:
      Reply from 2001:4860:0:1001::68: time=200ms
      Reply from 2001:4860:0:1001::68: time=222ms
      Reply from 2001:4860:0:1001::68: time=244ms
      Reply from 2001:4860:0:1001::68: time=267ms


      Ping statistics for 2001:4860:0:1001::68:
          Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
      Approximate round trip times in milli-seconds:
          Minimum = 200ms, Maximum = 267ms, Average = 233ms