World IPv6 Launch, June 6th 2012

Jared Mauch jared at puck.nether.net
Wed Jan 18 14:31:39 CET 2012


It does seem to be working for me now.

puck:~$ curl -v http://www.worldipv6launch.org/
* About to connect() to www.worldipv6launch.org port 80 (#0)
*   Trying 2600:1408:3:1::76d6:a43b... connected
* Connected to www.worldipv6launch.org (2600:1408:3:1::76d6:a43b) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-redhat-linux-gnu) libcurl/7.21.0 NSS/3.12.10.0 zlib/1.2.5 libidn/1.18 libssh2/1.2.4
> Host: www.worldipv6launch.org
> Accept: */*
> 
< HTTP/1.1 200 OK
< Server: Apache/2.2.16 (Debian)
< X-Powered-By: PHP/5.3.3-7+squeeze3
< X-Pingback: http://www.worldipv6launch.org/xmlrpc.php
< Content-Type: text/html; charset=UTF-8
< Date: Wed, 18 Jan 2012 13:30:56 GMT
< Content-Length: 16762
< Connection: keep-alive
< 
<!DOCTYPE html>
<html dir="ltr" lang="en-US">
<head>
<meta charset="UTF-8" />
<title>World IPv6 Launch</title>

- Jared

On Jan 18, 2012, at 7:58 AM, Bernhard Schmidt wrote:

> Am 18.01.2012 13:34, schrieb Jared Mauch:
>> I'm guessing someone needs to throw that lever. Hopefully they can work together to make that happen!
> 
> Has AAAA now, but geolocation isn't working that great and the site is
> broken for me. I think that's a layer7+ issue though.
> 
> traceroute to www.worldipv6launch.org (2600:1408:7::170f:871) from
> 2001:4ca0:0:f000:221:9bff:fe80:d1cd, port 33434, from port 53480, 30
> hops max, 60 bytes packets
> 1  vl-23.vss1-2wr.lrz.de (2001:4ca0:0:f000::1)  0.517 ms
> 2  vl-3066.csr1-2wr.lrz.de (2001:4ca0:0:66::1)  0.572 ms
> 3  xr-gar1-pc110-108.x-win.dfn.de (2001:638:c:a003::1)  0.543 ms
> 4  zr-fra1-te0-7-0-1.x-win.dfn.de (2001:638:c:c043::2)  9.427 ms
> 5  xe-8-1-1.edge5.Frankfurt1.Level3.net (2001:1900:5:2:2::825)  9.114 ms
> 6  vl-70.edge3.Frankfurt1.Level3.net (2001:1900:104:6::8)  8.968 ms
> 7  vl-4060.edge4.Paris1.Level3.net (2001:1900:5:1::216)  18.257 ms
> 8  vl-4081.edge3.Paris1.Level3.net (2001:1900:5:1::12d)  18.824 ms
> 9  vl-4086.car1.Washington1.Level3.net (2001:1900:6:1::16)  100.074 ms
> 10  ae-1-4046.edge1.Washington12.Level3.net (2001:1900:4:1::3b1)  98.061 ms
> 11  mci-level3-40G.WashingtonDC12.Level3.net (2001:1900:4:3::126)
> 103.860 ms
> 12  2600:803:96f::16 (2600:803:96f::16)  107.448 ms
> 13  2600:803:96f::16 (2600:803:96f::16)  106.868 ms
> 14  2600:1408:7::170f:871 (2600:1408:7::170f:871)  105.083 ms
> 
> LRZ lxbsc02:~ (130) % curl -v www.worldipv6launch.org
> * About to connect() to www.worldipv6launch.org port 80 (#0)
> *   Trying 2600:1408:7::170f:871... connected
> * Connected to www.worldipv6launch.org (2600:1408:7::170f:871) port 80 (#0)
>> GET / HTTP/1.1
>> User-Agent: curl/7.21.6 (x86_64-pc-linux-gnu) libcurl/7.21.6
> OpenSSL/1.0.0e zlib/1.2.3.4 libidn/1.22 librtmp/2.3
>> Host: www.worldipv6launch.org
>> Accept: */*
>> 
> [hangs here for a few minutes]
> 
> An error occurred while processing your request.
> 
> Reference #97.b5080f17.1326891400.376e524
> 
>> From another site the geolocation is great, but it still hangs.
> 
> traceroute to www.worldipv6launch.org (2a02:26f0:3::5435:af08) from
> 2001:1b10:100:3::1:2, port 33434, from port 46729, 30 hops max, 60 byte
> packets
> 1  backbone2-vl-15.teleport-iabg.de (2001:1b10:100:3::12)  0.474 ms
> 2  gi3-6-309.r1.muc3.m-online.net (2001:a60:0:201::1:1)  0.413 ms
> 3  r3.muc2.m-online.net (2001:a60::89:203)  0.825 ms
> 4  alpix-muc.netarch.akamai.com (2001:7f8:44::51cc:0:0)  0.993 ms
> 5  2a02:26f0:3::5435:af08 (2a02:26f0:3::5435:af08)  0.689 ms
> 
> Best Regards,
> Bernhard



More information about the ipv6-ops mailing list