6 ms·

What do you think are the biggest flaws in IPv6?

exabrial 5y ago
I've been advocating for this for a long long time. Just NAT to IPv6 or IPv4 and go about your business.
feldrim 5y ago
I believe that the comment is not a personal opinion but a reflection of the acceptance rate of IPv6. If most of the web still uses IPv4 and not using IPv6 is still defended with the "people against new things" arguments, it shows that there is at least one thing that prevents people from using it. Considering that the new kid on the block is 26 years old, I think, there is more than one.
- lostapathy 5y ago
  Any new protocol is going to have adoption costs. The "issue" with ipv6 is that for a lot of people/organizations, the tolerable cost of adoption is still pretty much zero. Adding yet another protocol to the mix would not make that better.
  - emptybottle 5y ago
    You are right, v6 is mostly a new protocol. But it's been been advertised as an updated version. It just contains essentially 100% breaking changes.
  - feldrim 5y ago
    By no means I did support the use of another protocol. All I focused on was that the IPv6 could not be a huge success over IPv4. For the previous 26 years, pros weren't enough to eliminate the cons. At least the overall usage ratio can be comprehended this way.
iso1631 5y ago
Dual Stack. Means twice the work for barely any benefit. I should be able to have a router with a ipv4 network and multiple ipv6 networks without losing access to the ip4 network. The ip6 network should be reachable via port natting on the ip4 IP I.E I have three networks on my router, two on ipv6 1000:2000:3000:4001::1/64 1000:2000:3000:4002::1/64 192.168.0.1/24 the ipv6 only server on 1000:2000:3000:4001::10 should cope with sending a packet to 1000:2000:3000:4002::10 By routing it via the router It should also transparently convert a target of 192.168.0.3 to ::ffff:c0a8:3 and send via the gateay. The router should then convert it to 192.168.0.3, with a source of 192.168.0.1, and maintaining a NAT state so return traffic goes back to 1000:2000:3000:4001::10 If there's a service that 1000:2000:3000:4001::10 needs to expose, the router can do a dst-nat on say 192.168.0.1 port 80 and forward to 1000:2000:3000:4001::10 port 80 That way you can comfortably deploy ipv6 wherever possible and not have to worry about ipv4 other than at the router, where you just have the ipv4 subnet Likewise my ipv6 network can reach 209.216.230.240 by running ipv6 across my network until it comes to a device with an ipv4 address, where it gets natted. Just like it runs across my private rfc19xx ipv4 range before srcnatting at the edge of my network.
- jcalvinowens 5y ago
  Poor interoperability with NAT is a feature, not a bug, IMHO. NAT rarely makes sense in IPv6. In your scenario, why wouldn't you just set up your router so you can directly address the V6 subnets over V6 to begin with? IPv6 works best when all addresses are globally routable (whether firewalled off or not). We're all so used to RFC1918 that we forget it was an ugly kludge that fundamentally broke how the internet was meant to work. IPv6 is the fix for that breakage: the address of every individual device can actually mean the same thing everywhere on the internet, as it was meant to be. L3 routing can be stateless again. The primary intent of IPv6 is to replace IPv4, not coexist with it. Coexistence is transitory and not worth optimizing for over the future of the internet when V4 is dead.
  - iso1631 5y ago
    V6-V6 sure, that doesn't need nat. It's the V6->V4. NAT is preferably to dual stack. I don't want to double my administration efforts by maintaining a v4 and a v6 network on every machine and every router, which appears to be best practice. Let me deploy v6, and only v6, but still interoperate with v4 until everyone has migrated. As for nat being a cludge, lets assume I have a simple small office network with two independent ISPs. Normally I want to send half my users out of ISP1 and half out of ISP2. If ISP2 fails, I want to send them all out of ISP1, OK there's less bandwidth to go round, but better than having no bandwidth for half my users. How do I do that with ipv6 without natting (assuming I'm not large enough to be running my own AS and peering with two different providers)
zeroimpl 5y ago
I tried turning on IPv6 on my VPS server running Docker. Not knowing much about IPv6, I naively assumed it’d just work. Evidently not, and you either need to run a NAT service or your containers become publicly routable, both having major caveats that I didn’t want to deal with. The notion that every endpoint has a globally unique address, with prefixes coming down from some upstream provider is just fundamentally incompatible with how IPv4 networks are designed today.

I've been advocating for this for a long long time. Just NAT to IPv6 or IPv4 and go about your business.

I believe that the comment is not a personal opinion but a reflection of the acceptance rate of IPv6. If most of the web still uses IPv4 and not using IPv6 is still defended with the "people against new things" arguments, it shows that there is at least one thing that prevents people from using it. Considering that the new kid on the block is 26 years old, I think, there is more than one.

lostapathy 5y ago
Any new protocol is going to have adoption costs. The "issue" with ipv6 is that for a lot of people/organizations, the tolerable cost of adoption is still pretty much zero. Adding yet another protocol to the mix would not make that better.
- emptybottle 5y ago
  You are right, v6 is mostly a new protocol. But it's been been advertised as an updated version. It just contains essentially 100% breaking changes.
- feldrim 5y ago
  By no means I did support the use of another protocol. All I focused on was that the IPv6 could not be a huge success over IPv4. For the previous 26 years, pros weren't enough to eliminate the cons. At least the overall usage ratio can be comprehended this way.

iso1631 5y ago

Dual Stack. Means twice the work for barely any benefit. I should be able to have a router with a ipv4 network and multiple ipv6 networks without losing access to the ip4 network. The ip6 network should be reachable via port natting on the ip4 IP I.E I have three networks on my router, two on ipv6 1000:2000:3000:4001::1/64 1000:2000:3000:4002::1/64 192.168.0.1/24 the ipv6 only server on 1000:2000:3000:4001::10 should cope with sending a packet to 1000:2000:3000:4002::10 By routing it via the router It should also transparently convert a target of 192.168.0.3 to ::ffff:c0a8:3 and send via the gateay. The router should then convert it to 192.168.0.3, with a source of 192.168.0.1, and maintaining a NAT state so return traffic goes back to 1000:2000:3000:4001::10 If there's a service that 1000:2000:3000:4001::10 needs to expose, the router can do a dst-nat on say 192.168.0.1 port 80 and forward to 1000:2000:3000:4001::10 port 80 That way you can comfortably deploy ipv6 wherever possible and not have to worry about ipv4 other than at the router, where you just have the ipv4 subnet Likewise my ipv6 network can reach 209.216.230.240 by running ipv6 across my network until it comes to a device with an ipv4 address, where it gets natted. Just like it runs across my private rfc19xx ipv4 range before srcnatting at the edge of my network.

jcalvinowens 5y ago
Poor interoperability with NAT is a feature, not a bug, IMHO. NAT rarely makes sense in IPv6. In your scenario, why wouldn't you just set up your router so you can directly address the V6 subnets over V6 to begin with? IPv6 works best when all addresses are globally routable (whether firewalled off or not). We're all so used to RFC1918 that we forget it was an ugly kludge that fundamentally broke how the internet was meant to work. IPv6 is the fix for that breakage: the address of every individual device can actually mean the same thing everywhere on the internet, as it was meant to be. L3 routing can be stateless again. The primary intent of IPv6 is to replace IPv4, not coexist with it. Coexistence is transitory and not worth optimizing for over the future of the internet when V4 is dead.
- iso1631 5y ago
  V6-V6 sure, that doesn't need nat. It's the V6->V4. NAT is preferably to dual stack. I don't want to double my administration efforts by maintaining a v4 and a v6 network on every machine and every router, which appears to be best practice. Let me deploy v6, and only v6, but still interoperate with v4 until everyone has migrated. As for nat being a cludge, lets assume I have a simple small office network with two independent ISPs. Normally I want to send half my users out of ISP1 and half out of ISP2. If ISP2 fails, I want to send them all out of ISP1, OK there's less bandwidth to go round, but better than having no bandwidth for half my users. How do I do that with ipv6 without natting (assuming I'm not large enough to be running my own AS and peering with two different providers)

zeroimpl 5y ago

I tried turning on IPv6 on my VPS server running Docker. Not knowing much about IPv6, I naively assumed it’d just work. Evidently not, and you either need to run a NAT service or your containers become publicly routable, both having major caveats that I didn’t want to deal with. The notion that every endpoint has a globally unique address, with prefixes coming down from some upstream provider is just fundamentally incompatible with how IPv4 networks are designed today.