3 ms·
The only "problem" here that is caused by IPv6 is the SD-WAN / multi-provider scenario. Even that is solvable. There are so many IPv6 addresses that your local
by jiggawatts 5y ago
The only "problem" here that is caused by IPv6 is the SD-WAN / multi-provider scenario. Even that is solvable. There are so many IPv6 addresses that your local router can have a unique routable range that it can hand out to the local network, "masking" the external internet provider addresses in the same way that IPv4 routing does it. That's not NAT, that's just routing. E.g. I have a customer that uses a non-RFC1918 public range internally and they have 5 ISP uplinks. They don't need to renumber their internal range just to fail over to another link.
ALL of the other issues are caused by vendors selling garbage products that have IPv6 as a "checkbox" tick without real support.
The real problem is that network engineers around the world let them get away with it, because they avoid IPv6 because of this perception that it isn't mature.
The protocol is over two decades old! It's been fully supported since Windows 2000! My phone is IPv6. My fibre LAN is IPv6. It just works.
What doesn't work is this attitude where people just like you continue to pay for products that only pay lip service to the future.
I've gone on rants here before about enormous service providers like AWS and Azure providing IPv6 "support" that is an absolute garbage fire. Totally worthless. Useless beyond belief. Literally counterproductive in the case of Azure, where turning on IPv6 anywhere will break unrelated IPv4 functionality!
Nobody ever chimes in to say: "Yes, we agree, this is bad."
Nobody ever says "Microsoft should fix this!"
Nobody has a problem. So now we have situations like the one you just described, where people are still buying routers in 2021 that that can't handle the most basic IPv6 functionality.
IPv4 addresses are now USD $40 each and rising exponentially. I really do hope the COVID case number graphs taught some of you in a visceral sense what the world "exponential" means. Hint: it doesn't mean that it'll cost $60 in a decade. Try $40000, each.
My ISP uses carrier-grade NAT on IPv4, breaking sites all over the place. I had to call them to enable a dedicated IPv4 address. Their annual investor report says that they will run out within a couple of years. Get one now while you can is the message.
Do you have any idea how much code is required for two PCs to communicate directly now, with up to 4 NAT layers as a common scenario? It's a huge library you have to integrate in your code and then you need a cloud service to assist it.
This is madness, and network engineers around the world are perpetuating it.
- yardstick 5y ago> The only "problem" here that is caused by IPv6 is the SD-WAN / multi-provider scenario. Even that is solvable. There are so many IPv6 addresses that your local router can have a unique routable range that it can hand out to the local network, "masking" the external internet provider addresses in the same way that IPv4 routing does it. That's not NAT, that's just routing. E.g. I have a customer that uses a non-RFC1918 public range internally and they have 5 ISP uplinks. They don't need to renumber their internal range just to fail over to another link. Neither does anyone using IPv4. Does your customer use BGP for that public IPv6 range? Do they have cellular links? Can they load balance some traffic over two/three links? Can they direct certain protocols over different carriers?
- hansel_der 5y agoy u so mad? > Literally counterproductive in the case of Azure, where turning on IPv6 anywhere will break unrelated IPv4 functionality! not just on azure; smartphones seem to be the only environment were v6 is doing its job (lots of smartphones need lots of addresses. ipv6 has a lot of addresses, problem solved) and i guess it's because they are most user-centric client-device imaginable, the actual users don't care at all and most importantly; expect things to occasionally fail.
- jiggawatts 5y agoI'm mad because network "engineers" use that word without realising what it entails to earn that title. The painting has been on the wall for decades. IPv4 exhaustion was predicted to the week. Did anyone do anything about it? No. There are people talking about how Kubernetes is the "future" on this very forum, yet it simply does not work with IPv6. Instead, it uses NAT and RFC1918 ranges... but you've got to be careful not to accidentally overlap those subnets with the rest of your network! I have a customer that screwed this up and now they're facing a rebuild of 3 out of 4 of their clusters. Fun times. I have another customer undergoing mergers, where renumbering their IPv4 RFC1918 ranges is going to cost them on the order of $10M. IPv4 is the legacy, and its costing real money to keep it going decades after its expiry.
- 5y ago