4 ms·

Why don’t most VPC providers offer IPv6? Is there some kind of implementation issue with it, or just that you don’t need it.

judge2020 6y ago
When you're using a private network v4 address exhaustion doesn't matter much and the simplicity of only 4 octets helps with IP memorability and simplicity. I would still prefer a v6 option though, as keeping private networks on v4 might be contributing to the slow adoption of v6.
- wmf 6y ago
  Life sure would be easier if "cloud native" meant IPv6-only (except the load balancer) with non-overlapping unique addresses everywhere. 10/8 doesn't go far if you give each VM a /24 and each k8s cluster a /16.
  - ec109685 6y ago
    Where have you experienced shortages? Even with a /16, you are talking about millions of unique IPs.
    - ponyfleisch 6y ago
      A /16 has ~65k unique IPs.
  - llama052 6y ago
    What network are you running where you're giving each virtual machine a /24? That's insane. 10/8 should go very far if you do it correctly, hence why it's in use in almost all internal networks.
    - KaiserPro 6y ago
      kubernetes, because for what ever reasons people are suspicious of using DHCP provided by the VPC.
- api 6y ago
  > When you're using a private network v4 address exhaustion doesn't matter much Until you start trying to connect to enterprise networks... This is seriously ridiculous. It's 2020, and Google and now DO have no IPv6 in their cloud networks.
  - JonathonW 6y ago
    DO has IPv6 on the public side of their network. Couldn't tell you why they've chosen not to use IPv6 for VPC networks, though. Probably just for management simplicity.
    - jrockway 6y ago
      DO sort of has IPv6. Their load balancers don't do IPv6, and you can't use IPv6 in their managed k8s offering. (My guess, honestly, is that nobody asks for it. IPv6 is a problem for Some Other Day.)
      - caymanjim 6y ago
        They also only give you 16 addresses. 16! Most providers give you an entire /64 or sometimes even a /48.
        RaitoBezarius 6y ago
        Wow. In France, home ISP give you a /64 generally (Free for example, known for Online/Scaleway). I think 80 % of their fiber deployments comes with IPv6 enabled now. And in few years, it should be 100 %.
        lloeki 6y ago
        When I was a customer, Free gave you eight (or was it 16?) /64 (as it appeared in the UI[0], I seem to recall they may not all be contiguous), 7 of them you could use for prefix delegation (can't recall why using the first one caused issues, IIRC it was special cased in some way as the "main" one that the Freebox wants to manage). Also it was 6rd, not purely native IPv6. Hopefully they changed that because latency was bad enough the devices would often pick IPv4 through Happy Eyeballs and throughput was a half to a tenth of the v4 path. After that, I had a whole native /56 at Red by SFR. Currently I'm at Sosh by Orange and I have a native /56. [0]: https://lafibre.info/remplacer-freebox/freebox-erl-et-ipv6/?action=dlattach;attach=67928 https://lafibre.info/remplacer-freebox/freebox-erl-et-ipv6/?...

judge2020 6y ago

When you're using a private network v4 address exhaustion doesn't matter much and the simplicity of only 4 octets helps with IP memorability and simplicity. I would still prefer a v6 option though, as keeping private networks on v4 might be contributing to the slow adoption of v6.

wmf 6y ago
Life sure would be easier if "cloud native" meant IPv6-only (except the load balancer) with non-overlapping unique addresses everywhere. 10/8 doesn't go far if you give each VM a /24 and each k8s cluster a /16.
- ec109685 6y ago
  Where have you experienced shortages? Even with a /16, you are talking about millions of unique IPs.
  - ponyfleisch 6y ago
    A /16 has ~65k unique IPs.
- llama052 6y ago
  What network are you running where you're giving each virtual machine a /24? That's insane. 10/8 should go very far if you do it correctly, hence why it's in use in almost all internal networks.
  - KaiserPro 6y ago
    kubernetes, because for what ever reasons people are suspicious of using DHCP provided by the VPC.
api 6y ago
> When you're using a private network v4 address exhaustion doesn't matter much Until you start trying to connect to enterprise networks... This is seriously ridiculous. It's 2020, and Google and now DO have no IPv6 in their cloud networks.
- JonathonW 6y ago
  DO has IPv6 on the public side of their network. Couldn't tell you why they've chosen not to use IPv6 for VPC networks, though. Probably just for management simplicity.
  - jrockway 6y ago
    DO sort of has IPv6. Their load balancers don't do IPv6, and you can't use IPv6 in their managed k8s offering. (My guess, honestly, is that nobody asks for it. IPv6 is a problem for Some Other Day.)
    - caymanjim 6y ago
      They also only give you 16 addresses. 16! Most providers give you an entire /64 or sometimes even a /48.
      - RaitoBezarius 6y ago
        Wow. In France, home ISP give you a /64 generally (Free for example, known for Online/Scaleway). I think 80 % of their fiber deployments comes with IPv6 enabled now. And in few years, it should be 100 %.
        lloeki 6y ago
        When I was a customer, Free gave you eight (or was it 16?) /64 (as it appeared in the UI[0], I seem to recall they may not all be contiguous), 7 of them you could use for prefix delegation (can't recall why using the first one caused issues, IIRC it was special cased in some way as the "main" one that the Freebox wants to manage). Also it was 6rd, not purely native IPv6. Hopefully they changed that because latency was bad enough the devices would often pick IPv4 through Happy Eyeballs and throughput was a half to a tenth of the v4 path. After that, I had a whole native /56 at Red by SFR. Currently I'm at Sosh by Orange and I have a native /56. [0]: https://lafibre.info/remplacer-freebox/freebox-erl-et-ipv6/?action=dlattach;attach=67928 https://lafibre.info/remplacer-freebox/freebox-erl-et-ipv6/?...