On Apr 30, 2014, at 12:37 AM, Mark Jenkins <[email protected]> wrote: > > A note that any decent OS lets you automatically choose dual-stack vs single > stack depending on which wifi network you're on -- well, at least > NetworkManger for GNU/Linux does this.... > Isn't that a bit histrionic?
Many 'newer' OS releases have v6 enabled by default but some don't allow you to easily turn them off. Especially mobile junk (Android 4.4 [only tried with my nexus 7], iOS [anything], AppleTV etc.). If you have a dual stack configuration your device will lookup the AAAA _first_ by protocol choice convention and Netflix will compare your source v6 address to it's geo-ip tables which are largely out of date with reality. This can be problematic for some uses of NetFlix of which I have experience with... the solution for those devices is to setup a v4 only vlan and put the AppleTV's in that VLAN (then expected/original behaviour resumes). I've tried blackholing NetFlix's v6 space with _limited_ success but I would have to setup a local DNS proxy and filter out the NetFlix AAAA's to _really_ solve it natively... It doesn't help that I'm epically lazy. Pretty much anything related to geo-ip on v6 is going to be wonky... hell v4 geo-ip in Canada isn't too great bit at least it is accurate the country scope. > So, if something like the Netflix example were a problem for anyone they > could configure their laptop to not do IPv6 at Skullspace. (useful if you do > want keep it on automatic elsewhere if it weren't a problem for you > elsewhere). > Yup... the point of making it known is to save people from pulling their hair out pre-maturely and wasting hours troubleshooting something someone already has. > That's an edge case naturally -- even more OSes will support just turning > IPv6 off regardless of location which is what I suppose most people would end > up doing if they found this a problem here. See above mobile comment. > > Word of warning to anyone thinking of dual-stacking elsewhere -- you don't > want to put folks on dual IPv4/IPv6 by default like this when your connection > comes from a tunnel or else they may try to reach some dual-stack services > via IPv6 when that's not the most efficient path to said service. (though > their are ways to set these priorities) Don't agree... HE (as of recently) has a WPG tunnel site... I was/am using tunnels and it works pretty damned well... youtube can be weird but so can my farmer DSL, a bit of MTU finagling made it less weird but I don't use youtube much. Latency to v6 stuff through the HE tunnel has been _more_ than reasonable and v4 failover doesn't have any noticeable hit for my use. > > For years many folks would make you use an ipv6.whatever.com address so you > knew which internet you were going over. > Still do but the enlightened just publish corresponding AAAA's for their 'traditional' A's... > > Do we know which big shots have stuck with it and who has joined them since? Theo is best to answer that... I don't follow v6 adoption anywhere near to his attention on it. > Dual-stack should be good at Skullspace as we're getting a native connection > (not tunneled) via VOI via Huricane Electric right? > It is native allocation from VOI's block. > This isn't to say that all tunneling is bad -- I don't think 6to4 is too bad > a thing if your ISP has its own relay server and native service thereafter. > http://en.wikipedia.org/wiki/6to4 6to4 is only needed if you are v6 only, dual-stack behaves as expected based on implementations protocol choice order. > > Though you do have to have a public IPv4 address assigned to the host doing > 6to4, so I think this means your typical home setup of private IPv4 LAN > behind a typical $30 broadband router isn't going to work for most people. > The router with public IPv4 address has to do the 6to4 and then do the fun > stateless stuff (like we now have at Skullspace) for the LAN side. Depends on how old the crappy CPE's are. Comcast in the states is pushing v6 to customers _now_ and they will do 6to4. China & Japan are pretty mature relative to v6 adoption. Regardless would love to see yourself or anyone else at the space mess around and poke at v6 issues, curiosities and observations. We have a small working group that would love to have that feedback. -- Sean _______________________________________________ SkullSpace Discuss Mailing List Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss Archive: https://groups.google.com/group/skullspace-discuss-archive/
