4 ms·
As far as I can tell, IPv6 is already here. My home network has IPv6, and all my servers have IPv6. Doing this amounted to one line of config on the servers,
by jrockway 16y ago
As far as I can tell, IPv6 is already here. My home network has IPv6, and all my servers have IPv6. Doing this amounted to one line of config on the servers, two lines of config on my router (one to tell it the ipv6 address, one to start rtadvd), and no configuration on my workstations.
And, I have better IPv6 connectivity from home than IPv4. Traceroute to Google:
$ traceroute google.com
traceroute to google.com (209.85.225.104), 30 hops max, 60 byte packets
1 blinky.internal (10.0.0.2) 0.267 ms 0.249 ms 0.230 ms
2 dsl253-036-001.chi1.dsl.speakeasy.net (66.253.36.1) 15.046 ms 19.018 ms 23.002 ms
3 220.ge-0-1-0.cr2.chi1.speakeasy.net (69.17.83.153) 16.991 ms 20.965 ms 24.950 ms
4 core1-2-2-0.ord.net.google.com (206.223.119.21) 26.932 ms 28.911 ms 30.893 ms
5 72.14.236.178 (72.14.236.178) 32.875 ms 72.14.236.176 (72.14.236.176) 87.863 ms 72.14.236.178 (72.14.236.178) 34.822 ms
6 209.85.241.22 (209.85.241.22) 37.802 ms 72.14.232.141 (72.14.232.141) 39.334 ms 41.312 ms
7 209.85.241.35 (209.85.241.35) 43.294 ms 209.85.241.29 (209.85.241.29) 23.635 ms 23.689 ms
8 66.249.95.138 (66.249.95.138) 27.670 ms 72.14.239.18 (72.14.239.18) 29.652 ms 209.85.248.102 (209.85.248.102) 31.626 ms
9 iy-in-f104.1e100.net (209.85.225.104) 33.608 ms 35.591 ms 37.573 ms
Traceroute6 to IPv6 Google:
$ traceroute6 ipv6.google.com
traceroute to ipv6.google.com (2001:4860:b007::68), 30 hops max, 80 byte packets
1 blinky.jrock.us (2001:470:1f11:488::1) 0.273 ms 0.246 ms 0.228 ms
2 jrockway-1.tunnel.tserv9.chi1.ipv6.he.net (2001:470:1f10:488::1) 17.464 ms 19.492 ms 21.437 ms
3 gige-g3-4.core1.chi1.ipv6.he.net (2001:470:0:6e::1) 31.410 ms 33.398 ms 35.383 ms
4 * * *
5 2001:4860::1:0:3f7 (2001:4860::1:0:3f7) 29.284 ms 2001:4860::1:0:92e (2001:4860::1:0:92e) 37.278 ms 2001:4860::1:0:3f7 (2001:4860::1:0:3f7) 39.263 ms
6 2001:4860::1:0:1d1 (2001:4860::1:0:1d1) 46.248 ms 2001:4860::1:0:2776 (2001:4860::1:0:2776) 47.653 ms 49.593 ms
7 2001:4860::38 (2001:4860::38) 51.579 ms 36.400 ms 36.944 ms
8 2001:4860:0:1::f (2001:4860:0:1::f) 35.849 ms 2001:4860:0:1::d (2001:4860:0:1::d) 33.996 ms 33.369 ms
9 iy-in-x68.1e100.net (2001:4860:b007::68) 27.974 ms 31.954 ms 31.951 ms
Same number of hops, but less latency!
- ay 16y agoNice to see the specific data. Another data point: last year at FOSDEM we had more than just a couple of v6-connected hosts, here're some stats I kept for fun: http://stdio.be/onsite.fosdem.net/ http://stdio.be/onsite.fosdem.net/ Needless to say, noone ran after the conference participants to upgrade the software on their devices.