BF> Another factor to take into account is that when using a tunnel, BF> you effectively are connected via proxy.
I don't think that is correct. With a proxy one hides behind the IP adress of a proxy server. But that is not the case with tunneled IPv6. One still has a unique address that uniquely identifies the user.
BF> That means for instance that I cannot watch anything from Netflix BF> on my computer, since they cannot verify that it's really me who tries BF> to watch it.
I think the problem is failing geolocation. My he.net address locates me in the US despite the fact that the POP is located in Amsterdam.
BF> I have to disable IPv6 first and get a direct IPv4 connection.
Then they know you are in Sweden, Europe. The IPv4 geolocation is pretty accurate. Contrary to the IPv6 geolocation. The database is still far from complete.
BF> Yet another reason why we must all strive for native IPv6. Damn all BF> the lazy ISPs to hell... :(
My ISP has been saying that they will roll out IPv6 "later this year" for over five years now. I have to give it to them, they are actually doing it now. It is getting closer. Very close actually, today I discovered that my next door neighbour has native IPv6 from my ISP. Rumour has it that their backbone and all the CMTSs are now IPv6 enabled. The bottlenecks is the CPEs. They presently have ONE modem/router that has a working implementation supporting IPv6. My neighbour happens to have that model. The Ubee 321b. I happen to have a Cisco EPC3928. They have no IPv6 firmware for that one yet. Very frustrating, my neighbour doesn't even know what IPv6 is. I am a certified sage. I want it. He could not care less. He has it, I have not. AARGH!
