SoylentNews is people
SoylentNews
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? ]
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(Never thought I'd be telling Malcolm and Ilya the same thing... :-)
-- Larry Wall in <199711071819.KAA29909@wall.org>
(Score: 1) by daaelar on Thursday May 05 2016, @06:44PM
Samsung isn't writing the v6 stack for their android phones, Google is. Google supports RFC 2460 and 6101, but unfortunately is refusing to support 3315. That means SLAAC works fine, but DHCPv6 doesn't. That all has to do with Google, though. And for the record, IPv6 in the home has been exploding with new home gateways and sites supporting the stack. I'm reading this site via native v6 right now and it's working very well.
(Score: 4, Informative) by Scruffy Beard 2 on Thursday May 05 2016, @06:52PM
That reminds me: for a few months I had native ISP-provided IPv6 (IPv4 only at the moment).
It appears that the Gnome Network Manager does not support SLAC: only DHCPv6. That meant my Android and machine with no network manager just worked, while Linux Mint did not.
Not sure if it is gnome network manager because: the about message has a non-functional network at cinnamon dot org e-mail address and the words "Network Manager Applet".
(Score: 2, Touché) by daaelar on Thursday May 05 2016, @06:53PM
Bah, that should have said RFC 6106, not 6101
(Score: 2) by TheGratefulNet on Thursday May 05 2016, @06:57PM
I don't remember if we had issues with nexus phones or if it was just samsungs. we bet on samsung and we lost. they could not deliver a quality ipv6 phone stack. the details escape me as it was a few yrs ago and I was more on the unix side than the phone/android side.
still, the one who SHIPS HARDARE is where the buck stops. so I would still blame samsung. they are big enough that they have funds and resources to fix killer bugs.
as for ipv6 at home, I still see no need until I'm forced. what do I gain, exactly, by changing things and HAVING to run dual stacks? I simply don't see any benefit for the effort involved.
perhaps on a brand new setup; but to update old working ones? if it aint broke, the saying goes....
"It is now safe to switch off your computer."