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).

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. :)

The SKSP LAN is allocated 2604:4280:1:c0de/64 so if you see those addresses 
don't freak out... everything is cooool.
Also note you don't have the 'obscurity' of NAT as all v6 addresses are public 
and routed, so turn on your host based firewall.

For those in the DMZ feel free to auto setup an interface for v6, if your v6 
stack has autoconfig enabled you should get the router advertisement as well 
but otherwise you can statically use 2604:4280:1:c0de::1 as the gateway.

If you've always wanted to mess around with v6, have at it. :)
I will be setting up a v6 only access point on the CDC router for messing 
around with and learning to manage single stack v6 issues.

Thanks to Theo and Colin S for helping us do the needful on this. 

Here is an example setup from my machine (at the space):

ifconfig em0
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        lladdr 00:14:5e:41:fc:70
        priority: 0
        groups: egress
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet6 fe80::214:5eff:fe41:fc70%em0 prefixlen 64 scopeid 0x1   <---- 
link local
        inet6 2604:4280:1:c0de:214:5eff:fe41:fc70 prefixlen 64 autoconf pltime 
604340 vltime 2591540 <--- v6 SLAAC
        inet6 2604:4280:1:c0de:1028:8e0c:5de6:51f9 prefixlen 64 autoconf 
autoconfprivacy pltime 67708 vltime 586451 <--- v6 SLAAC Privacy
        inet6 2604:4280:1:c0de:3141:5926:5358:9793 prefixlen 64 <---- v6 
static/manual assignment
        inet6 2604:4280:1:c0de::314 prefixlen 64 <---- v6 static/manual 
assignment, zero shortcut
        inet 206.220.196.58 netmask 0xfffffff0 broadcast 206.220.196.63 <---- 
v4 static assignment

cat /etc/resolv.conf
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844
nameserver 8.8.8.8      
nameserver 8.8.4.4
lookup file bind

We've tested this evening with iOS, Android, Windows (whatever is on the shared 
machine by the projector), MacOS X and OpenBSD so we're relatively confident it 
will work, for you as is.

If you want a nice test site... http://test-ipv6.com is very helpful.  
Theo has some kind of chicken quail site thing he uses which would be another 
test site choice.

-- 
Sean
P.S. Before you assume any/all problems are v6 related... turn off the v6 stack 
on your host and try again to validate the issue and send a note to netops@ 
with any well described problems.  I suppose you could email me too... though I 
don't have an SLA. :P
_______________________________________________
SkullSpace Discuss Mailing List
Help: http://www.skullspace.ca/wiki/index.php/Mailing_List#Discuss
Archive: https://groups.google.com/group/skullspace-discuss-archive/

Reply via email to