Dual stack statistics?

Eric Vyncke (evyncke) evyncke at cisco.com
Tue Jan 29 09:27:16 CET 2013


Sorry for late reply...

It seems that we (6lab.cisco.com) have to fix our IPV6 connectivity indeed ;-) 

Forwarding this information internally

-éric

> -----Original Message-----
> From: ipv6-ops-bounces+evyncke=cisco.com at lists.cluenet.de [mailto:ipv6-ops-
> bounces+evyncke=cisco.com at lists.cluenet.de] On Behalf Of Tore Anderson
> Sent: lundi 28 janvier 2013 14:59
> To: Ignatios Souvatzis
> Cc: IPv6 OPS
> Subject: Re: Dual stack statistics?
> 
> * Ignatios Souvatzis
> 
> > Side note: this claims me to connect via IPv4. Investigating shows
> > that it connects via map46.cisco.com, which makes me suspect that the
> > connection discovery <magicitem> only sees the connection from the
> > map46.
> 
> Using Chrome by any chance? If so there's a perfectly good explanation for
> it, map46.cisco.com's IPv6 connectivity quite simply sucks. This is on
> native v6 in Norway:
> 
> tore at envy:~$ nping -4 --tcp-connect -c 5 6lab.cisco.com | grep rtt Max rtt:
> 47.510ms | Min rtt: 41.501ms | Avg rtt: 44.245ms tore at envy:~$ nping -6 --
> tcp-connect -c 5 6lab.cisco.com | grep rtt Max rtt: 370.014ms | Min rtt:
> 368.259ms | Avg rtt: 368.913ms
> 
> 300ms is AFAIK the cut-off time when Chrome's Happy Eyeballs implementation
> decides it's not worth waiting for an IPv6 connection to establish any
> longer.
> 
> Tore



More information about the ipv6-ops mailing list