6 ms·

Anyone know what's the biggest hold up of IPv6 on AWS side? They must be working on this for years, but never heard of any push or beta program at all.

by yeukhon 11y ago

ra1n85 11y ago
What cloud provider currently supports IPv6?
- deleted 11y ago
  [deleted]
- toast0 11y ago
  SoftLayer offers v6
- mindcrime 11y ago
  Linode supports IPv6: [prhodes@doctorfeelgood ~]$ ping6 -n www.fogbeam.com PING www.fogbeam.com(2600:3c02::f03c:91ff:fe84:7b1d) 56 data bytes 64 bytes from 2600:3c02::f03c:91ff:fe84:7b1d: icmp_seq=1 ttl=55 time=31.7 ms 64 bytes from 2600:3c02::f03c:91ff:fe84:7b1d: icmp_seq=2 ttl=55 time=39.8 ms 64 bytes from 2600:3c02::f03c:91ff:fe84:7b1d: icmp_seq=3 ttl=55 time=38.6 ms ^C
  - ra1n85 11y ago
    Thanks! Just looking at this makes me feel for network operators that have to troubleshoot layer 3 addresses directly and without DNS. There needs to be a better approach - like an intelligent clipboard.
    - mindcrime 11y ago
      I'm far from an expert on ipv6, but I think there may be some "shortcuts" that let you work with less than the full address. See, for example: http://networkrecipes.blogspot.com/2014/08/ipv6-shortcuts.html http://networkrecipes.blogspot.com/2014/08/ipv6-shortcuts.ht...
- icebraining 11y ago
  Both VPS providers I use - DigitalOcean and TransIP - support IPv6, though only the latter does so by default.
justizin 11y ago
.. or they haven't .. VPC gives you your own entire rfc1918 space per region, which tho can be a pain to deal with overlap if you have site-to-site VPN, is enough for basically anyone.
- yeukhon 11y ago
  Well, public services are not. ELB for example. If AWS continues to grow, I think they will eventually exhaust their IPv4 blocks and this is an issue they can't ignore.
  - barlo 11y ago
    ELBs in EC2 Classic support IPv6, but not ELBs in VPCs, as of now at least. You may already have known this but I figured I'd point it out for others: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-internet-facing-load-balancers.html http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel...
    - yeukhon 11y ago
      I wasn't even aware of IPv6 support for Classic. Thanks.
- NetStrikeForce 11y ago
  You can avoid RFC1918 overlapping issues by using some overlay networking solution like Wormhole[1], which uses the CGNAT reserved IP space to build a virtual network between your servers, regardless of their location. This pain point is one of the reasons we've built Wormhole. [1]https://wormhole.network https://wormhole.network
jo909 11y ago
My guess is that their custom software defined networking infrastructure is the main holdup. There is little known about the SDN infrastructure behind AWS, but I would be surprised if large portions are not custom designed hardware and a homebrew control plane. It is very slow to iterate on the hardware side at such a scale for cost reasons. The cost structure is very different from server hardware, where the increase in performance per watt and rack density of newer hardware essentially pays for itself at some point. But a 10Gbps Port in your top of rack switch is good enough for many many years and multiple server generations, until you make the leap to a higher port speed. If the chip inside your SDN switch has no understanding of IPv6, you could only tunnel such packets in software at substantial performance costs. So it takes ages until the whole physical network is using new enough gear.
bluedonuts 11y ago
AWS does support ipv6 in ELBs in a fashion. ELBs will have both an ipv6 and a dual stack DNS entry created for them, in addition to the ipv4. example.us-east-1.elb.amazonaws.com (A Record) ipv6.example.us-east-1.elb.amazonaws.com (AAAA Record) dualstack.example.us-east-1.elb.amazonaws.com (A or AAAA Record) These records will only be displayed for ELBs in classic despite existing and being resolvable for VPC ELBs. The twist is that there is no way to add security groups with ipv6 addresses in VPC so its not possible to receive requests. Amusingly this means ELBs in classic have an advantage on VPC when it comes to ipv6.
- yeukhon 11y ago
  Thanks did not ipv6 version exists. Now you are bringing the right thing... IPv6 support in VPC SG.

Anyone know what's the biggest hold up of IPv6 on AWS side? They must be working on this for years, but never heard of any push or beta program at all.

