APNIC reminds us that "there are now a large number of ISPs, data centres, cloud services, and software that now support IPv6" and "enabling IPv6 can be as simple as clicking a button on your WiFi router."
I turned it on, with Comcast I received an IPv6 route but no DNS server. Fortunately, Google Public DNS has unmemorable addresses, which I was able to configure manually.
2001:4860:4860::8888
2001:4860:4860::8844
It works. "There's only one thing left for you to do: Turn it on!"
[ ed: What are the alternatives to Google's Public DNS? ]
(Score: 0) by Anonymous Coward on Thursday May 05 2016, @07:44PM
Personally I like to ssh from the clouds straight into the various boxen at home behind my NAT/IPv6 router box. Not a lot of places have IPv6 so I find myself bouncing off my server in the clouds, but in my mind that's a little better than doing the port-forwarding dance.
There's probably no real rush other than you get to do the IPv6 nerd dance when you get on the IPv6 internet.
The port-forwarding dance does still work for IPv4. The vast majority of torrent peers I see are still IPv4 with the occasional IPv6 peer. I just thought I'd throw this out for passers-by who might need to do the UPnP dance for a custom-built NAT box who don't want say PfSense: MiniUPnP [tuxfamily.org].
Hmm... I've often thought that once everybody's IPv6, we'd be able to finally be successful with providing Everyman a client/server to some kind of distributed content network, say a distributed Facebook that Everyman could find "easy to use" without having to muck with port forwarding, being picky about which box it's install on in the house, etc. On the other hand, most consumer NAT devices probably have UPnP enabled by default. I guess one less thing to go wrong? I don't really know anything about this subject area.
(Score: 2) by Capt. Obvious on Friday May 06 2016, @08:55AM
So, I should turn on IPv6 because it avoids my DMZ/firewall? That sounds exactly backwards from the way I want to go..