Google responding with IPv6

T

TheGuy

Expert Member
Joined
Sep 14, 2009
Messages
2,974
Reaction score
19
Location
Jozi
Hi Guys

I'm pinging Google and it responding with IPv6

C:\>ping www.google.com

Pinging www.google.com [2c0f:fb50:4002:801::1013] with 32 bytes of data:
Reply from 2c0f:fb50:4002:801::1013: time=380ms
Reply from 2c0f:fb50:4002:801::1013: time=398ms
Reply from 2c0f:fb50:4002:801::1013: time=380ms
Reply from 2c0f:fb50:4002:801::1013: time=380ms

Ping statistics for 2c0f:fb50:4002:801::1013:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 380ms, Maximum = 398ms, Average = 384ms

C:\>

This happening to anyone else?
 
Nope

Last login: Fri Jan 11 20:11:11 on console
-MacBook-Pro:~ $ ping www.google.com
PING www.google.com (74.125.233.19): 56 data bytes
64 bytes from 74.125.233.19: icmp_seq=0 ttl=52 time=48.198 ms
64 bytes from 74.125.233.19: icmp_seq=1 ttl=52 time=45.223 ms
64 bytes from 74.125.233.19: icmp_seq=2 ttl=52 time=46.099 ms
64 bytes from 74.125.233.19: icmp_seq=3 ttl=52 time=47.582 ms
64 bytes from 74.125.233.19: icmp_seq=4 ttl=52 time=47.333 ms
64 bytes from 74.125.233.19: icmp_seq=5 ttl=52 time=46.338 ms
64 bytes from 74.125.233.19: icmp_seq=6 ttl=52 time=48.075 ms
64 bytes from 74.125.233.19: icmp_seq=7 ttl=52 time=49.216 ms
64 bytes from 74.125.233.19: icmp_seq=8 ttl=52 time=47.529 ms
64 bytes from 74.125.233.19: icmp_seq=9 ttl=52 time=45.786 ms
64 bytes from 74.125.233.19: icmp_seq=10 ttl=52 time=44.591 ms
64 bytes from 74.125.233.19: icmp_seq=11 ttl=52 time=48.195 ms
^C
--- www.google.com ping statistics ---
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 44.591/47.014/49.216/1.334 ms
-MacBook-Pro:~ $
 
Google services have been available on IPv6 for a while now, whether you access them via IPv4 or IPv6 will depend on your ISP
 
eh? What type of connection are you on?

No SA ADSL supports native IPv6 afaik.
 
grim said:
Google services have been available on IPv6 for a while now, whether you access them via IPv4 or IPv6 will depend on your ISP
Click to expand...
Correct. Google, Facebook, Youtube, Yahoo!, Wikipedia, Bing and a whole bunch of other sites turned on IPv6 permanently on 06/06/2012. What has changed is your Internet connection :D

Your system will prefer using IPv6 if you have a working IPv6 connection. You can visit the local test-ipv6 mirror to test.

As a side note... Google publishes their IPv6 statistics. About 1.1% of all Google users are on IPv6 already but what is much more interesting is the steep upward climb of the graph!
 
AlphaJohn said:
He is most probably running 6to4 ?
Click to expand...
Probably not. They've found that 6to4 has actually been hindering the roll out of IPv6 and its busy being phased out. Windows, Mac and Linux will all generally prefer IPv4 over 6to4 unless the destination is IPv6 only.

Also - that's pretty poor latency...
TheGuy said:
Ping statistics for 2c0f:fb50:4002:801::1013:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 380ms, Maximum = 398ms, Average = 384ms
Click to expand...
Should be closer to this from ZA:
Code: 
64 bytes from 2c0f:fb50:4002:801::1013: icmp_seq=12 ttl=58 time=12.5 ms
64 bytes from 2c0f:fb50:4002:801::1013: icmp_seq=13 ttl=58 time=11.1 ms
64 bytes from 2c0f:fb50:4002:801::1013: icmp_seq=14 ttl=58 time=12.7 ms
64 bytes from 2c0f:fb50:4002:801::1013: icmp_seq=15 ttl=58 time=12.7 ms
 
Hi Guys I'm on Mweb Adsl and if I force ipv4 when pinging then my latency drops to around 70ms
 
TheGuy said:
Hi Guys I'm on Mweb Adsl and if I force ipv4 when pinging then my latency drops to around 70ms
Click to expand...
Please visit test-ipv6 and tell us what you IPv6 address is. The first 8 digits are the important ones - the rest you don't have to share ;)
 
No IPV6 on IS :s tried MWEB and it's giving no IPV6 for me either.

Does it also depend on your DSL modem?
 
Howdy,

blunt said:
No IPV6 on IS :s
Click to expand...

Well, the main problem here is that ISPs still need to populate their own dsl pools on SAIX's devices. Needless to say, SAIX is not yet supporting ipv6.. (sort of the same reasoning consumers can not yet have a static ip allocation).

So right now, if you on ADSL, the only way of doing IPv6 (for consumers) would be via a tunnel. I am running dual stack at home and my OS decides automatically whether to connect via IPv6 or IPv4 to sites. I have also seen some of my torrent trackers and peers making use of IPv6.

Of course, using a tunnel bring some disadvantages with it.

Code: 
velocidade#traceroute www.facebook.com
Translating "www.facebook.com"...domain server (168.210.2.2) [OK]

