Videoland en "Oeps, we konden de video niet afspelen. Het starten van de video is mislukt. Playservice error."

Op Videoland kreeg ik foutmelding "Oeps, we konden de video niet afspelen. Het starten van de video is mislukt. Playservice error.". 

Oorzaak gevonden: mijn IPv6-tunnel via Hurricane Electric. Na het uitschakelen van de IPv6-tunnel kon ik wel Videoland kijken.

Gokje: Videoland beschouwt the IPv6-tunnel als buiten-EU / buiten-Nederland, en weigert daarom met die cryptische melding om af te spelen. En nettere foutmelding (bijv: "u / uw IP-adres xyz komt van buiten de EU, daarom spelen we niet af") zou duidelijker zijn.

Oeps, we konden de video niet afspelen

Het starten van de video is mislukt.

Playservice error

Ah, de Videoland-app geeft een betere foutmelding als de IPv6-tunnel aanstaat: "Videoland is helaas niet beschikbaar in Verenigde Staten" 

PCExtreme with "IPv6-only" VPS ... certain IPv4 traffic is working, from behind NAT

 

PCExtreme offers "Standard Server 1GB IPv6 only" for only €1 ex VAT per month. See https://www.pcextreme.com/cloud-servers/standard

I wanted to try that out, because: how does IPv6-only work in practice? Is that working in 2022?

So I bought a VPS, and now I'm a bit disappointed: the VPS does have IPv4 after all. It's behind NAT. Just like a device on a home LAN with an ISP connection.

However, some of my IPv4 traffic failed, like git connections to special git ports (no problem via https). So I did some research by trying to connect to outside ports

Some checks: HTTP and HTTPS are both allowed:

port 80 is allowed

port 443 is allowed

SMTP Port 25 is of course not possible:

port 25 not reached

Other ports ... to find out.

Suddenly FD...-addresses, aka Unique Local IPv6 Unicast Addresses

Suddenly I saw IPv6 addresses starting with FD in my ifconfig.

On Linux 3.13:

          inet6 addr: fdd6:5a2d:3f20:0:213:77ff:fefa:63e3/64 Scope:Global
          inet6 addr: fdd6:5a2d:3f20:0:6001:f53f:1e8:3850/64 Scope:Global

and on Linux 4.14:

        inet6 fdd6:5a2d:3f20:0:ce90:a2cc:655b:416e  prefixlen 64  scopeid 0x0


It appears these are "Unique Local IPv6 Unicast Addresses", defined in RFC4193. They are world wide unique (well, at least: very probably unique), and to be used within a site.

At first I thought this was a new Linux setting, but these addresses also showed up on my old Ubuntu 14.04.
So ... what is going on? Ah, it's my new Fiber modem/router Genexis Platinum that is providing these addresses.

My use so far: you can use the FD address without specifying the interface. So handier than the FE80 addresses.

I checked a Windows 10 machine, but Windows 10 did not show these addresses. Maybe a Windows policy?

Update (2018-11-11):
Both Android and MacOSX show the FD... addresses too.

KPN IPv6 statistics shows impressive growth

The KPN IPv6 statistics for the last four months:

• 2016-08: 6.8% IPv6 
• 2016-12: 14.8% IPv6

So + 8% in four months time, or + 2% per month. Well done, KPN!

That could mean KPN could be at 14% + 12*2% = 38% IPv6 traffic at the end of 2017. We'll see in one year time.

Source of KPN graph: http://www.worldipv6launch.org/apps/ipv6week/measurement/images/graphs/KPN.png

FWIW: in the last 8 months the other Netherlands ISP Ziggo has only gone down. See here

Netherlands IPv6 - KPN versus Ziggo

Based on the measurements from Worldipv6launch you can see the status of IPv6 in the Netherlands of the two biggest ISPs KPN and Ziggo (October 2016):

Hacked together in one overview with KPN in orange and Ziggo in red:

So:

• KPN is at 9% IPv6 traffic, with a nice rise in August and September 2016: +3% in two months.
• Ziggo is at 8% IPv6 traffic, and ... going down. Ziggo's IPv6 rollout looked very promising in Q1-2016 going from about 1% to almost 9%, but since then it's declining. So that looks like Ziggo has stopped deploying IPv6 to more customers. EDIT: or Ziggo is migrating users from the UPC-AS to Ziggo-AS without giving them IPv6?

I'm curious what the situation will be in a few months. To be continued ...

Netflix, IPv6 and "You seem to be using an unblocker or proxy."

Trying to watch a movie via Netflix, I get:

Whoops, something went wrong...
Streaming Error
You seem to be using an unblocker or proxy. Please turn off any of these services and try again. For more help, visit netflix.com/proxy. 

Error Code: M7111-1331-5059

The cause seems to be that I use an IPv6 tunnel (from Hurrican Electric). See http://seclists.org/nanog/2016/Jun/26 .
Great ... :-(

I don't understand why Netflix doesn't use IPv4 to detect the real origin of the customer, and then offers the 'correct'/meant offering via IPv6.


Anyway. Workarounds:

• Turn off IPv6 altogether
• Start Chrome without IPv6 ... option does not exist anymore: https://codereview.chromium.org/1149303005
• Block IPv6 address range of Netflix / AWS
• ...

A bit more info on German site Golem: http://www.golem.de/news/geoblocking-netflix-sperrt-nutzer-von-ipv6-tunneln-1606-121376.html

IPv6 traffic is the majority of my Internet traffic

Interesting: IPv6 traffic is the majority of my Internet traffic at home: 54%. And IPv4 is the minority.

Calculation (thanks to the MRTG monitoring of my router):

• IPv6 traffic has an average of 366.0 kb/s
• Total IPv4+IPv6 traffic has an average of 676.4 kb/s

So divide those numbers IPv6 by total traffic: 366/676 = 54% IPv6 traffic.

The explanation is quite easy: the well-known high-traffic sites (youtube, google, facebook) are IPv6-enabled.

PS: If "an average 676.4 kb/s" sounds low: that's almost 7GB per day. Rule of thumb: 100 kbps average is 1GB per day.

MRTG overview of my traffic: Green is total traffic, Blue is IPv6. Note there are only two IPv4-spikes.

Youtube: IPv6-only: