Testing IPv6 - BSD

This is a discussion on Testing IPv6 - BSD ; I would like to test IPv6 through my ISP (comcast). Are there any websites that I can use ping6, traceroute6, etc with? Thanks. Dave Feustel...

+ Reply to Thread
Results 1 to 12 of 12

Thread: Testing IPv6

  1. Testing IPv6

    I would like to test IPv6 through my ISP (comcast). Are there any
    websites that I can use ping6, traceroute6, etc with?


    Thanks.
    Dave Feustel

  2. Re: Testing IPv6

    dave wrote:

    > I would like to test IPv6 through my ISP (comcast). Are there any
    > websites that I can use ping6, traceroute6, etc with?



    www.kame.net (the famous dancing turtle)
    www.sixxs.net/main (IP below)
    ftp.freebsd.org

    HTH, Helmut

  3. Re: Testing IPv6

    Helmut Schneider wrote:
    > dave wrote:
    >
    >> I would like to test IPv6 through my ISP (comcast). Are there any
    >> websites that I can use ping6, traceroute6, etc with?

    >
    >
    > www.kame.net (the famous dancing turtle)
    > www.sixxs.net/main (IP below)
    > ftp.freebsd.org
    >
    > (IP below) HTH, Helmut


    That definitely helps! :-)

    How do I switch to IPv6 http as suggested by kame?

  4. Re: Testing IPv6

    dave wrote:
    > I would like to test IPv6 through my ISP (comcast). Are there any
    > websites that I can use ping6, traceroute6, etc with?
    >
    >
    > Thanks.
    > Dave Feustel


    Many websites about IPv6 have little "you are connecting from ..."
    somewhere on their index page - http://www.go6.net/
    http://www.ipv6tf.org http://www.ipv6day.org/ http://ww.ipv6.org/

    My fave for checking is the venerable dancing kame at
    http://www.kame.net/ - if you get the animated turtle you've connected
    vi IPv6, if not then you've connected via IPv4.

    http://www.sixxs.net/tools/ipv6calc/ will try to do a reverse lookup to
    see if your nameserver is properly serving and reversing IPv6 addresses.

  5. Re: Testing IPv6

    dave writes:

    > I would like to test IPv6 through my ISP (comcast). Are there any
    > websites that I can use ping6, traceroute6, etc with?


    When I go to this web page: http://www.ipv6.org/
    It tells me:

    You are using IPv6 from 2001:5a8:4:910:2e0:81ff:fe28:989f

    Other examples using the same address:

    $ ping6 www.ipv6.org
    PING6(56=40+8+8 bytes) 2001:5a8:4:910:2e0:81ff:fe28:989f --> 2001:6b0:1:ea:202:a5ff:fecd:13a6
    16 bytes from 2001:6b0:1:ea:202:a5ff:fecd:13a6, icmp_seq=0 hlim=46 time=232.799 ms
    16 bytes from 2001:6b0:1:ea:202:a5ff:fecd:13a6, icmp_seq=1 hlim=46 time=221.813 ms
    ^C
    --- shake.stacken.kth.se ping6 statistics ---
    2 packets transmitted, 2 packets received, 0.0% packet loss
    round-trip min/avg/max/std-dev = 221.813/227.306/232.799/5.493 ms

    $ traceroute6 www.ipv6.org
    traceroute6 to shake.stacken.kth.se (2001:6b0:1:ea:202:a5ff:fecd:13a6) from 2001:5a8:0:1::123, 64 hops max, 12 byte packets
    1 tunnel-sonic-end 10.403 ms 9.59 ms 9.808 ms
    2 2001:5a8:0:2:: 10.975 ms 11.265 ms 11.272 ms
    3 2001:5a8:0:5::2 29.702 ms 27.767 ms 28.744 ms
    4 6.fe-0-3.cr1.mci1.us.occaid.net 63.461 ms 56.255 ms 58.307 ms
    5 57.ge0-0.cr1.ord1.us.occaid.net 73.837 ms 76.193 ms 73.618 ms
    6 67.ge0-0.cr1.ewr1.us.occaid.net 99.422 ms 104.589 ms 100.941 ms
    7 v3323-mpd.cr1.lhr1.uk.occaid.net 179.502 ms 180.222 ms 183.963 ms
    8 14.fe0-0.cr1.arn1.se.occaid.net 231.974 ms 221.093 ms 226.875 ms
    9 2001:16d8:2:80::8473:1 231.73 ms 221.749 ms 234.991 ms
    10 2001:7f8:21:9::219 239.583 ms 223.381 ms 225.121 ms
    11 * kthnoc6.sunet.se 233.513 ms 222.296 ms
    12 stockholm1-SRP4.sunet.se 228.096 ms 228.883 ms 225.402 ms
    13 * c1sth-ge5-0-9.sunet.se 253.215 ms 263.384 ms
    14 2001:6b0:dead:beef:2::2c2 322.409 ms 233.344 ms 251.188 ms
    15 2001:6b0:1:1d20::2 226.531 ms 256.238 ms 238.193 ms
    16 clubroom-gw.stacken.kth.se 228.067 ms 361.125 ms 293.346 ms
    17 igloo.stacken.kth.se 236.177 ms 236.188 ms 227.637 ms

    // marc

  6. Re: Testing IPv6

    Cory Albrecht wrote:
    > dave wrote:
    >> I would like to test IPv6 through my ISP (comcast). Are there any
    >> websites that I can use ping6, traceroute6, etc with?
    >>
    >>
    >> Thanks.
    >> Dave Feustel

    >
    > Many websites about IPv6 have little "you are connecting from ..."
    > somewhere on their index page - http://www.go6.net/
    > http://www.ipv6tf.org http://www.ipv6day.org/ http://ww.ipv6.org/
    >
    > My fave for checking is the venerable dancing kame at
    > http://www.kame.net/ - if you get the animated turtle you've connected
    > vi IPv6, if not then you've connected via IPv4.
    >
    > http://www.sixxs.net/tools/ipv6calc/ will try to do a reverse lookup to
    > see if your nameserver is properly serving and reversing IPv6 addresses.


    I had already visited sixxs but the URL you supply above is
    particularly useful. It makes me think there is no IPv6 for me through comcast.

  7. Re: Testing IPv6

    dave wrote:
    > How do I switch to IPv6 http as suggested by kame?


    If you are using Firefox, make sure that you did not set
    network.dns.disableIPv6 = true. Or equivalent for your browser if not FFX.

    However, IPv6 is enabled by default in FFX so there shouldn't be
    anything to switch. If you have IPv6 routing set up properly you should
    get the dancing kame.

    If not, try "traceroute6 www.kame.net"[1]. If that doesn't work, do "dig
    www.kame.net IN ANY" to check if you're getting back AAAA records to DNS
    queries[2].

    If you still can't get IPv6 traffic flowing to the outside world, show
    us the results of "route -n show -inet6" and "ifconfig -a".


    [1] traceroute to www.kame.net, though this was done from windows, hop 1
    is my OpenBSD machine

    Z:\>tracert -6 www.kame.net

    Tracing route to www.kame.net [2001:200:0:8002:203:47ff:fea5:3085]
    over a maximum of 30 hops:

    1 1 ms 1 ms 3 ms bytor.wireless.fenris.cjb.net
    [2001:5c0:92cf:1::c0a8:102]
    2 29 ms 29 ms 30 ms 2001:5c0:8fff:fffe::5a3a
    3 28 ms 27 ms 29 ms 2001:5c0:0:5::114
    4 28 ms 28 ms 28 ms
    if-5-0-1.6bb1.mtt-montreal.ipv6.teleglobe.net [2001:5a0:300::5]
    5 29 ms 28 ms 28 ms
    if-1-0.mcore3.mtt-montreal.ipv6.teleglobe.net [2001:5a0:300:100::1]
    6 35 ms 37 ms 35 ms
    if-13-0.mcore4.nqt-newyork.ipv6.teleglobe.net [2001:5a0:300:100::2]
    7 228 ms 134 ms 57 ms 2001:5a0:400:200::1
    8 39 ms 39 ms 40 ms 2001:5a0:600:200::1
    9 42 ms 40 ms 41 ms 2001:5a0:600:200::6
    10 41 ms 40 ms 41 ms 2001:5a0:600::5
    11 57 ms 57 ms 54 ms ge-0.equi6ix.asbnva01.us.bb.verio.net
    [2001:504:0:2::2914:1]
    12 56 ms 56 ms 56 ms xe-3-0-0.r20.asbnva01.us.bb.gin.ntt.net
    [2001:418:0:2000::f1]
    13 129 ms 200 ms 204 ms as-0.r20.snjsca04.us.bb.gin.ntt.net
    [2001:418:0:2000::1de]
    14 223 ms 203 ms 204 ms
    p64-2-0-0.r21.mlpsca01.us.bb.gin.ntt.net [2001:418:0:2000::115]
    15 229 ms 230 ms 230 ms
    p64-2-2-0.r20.tokyjp01.jp.bb.gin.ntt.net [2001:218:0:2000::ce]
    16 232 ms 231 ms 230 ms xe-0-0-0.a20.tokyjp01.jp.ra.gin.ntt.net
    [2001:218:0:6000::1a]
    17 231 ms 231 ms 231 ms
    ge-1-0-0-8.a13.tokyjp01.jp.ra.gin.ntt.net [2001:218:2000:3008::14]
    18 220 ms 220 ms 220 ms 2001:218:2000:5000::92
    19 223 ms 224 ms 225 ms ve-4.nec2.yagami.wide.ad.jp
    [2001:200:0:1c04:230:13ff:feae:5b]
    20 223 ms 222 ms 223 ms lo0.alaxala1.k2.wide.ad.jp
    [2001:200:0:4800::7800:1]
    21 219 ms 221 ms 220 ms orange.kame.net
    [2001:200:0:8002:203:47ff:fea5:3085]

    [2] dig www.kame.net IN ANY

    [cory@bytor] 19:08:37 [102]~> dig www.kame.net IN ANY

    ; <<>> DiG 9.3.2-P1 <<>> www.kame.net IN ANY
    ;; global options: printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55273
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 4

    ;; QUESTION SECTION:
    ;www.kame.net. IN ANY

    ;; ANSWER SECTION:
    www.kame.net. 85605 IN A 203.178.141.194
    www.kame.net. 71625 IN AAAA
    2001:200:0:8002:203:47ff:fea5:3085

    ;; AUTHORITY SECTION:
    kame.net. 71625 IN NS ns1.itojun.org.
    kame.net. 71625 IN NS orange.kame.net.

    ;; ADDITIONAL SECTION:
    ns1.itojun.org. 163738 IN A 202.232.15.92
    orange.kame.net. 3613 IN A 203.178.141.194
    orange.kame.net. 71625 IN AAAA 2001:200:0:8000::42
    orange.kame.net. 71625 IN AAAA
    2001:200:0:8002:203:47ff:fea5:3085

    ;; Query time: 8 msec
    ;; SERVER: 192.168.0.1#53(192.168.0.1)
    ;; WHEN: Thu Feb 8 19:09:22 2007
    ;; MSG SIZE rcvd: 211

  8. Re: Testing IPv6

    dave writes:

    > I had already visited sixxs but the URL you supply above is
    > particularly useful. It makes me think there is no IPv6 for me through
    > comcast.


    Few ISPs supply native IPv6. My ISP does supply an IPv6 tunnel
    as do places like HE (google HE ipv6 for info). The tunnel consists
    of an IP address (the IP tunnel endpoint), 2 ipv6 addresses (the IPv6
    tunnel endpoints), and your ipv6 assigned addresses. In my case
    the info is this:

    208.201.244.208 IP address of my gateway machine
    2001:05a8:0:1::0123 my IPv6 tunnel address

    208.201.234.221 ISP IP tunnel address
    2001:05a8:0:1::0122 ISP IPv6 tunnel address

    Setup is done in hostname.gif0

    --------
    tunnel 208.201.244.208 208.201.234.221
    inet6 alias 2001:05a8:0:1::0123 128
    dest 2001:05a8:0:1::0122
    ! route add -inet6 default ::1
    ! route change -inet6 default -ifp gif0
    --------

    The first line sets up the tunnel
    the second assigns my ipv6 tunnel address
    the third line assigns the ISP ipv6 tunnel address
    the forth line prepares an ipv6 default route
    the final line changes the ipv6 default route to use interface gif0

    // marc

  9. Re: Testing IPv6

    Marco S Hyman wrote:
    > dave writes:
    >
    >> I had already visited sixxs but the URL you supply above is
    >> particularly useful. It makes me think there is no IPv6 for me through
    >> comcast.

    >
    > Few ISPs supply native IPv6. My ISP does supply an IPv6 tunnel
    > as do places like HE (google HE ipv6 for info). The tunnel consists
    > of an IP address (the IP tunnel endpoint), 2 ipv6 addresses (the IPv6
    > tunnel endpoints), and your ipv6 assigned addresses. In my case
    > the info is this:
    >
    > 208.201.244.208 IP address of my gateway machine
    > 2001:05a8:0:1::0123 my IPv6 tunnel address
    >
    > 208.201.234.221 ISP IP tunnel address
    > 2001:05a8:0:1::0122 ISP IPv6 tunnel address
    >
    > Setup is done in hostname.gif0
    >
    > --------
    > tunnel 208.201.244.208 208.201.234.221
    > inet6 alias 2001:05a8:0:1::0123 128
    > dest 2001:05a8:0:1::0122
    > ! route add -inet6 default ::1
    > ! route change -inet6 default -ifp gif0
    > --------
    >
    > The first line sets up the tunnel
    > the second assigns my ipv6 tunnel address
    > the third line assigns the ISP ipv6 tunnel address
    > the forth line prepares an ipv6 default route
    > the final line changes the ipv6 default route to use interface gif0
    >
    > // marc


    This is what I call a high info density post!
    Thanks!

  10. Re: Testing IPv6

    On 09 Feb 2007 12:55:04 -0800, Marco S Hyman wrote:
    >Few ISPs supply native IPv6. My ISP does supply an IPv6 tunnel
    >as do places like HE (google HE ipv6 for info). The tunnel consists
    >of an IP address (the IP tunnel endpoint), 2 ipv6 addresses (the IPv6
    >tunnel endpoints), and your ipv6 assigned addresses. In my case
    >the info is this:
    >
    >208.201.244.208 IP address of my gateway machine
    >2001:05a8:0:1::0123 my IPv6 tunnel address
    >
    >208.201.234.221 ISP IP tunnel address
    >2001:05a8:0:1::0122 ISP IPv6 tunnel address
    >
    >Setup is done in hostname.gif0
    >
    >--------
    >tunnel 208.201.244.208 208.201.234.221
    >inet6 alias 2001:05a8:0:1::0123 128
    >dest 2001:05a8:0:1::0122
    >! route add -inet6 default ::1
    >! route change -inet6 default -ifp gif0
    >--------


    Slightly shorter:

    up tunnel 208.201.244.208 208.201.234.221
    up inet6 2001:05a8:0:1::0123 2001:05a8:0:1::0122 prefixlen 128
    !route -qn add -inet6 default 2001:05a8:0:1::0122

    --
    Maurice

  11. Re: Testing IPv6

    Maurice Janssen writes:

    > >tunnel 208.201.244.208 208.201.234.221
    > >inet6 alias 2001:05a8:0:1::0123 128
    > >dest 2001:05a8:0:1::0122
    > >! route add -inet6 default ::1
    > >! route change -inet6 default -ifp gif0

    >
    > Slightly shorter:
    >
    > up tunnel 208.201.244.208 208.201.234.221
    > up inet6 2001:05a8:0:1::0123 2001:05a8:0:1::0122 prefixlen 128
    > !route -qn add -inet6 default 2001:05a8:0:1::0122


    Shorter isn't always better. If a default route exists the route
    command in the shorter version will fail. With the longer version
    the route add will fail, but the route change will still take effect,
    insuring that the default route is set as desired.

    // marc

  12. Re: Testing IPv6

    On 11 Feb 2007 21:28:11 -0800, Marco S Hyman wrote:
    >Maurice Janssen writes:
    >
    >> >tunnel 208.201.244.208 208.201.234.221
    >> >inet6 alias 2001:05a8:0:1::0123 128
    >> >dest 2001:05a8:0:1::0122
    >> >! route add -inet6 default ::1
    >> >! route change -inet6 default -ifp gif0

    >>
    >> Slightly shorter:
    >>
    >> up tunnel 208.201.244.208 208.201.234.221
    >> up inet6 2001:05a8:0:1::0123 2001:05a8:0:1::0122 prefixlen 128
    >> !route -qn add -inet6 default 2001:05a8:0:1::0122

    >
    >Shorter isn't always better.


    That's true.

    >If a default route exists the route
    >command in the shorter version will fail. With the longer version
    >the route add will fail, but the route change will still take effect,
    >insuring that the default route is set as desired.


    That's a good point, but in my case the default route isn't going to
    change anytime soon. I prefer the single route command because it's
    easier for me to read and understand.

    --
    Maurice

+ Reply to Thread