by yeukhon 11y ago

Anyone know what's the biggest hold up of IPv6 on AWS side? They must be working on this for years, but never heard of any push or beta program at all.

ra1n85 11y ago

What cloud provider currently supports IPv6?

deleted 11y ago
[deleted]
toast0 11y ago
SoftLayer offers v6
mindcrime 11y ago
Linode supports IPv6: [prhodes@doctorfeelgood ~]$ ping6 -n www.fogbeam.com PING www.fogbeam.com(2600:3c02::f03c:91ff:fe84:7b1d) 56 data bytes 64 bytes from 2600:3c02::f03c:91ff:fe84:7b1d: icmp_seq=1 ttl=55 time=31.7 ms 64 bytes from 2600:3c02::f03c:91ff:fe84:7b1d: icmp_seq=2 ttl=55 time=39.8 ms 64 bytes from 2600:3c02::f03c:91ff:fe84:7b1d: icmp_seq=3 ttl=55 time=38.6 ms ^C
- ra1n85 11y ago
  Thanks! Just looking at this makes me feel for network operators that have to troubleshoot layer 3 addresses directly and without DNS. There needs to be a better approach - like an intelligent clipboard.
  - mindcrime 11y ago
    I'm far from an expert on ipv6, but I think there may be some "shortcuts" that let you work with less than the full address. See, for example: http://networkrecipes.blogspot.com/2014/08/ipv6-shortcuts.html http://networkrecipes.blogspot.com/2014/08/ipv6-shortcuts.ht...
icebraining 11y ago
Both VPS providers I use - DigitalOcean and TransIP - support IPv6, though only the latter does so by default.

justizin 11y ago

.. or they haven't .. VPC gives you your own entire rfc1918 space per region, which tho can be a pain to deal with overlap if you have site-to-site VPN, is enough for basically anyone.

yeukhon 11y ago
Well, public services are not. ELB for example. If AWS continues to grow, I think they will eventually exhaust their IPv4 blocks and this is an issue they can't ignore.
- barlo 11y ago
  ELBs in EC2 Classic support IPv6, but not ELBs in VPCs, as of now at least. You may already have known this but I figured I'd point it out for others: http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/elb-internet-facing-load-balancers.html http://docs.aws.amazon.com/ElasticLoadBalancing/latest/Devel...
  - yeukhon 11y ago
    I wasn't even aware of IPv6 support for Classic. Thanks.
NetStrikeForce 11y ago
You can avoid RFC1918 overlapping issues by using some overlay networking solution like Wormhole[1], which uses the CGNAT reserved IP space to build a virtual network between your servers, regardless of their location. This pain point is one of the reasons we've built Wormhole. [1]https://wormhole.network https://wormhole.network

jo909 11y ago

My guess is that their custom software defined networking infrastructure is the main holdup. There is little known about the SDN infrastructure behind AWS, but I would be surprised if large portions are not custom designed hardware and a homebrew control plane. It is very slow to iterate on the hardware side at such a scale for cost reasons. The cost structure is very different from server hardware, where the increase in performance per watt and rack density of newer hardware essentially pays for itself at some point. But a 10Gbps Port in your top of rack switch is good enough for many many years and multiple server generations, until you make the leap to a higher port speed. If the chip inside your SDN switch has no understanding of IPv6, you could only tunnel such packets in software at substantial performance costs. So it takes ages until the whole physical network is using new enough gear.

bluedonuts 11y ago

AWS does support ipv6 in ELBs in a fashion. ELBs will have both an ipv6 and a dual stack DNS entry created for them, in addition to the ipv4. example.us-east-1.elb.amazonaws.com (A Record) ipv6.example.us-east-1.elb.amazonaws.com (AAAA Record) dualstack.example.us-east-1.elb.amazonaws.com (A or AAAA Record) These records will only be displayed for ELBs in classic despite existing and being resolvable for VPC ELBs. The twist is that there is no way to add security groups with ipv6 addresses in VPC so its not possible to receive requests. Amusingly this means ELBs in classic have an advantage on VPC when it comes to ipv6.

yeukhon 11y ago
Thanks did not ipv6 version exists. Now you are bringing the right thing... IPv6 support in VPC SG.