Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

More than 1/3 of all access to Google is now over IPv6

google.com

Post reply on HN
Print view View original

191–200 of 237 posts

Re: More than 1/3 of all access to Google is now over IPv6

#191

Post by dbt00 »

richardwhiuk wrote: post #165
ghshephard wrote: post #161

Earlier quoted context omitted.

Well - you may have overlapping RFC 4193, but if your network engineers have done their job well, you are randomly choosing from a big honking FD/8 address space, and the odds of a collision are statistically very unlikely.

FD/8 space? You mean 10.0.0.0/8? No the odds of a collision on 10.0.0.0/8 are high because: - Both corporations probably started allocating from the top - Both corporations probably allocated huge subnets.

No, FD00::/8. Read RFC 4193. He's talking about the IPv6 solution, not the IPv4 problem.

Re: More than 1/3 of all access to Google is now over IPv6

#192

Post by dragonwriter »

orf wrote: post #189
avianlyric wrote: post #160

Earlier quoted context omitted.

I’m confused why would this happen? > The IPv6 enterprise argument is 'You might one day have to renumber some devices because some other enterprise might have set up overlapping addresses, therefore you definitely have to renumber everything now, and oh, every time the ISP decides they don't like you, because private addresses are icky'. Obviously that's a hard sell. If you’re an enterprise you would just get your o…

> It’s not like they’re expensive or hard to get hold of. For context, apparently a block of 79,228,162,514,264,337,593,543,950,336 addresses (/48) is about 100$ a year.

79 octillion addresses ought to be enough for anybody.

Re: More than 1/3 of all access to Google is now over IPv6

#193

Post by [deleted] »

dragonwriter wrote: post #192
orf wrote: post #189

Earlier quoted context omitted.

> It’s not like they’re expensive or hard to get hold of. For context, apparently a block of 79,228,162,514,264,337,593,543,950,336 addresses (/48) is about 100$ a year.

79 octillion addresses ought to be enough for anybody.

[deleted]

Re: More than 1/3 of all access to Google is now over IPv6

#194

Post by ed25519FUUU »

myself248 wrote: post #179

Just turn off ipv4 for one minute every day. Next month, increase it to 2 minutes. A minor inconvenience, but a major motivator.

Punish people that don't care and have no control over whether or not their ISP supports IPv6?

IPv6 affects everyday internet users exactly 0%. It's rational for them not to care about it.

Re: More than 1/3 of all access to Google is now over IPv6

#195

Post by jedberg »

Bnshsysjab wrote: post #176
lma21 wrote: post #94

Earlier quoted context omitted.

Excuse my ignorance, on what layer do we need IPv6 when deploying our apps/systems/whatever on AWS? Is IPv4 becoming a severe problem for such things?

Gmail blocks my mailserver, I recently discovered it’s the lack of ipv6 that causes it.

If your mail server is in AWS, it's not ipv6 that is the problem per se. It's that google has blocked the entire AWS address space. To be fair, you shouldn't be sending email from AWS without going through SES, which has it's own address space and has specific deals for deliverability to all the big mail recipients, like gmail and hotmail.

Re: More than 1/3 of all access to Google is now over IPv6

#196

Post by marcosdumay »

ipython wrote: post #105
jiggawatts wrote: post #72

Earlier quoted context omitted.

Imagine someone saying, in 2001 that they're adding IPv4 support. Laughable, right? IPv6 was available in Windows 2000. Just saying.

I believe that was only because it was mandated by the federal government as part of procurement process. It’s the same reason there was a half baked posix subsystem in Windows NT. I don’t have citations at the moment to prove my memory.

Windows NT was built VMS-style, getting half-baked subsystems is it's entire point.

Re: More than 1/3 of all access to Google is now over IPv6

#197

Post by Sesse__ »

jeppesen-io wrote: post #178
dijit wrote: post #40

And yet, when I beg my google cloud rep for IPv6 addresses on instances (or on anything that isn’t the load balancer) I get told that it is not on the immediate roadmap. The cloud providers have pushed back ipv6 adoption so hard imo. At least native ipv6 access. I know they’ve thrown in some token support and you /can/ make something work; but compared to VPS providers which consistently deliver machines with IPv6 ad…

> I beg my google cloud rep for IPv6 addresses on instances Why? What problem does this solve?

Ease of management.

Re: More than 1/3 of all access to Google is now over IPv6

#198

Post by jedberg »

walton_simons wrote: post #48

My ISP supports IPv6, and while I can understand why a large organisation would want to use it (especially given the increasing cost and scarcity of IPv4 blocks), I'm still yet to be persuaded of its benefits for home users. I admit that I only have a very cursory understanding of how it works, and perhaps I'm just stuck in my ways, but the scale and complexity seems so extreme compared to IPv4, with no compensating…

Anecdotal, but IPv6 saved me a lot of headache recently.

I got a warning about an unauthorized attempted login to my gmail account. They gave me the IP of the offending login. I was able to track that IP not only back to my house, but to a specific device in my house.

It was my NAS, and it was trying to log into gmail to send me an email about a failing drive. Gmail no longer allows username/password logins from third party apps, so I got a warning instead.

Without IPv6, I would have just chalked it up to a misbehaving device and ignored it since it came from my own IP, but because of IPv6, I was able to see it was from the NAS and investigate further.

Re: More than 1/3 of all access to Google is now over IPv6

#199

Post by [deleted] »

dragonwriter wrote: post #192
orf wrote: post #189

Earlier quoted context omitted.

> It’s not like they’re expensive or hard to get hold of. For context, apparently a block of 79,228,162,514,264,337,593,543,950,336 addresses (/48) is about 100$ a year.

79 octillion addresses ought to be enough for anybody.

[deleted]

Re: More than 1/3 of all access to Google is now over IPv6

#200

Post by alblue »

api wrote: post #186
dijit wrote: post #40

And yet, when I beg my google cloud rep for IPv6 addresses on instances (or on anything that isn’t the load balancer) I get told that it is not on the immediate roadmap. The cloud providers have pushed back ipv6 adoption so hard imo. At least native ipv6 access. I know they’ve thrown in some token support and you /can/ make something work; but compared to VPS providers which consistently deliver machines with IPv6 ad…

AWS supports IPv6 almost everywhere. Azure has some support but requires IPv6 NAT for some mysterious reason. Most of the smaller cloud/VPS providers support it: Digital Ocean, Vultr, Linode, OVH, Packet.net, and so on.

The AWS elastic load balancers don’t support IPv6 targets, and since they are used in almost all circumstances means that AWS’ support for IPv6 is practically irrelevant. Plus, it’s not on their road map to fix.
Post reply on HN