On April 30, 2014 12:37:55 AM CDT, Mark Jenkins <[email protected]> wrote:
>On 04/29/14 23:41, Sean Cody wrote:
>> Some of you may notice that when you connect to the SKSP wifi that
>you'll get both ipv4 and ipv6
>> addresses.
>> 99.99996% of stuff should still work though there may be some
>funkiness relative to DNS and odd
>> dual-stack configurations (Netflix may have country assignment
>confusion).
>
>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....
>
>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).
>
>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.
>
>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)
>
>For years many folks would make you use an ipv6.whatever.com address so
>
>you knew which internet you were going over.
>
>It seems some folks left their AAAA records up on primary domains
>(www.whatever.com, whatever.com) on World IPv6 Launch day June 6, 2012.
>http://en.wikipedia.org/wiki/World_IPv6_Day_and_World_IPv6_Launch_Day
>
>Do we know which big shots have stuck with it and who has joined them
>since?
>
>Dual-stack should be good at Skullspace as we're getting a native
>connection (not tunneled) via VOI via Huricane Electric right?
>
>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
>
>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.
>
>
>> We will need to work out a DHCP config to deploy v6 DNS servers but
>for now the v4 DNS will serve up
>> v6 space and your machine/device should just seamlessly cope with it.
> There is NO dhcp for v6 being done
>> at this point, address and route configurations are all done
>automagically by the power of gray-skull or
>> necromancy... whichever you prefer.
>>
>> Some may notice that you get a few ipv6 addresses as well and that's
>perfectly normal, you'll have two
>> public addresses (called the SLAAC assignment and a 'privacy' address
>along with the usual link local
>> fe80:: address. This is all normal. :)
>
>Link for the curious
>http://en.wikipedia.org/wiki/IPv6#Stateless_address_autoconfiguration_.28SLAAC.29
>http://en.wikipedia.org/wiki/IPv6_address#Stateless_address_autoconfiguration
>
>> The SKSP LAN is allocated 2604:4280:1:c0de/64 so if you see those
>addresses don't freak out... everything
>> is cooool.
>
>Fun fact for those of you new to IPv6: Your automatically assigned 128
>bit IPv6 address on our LAN is derived from your ethernet MAC address
>(http://en.wikipedia.org/wiki/MAC_address) which is 48bits.
>
>The 64 bit prefix cited above takes up the most significant 64 bits,
>your 48 bit MAC address takes up another chunk of it and an algorithm
>fills in the rest.
>
>Use ye old favourite tool for comparing MAC address to automatically
>assigned IPv6 addresses to see this in action.
>
>
>Mark
>
>p.s, I don't suppose there is globally routed IPv6 multicast happening
>with our router, VOIs router, Huricane Electric's router etc? Would be
>nice to get a reservation and start hackerspace.tv someday..... Dead in
>
>the water like IPv4 globally routed multicast?
>
>
>_______________________________________________
>SkullSpace Discuss Mailing List
>Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
>Archive: https://groups.google.com/group/skullspace-discuss-archive/
1. I disagree - everyone should be making IPv6 the default for everything at
this time. Ripping the bandage off quickly will involve some pain, but will be
over a lot faster than tearing it off one hair at a time. It's a catch-22
right now: no one supports v6 because no one uses v6 because no one supports v6
because...
2. For native IPv6 connections, v6 is typically the better path based on what
I've seen over the last year. Tunnels need not apply :-(.
3. Global multicast will probably always be a lame duck. You give up way too
much control as a network operator by participating.
-Adam
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
SkullSpace Discuss Mailing List
Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
Archive: https://groups.google.com/group/skullspace-discuss-archive/
