3 ms·
Azure's IPv6 "support" saddens me. It's just painful how minimal their support is. For one, they NAT all IPv6 traffic. Let that sink in. Let it percolate. Mul
by jiggawatts 6y ago
Azure's IPv6 "support" saddens me. It's just painful how minimal their support is.
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-public-ip-address-prefix#ipv6-prefix-sizes https://docs.microsoft.com/en-us/azure/virtual-network/ipv6-...
- grahamedgecombe 6y agoWe've been experimenting with Azure's IPv6 support at work recently. The fact it uses NAT is insane - though we could tolerate that. Even worse is that the NAT is broken - it doesn't update the ICMPv6 checksum when it rewrites the source/destination address, so the machines on both ends drop all ICMPv6 traffic that passes through Azure. 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!
- jiggawatts 6y agoPath MTU Discovery is broken in Azure's IPv4 stack as well, which is even more sad. Similarly to you, I had to report to them that their VPN tunnels only send PMTUD in one direction, so you get this wonderful experience where TCP streams with big packets work in one direction, but not the other! With most ACK packets being small, this can take a surprising amount of time to discover and troubleshoot.
- api 6y agoMicrosoft sells to a lot of crusty enterprises, and I bet a lot of the IT folks there think NAT is for security and refused to use IPv6 if it wasn't NATed. They probably deployed it that way to placate that particular piece of brain dead security cargo cultism. Azure sucks anyway. Their prices are not good and their management console is horrible.
- thehappypm 6y agoYou’re right that eliminating NAT is a huge part of IPV6, possibly it’s largest value-add. 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.
- fulafel 6y agoWow. That's terrible.