For one, they NAT all IPv6 traffic.
Let that sink in. Let it percolate. Mull over the fact that the entire purpose of IPv6 is to eliminate NAT, and that it's practically impossible to get an IPv6 NAT-ing network device.
Microsoft must have had to write their own, custom network load balancers to NAT IPv6. It's madness.
Oh, if that's not bad enough, they also hand out ludicrously small /124 ranges of just 16 addresses. Sixteen! Not sixteen trillion or some crazy huge number like that, which is what I've got on my home internet. Sixteen. Six and ten.
But no worries, right? Just allocate more blocks! Bzzt... that would run up against the subscription IP limits with just 100 addresses.
Okay, fine, just because my lab environment needed more than a couple of addresses doesn't mean that everybody is so wasteful with the precious IPv6 address pool. Some people can constrain themselves to just a handful of addresses, and don't have a problem with any of the above.
Except that when Azure finally adds proper, native IPv6 support, whatever work their early adopter customers have done will have to be thrown out and redone. Subnets. DNS addresses. Load balancer rules. NAT rules. Security Groups. Everything will have to be revisited.
So why would you bother?
https://docs.microsoft.com/en-us/azure/virtual-network/ipv6-...
This is rather bad considering the importance of ICMPv6 in IPv6 (for Path MTU Discovery, for example).
Their support is being rather useless, despite us having to pay for the privilege of reporting a bug in their own infrastructure to them!
Azure sucks anyway. Their prices are not good and their management console is horrible.
That’s why adoption is slow.
NAT isn’t such a huge problem that the industry thinks it’s urgent enough to push hard to solve.
RFC1918 was forced upon the cloud providers only because there weren't enough IPv4 addresses to go around.
If Amazon had started in 1980, they would have simply allocated a /8 for each region and be done with it. No NAT, no gateways, no address translation of any sort. Everything routing to everything else natively.
For example, Azure Network Security Groups (NSGs) have some glaring omissions that were ignored for years, but have just recently been oh-so-conveniently resolved by Azure Firewall. The old NSGs were free, the firewall costs money, and they also charge per gigabyte of data transferred through it!
Of course, they're recommending that all customers should immediately "uplift" their network architectures to plumb everything through a central firewall.
For security.
You know, income security. For Microsoft.
I should go buy some AMZN and MSFT...
Bucking this trend and building an "Internet-style architecture" is a competitive advantage. You can save multiple orders of magnitude on your hosting and bandwidth costs.
AWS has 24 regions. If each one had a single /8 block -- which would be the bare-minimum at their scale these days -- they would eat up 10% of all available IPv4 addresses!
Keep in mind that they would still have to "carve up" that /8 for each customer, which is still an overly tight fit. Either everyone gets a bunch of small random pools of addresses (eww), or they have to restrict each region to a small number of customers (bad for business), or provide each customer with tiny subnets (too restrictive for the big fish customers).
With IPv6 this just vanishes. They could have multiple address ranges for each Region, AZ, CDN POP, or whatever. They could have ranges for each service, making firewall rules trivial. They could give each customer a huge prefix that they could still carve up into many subnets.
I seriously don't get the arguments against IPv6.
Why are people so happy with their constraints?
So then you ask the engineers, "when are you going to adopt IPv6?" And they're like: "What do you mean? We've never NOT used IPv6 for everything important."
On the one had my GCP server's "native" IP address that the OS sees is always an IPv4 address. On the other hand, it's always in the 10.x.x.x/8 range. Everything else is NAT and LB.
Take a look at kubernetes, which is based on google's Borg. It's only now, slowly getting IPv6 support
I just think that there’s little demand on cloud (and tons of other high prior work)
There would be a lot of demand if IPv6 wasn't an "also ran", a "tack on", some checkbox to tick.
Think about how much network complexity would simply vanish if everything used only public routable IPv6 ranges.
No more split DNS. No more NAT gateways. No need for a separate "public IP" and "private IP". No need to carefully "carve up" the 10.x.x.x range to carefully avoid overlaps... even with future business partners. No need to worry about the "size" of subnets or accidentally running out of addresses in the cramped /24 subnets most people allocate.
It goes on and on.
And on.
But none of that is possible in the public cloud, because it is IPv4 first, and 99% IPv4 by default, and if there's IPv6 support, it's broken, or incomplete, or half-arsed.
(They still could do IPv6 proper - no argument there)
If the default security group for IPv6 only allows SSH and ICMPv6 to an instance/host, what difference does it make?
* https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-secu...
It's not the NATing that gives (internal) networks security, it's the stateful packet inspection at the gateway and--more and more--at the host level.
IPv4 NAT provides security as a side effect.
You don't need NAT for security.
PS: This is the #1 most common argument trotted out against IPv6, and it is blatantly false.
https://www.f5.com/services/resources/white-papers/the-myth-....
Obviously that doesn't make those machines secure, but an insecure machine that hasn't been exploited is better than an insecure machine that has.
Laughable, right?
IPv6 was available in Windows 2000. Just saying.
Over the next few releases, they worked hard on v6 support, and in fact some issues people had with Vista were caused by NT6 being IPv6-first OS, across all of the MS solutions. MŚ had to go backwards a bit in 6.1, introducing things like v6-over-HTTP tunnels because they found that assuming native v6+ipsec working was too much, even with Teredo.
If any vendor had tried to sell a network product in 2001 that didn't do IPv4, they would have been laughed out of the room.
Nobody is laughing in the faces of vendors in 2020 for selling products that can't do IPv6 properly... or at all.
Nobody will be laughing in 2021. Or 2022... or...
I suspect we'll be having this conversation in 2030 as well, and the same people complaining about the side-effects of carrier grade NAT four levels deep will trot out things like "IPv6 doesn't have security because it's not behind a NAT!"
I mainly remember as Vista dropped IPX support, rendering those games unplayable on LAN's for years until someone developed a UDP patch instead
Why? What problem does this solve?
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 addresses by default- it’s a huge barrier to adoption. You have to really /want/ it, and most people don’t see the value. Unless it’s a backend for an iOS App.
It really frustrates me.