Type escape sequence to abort.
Tracing the route to star.c10r.facebook.com (2A03:2880:10:6F01:FACE:B00C:0:8)

  1 2C0F:FC00:5000:13::1 16 msec 44 msec 16 msec
  2 core1b-pkl-te-0-0-0-0-102.ipv6.isnet.net (2C0F:FC00:0:6::99) 16 msec 16 msec 16 msec
  3 2C0F:FC00:2:1D::2 196 msec 220 msec 184 msec
  4 10gigabitethernet1-1.core1.lon1.he.net (2001:7F8:4::1B1B:1) 192 msec 204 msec 192 msec
  5 2001:7F8:4::80A6:1 192 msec 200 msec 196 msec
  6 ae19.bb01.iad2.tfbnw.net (2620:0:1CFF:DEAD:BEEF::259) 272 msec 284 msec 272 msec
  7 ae8.bb05.prn1.tfbnw.net (2620:0:1CFF:DEAD:BEEF::122) 364 msec 340 msec 348 msec
  8 ae33.dr05.prn1.tfbnw.net (2620:0:1CFF:DEAD:BEEE::234) 340 msec
    ae9.dr02.prn1.tfbnw.net (2620:0:1CFF:DEAD:BEEF::43B) 340 msec
    ae33.dr05.prn1.tfbnw.net (2620:0:1CFF:DEAD:BEEE::234) 340 msec
  9 2620:0:1CFF:DEAD:BEEF::1049 352 msec 352 msec
    2620:0:1CFF:DEAD:BEEF::1039 376 msec
 10  *  *  *

Code: 
velocidade#traceroute ip www.facebook.com

Translating "www.facebook.com"...domain server (168.210.2.2) [OK]

Type escape sequence to abort.
Tracing the route to star.c10r.facebook.com (31.13.80.23)

  1 196-210-138-129.dynamic.isadsl.co.za (196.210.138.129) 8 msec 8 msec 8 msec
  2 196.38.73.85 8 msec 8 msec 8 msec
  3 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 8 msec 8 msec 8 msec
  4 core2-pkl-t0-7-0-0.ip.isnet.net (168.209.1.163) 12 msec 12 msec 12 msec
  5 168.209.201.73 188 msec 184 msec 188 msec
  6 xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net (83.231.235.221) 184 msec 180 msec 180 msec
  7 ae-4.r23.londen03.uk.bb.gin.ntt.net (129.250.5.40) 180 msec 184 msec 184 msec
  8 as-0.r20.parsfr01.fr.bb.gin.ntt.net (129.250.5.9) 192 msec 188 msec 188 msec
  9 ae-0.r21.parsfr01.fr.bb.gin.ntt.net (129.250.2.181) 196 msec 196 msec 192 msec
 10 po-2.r01.parsfr02.fr.bb.gin.ntt.net (129.250.4.178) 188 msec 204 msec 192 msec
 11 82.112.96.146 192 msec 192 msec 192 msec
 12 ae1.bb01.cdg1.tfbnw.net (204.15.22.194) 192 msec
    ae1.bb02.cdg1.tfbnw.net (204.15.22.198) 196 msec
    ae1.bb01.cdg1.tfbnw.net (204.15.22.194) 200 msec
 13 ae1.pr02.cdg1.tfbnw.net (204.15.23.13) 236 msec 192 msec
    ae2.pr02.cdg1.tfbnw.net (204.15.23.15) 188 msec
 14 po126.msw01.02.cdg1.tfbnw.net (31.13.27.93) 192 msec 192 msec 200 msec
 15  *  *  *

As for business dsl, I would imagine any ISP can throw in IPv6 allocation over that l2tp.

blunt said:
Does it also depend on your DSL modem?
Click to expand...

Yes as well as your OS (although (most) latest operating systems do support dual stacking)



--
The Janitor @ PluGG

PluGG - Consumer division of Internet Solutions
[email protected] | [email protected]
www.plugg.co.za | 08611 PluGG | www.is.co.za

#include <std-disclaimer.h>
 
Using IPV6 as addresses, yet responding with 32bytes of data, so converted to IPV4 for your convenience? IPV6 is coming, but not quite there.
 
TheGuy said:
2002:2985
Click to expand...
Interesting... that is definitely a 6to4 address and you're on Mweb right? ;) What modem or device are you using to dial your account?

FlatspinZA said:
IPV6 is coming, but not quite there.
Click to expand...
Why do you say that? I use IPv6 to reach: MyBB, email, Google, Facebook, Youtube and dozen other things I use on a daily basis. :D
 
Last edited:
ambo said:
Interesting... that is definitely a 6to4 address and you're on Mweb right? ;) What modem or device are you using to dial your account?

Why do you say that? I use IPv6 to reach: MyBB, email, Google, Facebook, Youtube and dozen other things I use on a daily basis. :D
Click to expand...

'As of late November 2012, IPv6 traffic share was reported to be approaching 1%.'

Source

Well before we can switch over, all devices on the Internet need to IPV6 capable, and because of all the legacy IPV4 devices, that's probably going to take a little while longer.

Anyway, I shouldn't post when I am plonkered - the omitted blocks are zeros.
 
ambo said:
Interesting... that is definitely a 6to4 address and you're on Mweb right? ;) What modem or device are you using to dial your account?

Why do you say that? I use IPv6 to reach: MyBB, email, Google, Facebook, Youtube and dozen other things I use on a daily basis. :D
Click to expand...

I'm using a linksys router but it must something that changed on Mweb's side as I havn't made any changes appart from switching to win 8
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X