Some very nice IPv6 growth as measured by Google

Jeroen Massar jeroen at
Sat Nov 8 16:43:15 CET 2014

On 2014-11-08 16:16, Tore Anderson wrote:
> * Jeroen Massar
>> On 2014-11-08 11:34, Tore Anderson wrote:
>>> * Jeroen Massar
>>>> On 2014-11-08 10:27, Yannis Nikolopoulos wrote:
>>>> [..]
>>>>> the short story here is that we're (finally) enabling IPv6 on our
>>>>> (already capable) CPEs :)
>>>> And then getting broken connectivity to Google:
>>> Non sequitur. I'd be extremely interesting in understanding how
>>> Yannis' IPv6 deployment in OTE (kudos!) could possibly impact the
>>> SixXS/HE tunnel users' ability to contact Google.
>> That is not what I wrote or intended.
>> Something unrelated to their deployment broke. But doing the
>> deployment does mean that you are now providing connectivity that
>> breaks to two major providers: Google and Akamai.
> I still do not follow. Is (or were) OTE's deployment broken?


But their deployment, just like that of anybody else, will cause them to
make Google/Akamai unreachable or at least lag in the browser of the
people that any provider

> If
> yes, is the reason for the brokenness the same as for the SixXS/HE
> users? (Is OTE using 6RD?) If no, what is the connection between OTE's
> deployment and the SixXS/HE problems you linked to?

The only link: they are all using IPv6.

You are trying to make this OTE link. I have never stated anything like
that. Though, you likely take that from the fact that the reply followed
in that thread.

>> Tunnels do not suck, people who have broken clusters that randomly
>> drop packets suck.
> Let me rephrase: PMTUD sucks. Tunnels suck by association, because
> they rely on PMTUD not sucking.

No. PMTUD is fine.

What sucks is 'consultants' advising blocking ICMPv6 "because that is
what we do in IPv4" and that some hardware/software gets broken once in
a while.

> (Except where the tunnel can accomodate an inner MTU of 1500.)

That is irrelevant.

And likely in the case of Akamai it has little to do with MTU, just
nodes that hang and never reply as Wireshark shows an ongoing TCP
conversation, but that is just a guess.

>> Note that even with a full 1500 MTU you will have
>> broken connectivity to Google at the moment, lots of fun thus for
>> those native deployments like Unitymedia who forcefully stuff folks
>> in DSlite land.
> This is news to me, both Google and Akamai works just fine from here
> in Norway. Could you elaborate on what broke and how I could try to
> reproduce it?

See the threads I referenced, they are still in the above quoted text.

Note that the Google case is consistent: (as good as) every IPv6
connection breaks.

The Akamai case is random: sometimes it just works as you hit good nodes
in the cluster, sometimes it breaks.

In both cases, it is hard to say what exactly breaks as only the people
in those networks/companies have access to their side of the view.

As such... here is for hoping they debug and resolve the problem.


More information about the ipv6-ops mailing list