4 ms·
I've been running dual ipv6 on comcast for about 2 years now. Now that I've got el capitan installed my traffic is > 50% ipv6
by mitchty 11y ago
I've been running dual ipv6 on comcast for about 2 years now. Now that I've got el capitan installed my traffic is > 50% ipv6
- simoncion 11y agoI've been doing the same for many years (and used a Hurricane Electric 6to4 tunnel before that). Haven't bothered to look at my traffic mix, but I expect it's similar to yours. Thing is, there are still routers out there that don't support v6 out of the box, and -just as there are network admins who DROP traffic because doing so "keeps them hidden from hackers"- some people keep v6 support disabled because of cargo-cult security concerns. (Others keep v6 off because some or all of their systems are misconfigured and cannot be fixed, or their ISP is incompetent and hasn't configured their network correctly. These are reasonable reasons to keep v6 off. ;) )
- dorfsmay 11y agoI used to run IPv6 through an HE tunnel at home until YouTube became really really slow: Google had enable IPv6 on YouTube, so the traffic was now going through the tunnel. I had to get rid of my tunnel for everything but my servers that day!
- nissehulth 11y agoSimilar problem here, I can't use Netflix over IPv6 because that makes them believe I'm in the "wrong" country. Kinda weird since a whois on my IPv6 ranges gives the same country as my IPv4 address. Tried to escalate this at Netflix support but never got anywhere.
- simoncion 11y agoI expect that Netflix's technical staff would be very interested in this. Have you tried -ugh- tweeting at them and telling them that their IPv6 geolocation information is wrong for your address range?
- nissehulth 11y agoDidn't try tweeting, will try that. I'm sure the techs at Netflix would like to know and I'm sure they would fix it but it seems to be quite difficult to get pass their first-level support.
- simoncion 11y agoI had that happen... except that I had been running my HE.net tunnel for years. Did some diagnostics... found that the endpoint I had selected (in Fremont, CA) was being geolocated by Google as somewhere in an ex-Soviet Bloc country. Changed the endpoint, and YouTube was back up to full speed. I've had more trouble with Comcast deliberately throttling YouTube downloads [0] than I ever had with that HE.net tunnel. [0] I'm in a position where I can verify that it's Comcast's problem... grab the URL for the actual video file (which dictates the CDN location) and wget it at a high-bandwidth site run by a large, independent third party that's not in the business of doing hosting. Notice that the download at the site saturates a 100mbit connection, whereas at home it hardly hits 500kbit/s. Frown.
- dorfsmay 11y agoGood point, I know that there's now an HE presence in Calgary, but my understanding is that no ISP is peering in that exchange. I'll have to give it a try to confirm.
- Osiris 11y agoGoogle's OnHub device doesn't support IPv6. I was shocked when I first installed it.