4 ms·

IPv6 "adoption" is happening at roughly the same rate as the move to handheld devices becoming the primary browsing platform. The weekday split you see is peopl

by mike_d 2y ago

IPv6 "adoption" is happening at roughly the same rate as the move to handheld devices becoming the primary browsing platform. The weekday split you see is people being on their work computers during the day and personal tablets/phones on weekends. Very little progress has actually been made to move the bulk of stuff using v4 addresses over to v6. AWS v6 only instances have only been around for 20 months or so?

School-Cotton 2y ago
FWIW the weekday numbers are increasing too, they just lag the weekend ones a bit. I don't know how to quantify "very little progress", but my home ISP (Verizon FiOS in NYC) got IPv6 relatively recently (maybe a year or two ago). Anyway, don't most people connect to WiFi while using their handheld devices at home anyway?
simoncion 2y ago
> AWS v6 only instances have only been around for 20 months or so? a) According to [0], AWS has provided IPv6 addressing to EC2 instances since 2016. > IPv6 support for Amazon Elastic Compute Cloud (Amazon EC2) has been available along with IPv6 support for several other services since 2016. Refer to the 2016 blog post at [1], which says (among other things) > By default, every IPv6 address is public and internet-routable. For customers requiring a private subnet on their IPv6-enabled VPCs, we are introducing a new resource within the VPC called the Egress-only Internet Gateway, which can be setup to allow one-way access to Internet resources. b) I don't get the "This migration only counts if we can support only IPv6 and shut off IPv4" obsession. I see no reason to shut off IPv4 within our lifetimes. I expect the distant future will be providing end-users with a globally-routable IPv6 prefix and a CGNATted-to-hell-and-back IPv4 address for reaching out to those sites that may still be using v4 only. [0] <https://aws.amazon.com/blogs/publicsector/aws-enables-us-federal-governments-move-ipv6/ https://aws.amazon.com/blogs/publicsector/aws-enables-us-fed...> [1] <https://aws.amazon.com/about-aws/whats-new/2016/12/announcing-internet-protocol-version-6-support-for-ec2-instances-in-amazon-virtual-private-cloud/ https://aws.amazon.com/about-aws/whats-new/2016/12/announcin...>
- mike_d 2y ago
  > a) According to [0], AWS has provided IPv6 addressing to EC2 instances since 2016. Yes, but that isn't what we are talking about. 2022 is when they added native IPv6 support, prior to that it was just a fancy NAT like translation.
  - simoncion 2y ago
    > 2022 is when they added native IPv6 support, prior to that it was just a fancy NAT like translation. Are you sure about that? The relevant docs from 2019 (the Wayback Machine doesn't have anything earlier) sure make it seem like you're getting globally-reachable IPv6 addresses: From [0]: > To complete this exercise, do the following: ... > * Launch an Amazon EC2 instance into your subnet, and associate an IPv6 address with your instance during launch. An IPv6 address is globally unique, and allows your instance to communicate with the Internet. Yes, the last bit of that doesn't automatically mean that your instance is globally-reachable. Read on. From [1]: > IPv6 addresses are globally unique, and therefore reachable over the Internet. You can control whether instances are reachable via their IPv6 addresses by controlling the routing for your subnet, or by using security group and network ACL rules. For more information, see Security. From the "Inbound" table of the "Recommended Rules for Scenario 1" section of [2]: > | 170 | IPv6 address range of your home network | TCP | 22 | ALLOW | Allows inbound SSH traffic from your home network (over the Internet gateway). | Am I missing some part of the docs where they talk about how there was some fancy NAT-like translation box that made it so that these weren't globally-reachable IP addresses? Was AWS just lying in their docs? [0] <https://web.archive.org/web/20190131164146/https://docs.aws.amazon.com/vpc/latest/userguide/get-started-ipv6.html https://web.archive.org/web/20190131164146/https://docs.aws....> [1] <https://web.archive.org/web/20190801182729/https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html https://web.archive.org/web/20190801182729/https://docs.aws....> [2] <https://web.archive.org/web/20191021190354/https://docs.aws.amazon.com/vpc/latest/userguide/vpc-recommended-nacl-rules.html https://web.archive.org/web/20191021190354/https://docs.aws....>
    - mike_d 2y ago
      You seem to be confusing being able to reach IPv6 with native IPv6. With rare exceptions AWS does not document how their internal network functions because it is a trade secret. However for the longest time it was fairly easy to test: if you removed the IPv4 address from an instance it was no longer reachable via IPv6. AWS was never built with IPv6 in mind and it is mostly glued on. As of right now 88% of AWS services are IPv4 only: https://awsipv6.neveragain.de/ https://awsipv6.neveragain.de/ (uncheck the Hide IPv4 only box)

by mike_d 2y ago

School-Cotton 2y ago

FWIW the weekday numbers are increasing too, they just lag the weekend ones a bit. I don't know how to quantify "very little progress", but my home ISP (Verizon FiOS in NYC) got IPv6 relatively recently (maybe a year or two ago). Anyway, don't most people connect to WiFi while using their handheld devices at home anyway?

simoncion 2y ago

> AWS v6 only instances have only been around for 20 months or so? a) According to [0], AWS has provided IPv6 addressing to EC2 instances since 2016. > IPv6 support for Amazon Elastic Compute Cloud (Amazon EC2) has been available along with IPv6 support for several other services since 2016. Refer to the 2016 blog post at [1], which says (among other things) > By default, every IPv6 address is public and internet-routable. For customers requiring a private subnet on their IPv6-enabled VPCs, we are introducing a new resource within the VPC called the Egress-only Internet Gateway, which can be setup to allow one-way access to Internet resources. b) I don't get the "This migration only counts if we can support only IPv6 and shut off IPv4" obsession. I see no reason to shut off IPv4 within our lifetimes. I expect the distant future will be providing end-users with a globally-routable IPv6 prefix and a CGNATted-to-hell-and-back IPv4 address for reaching out to those sites that may still be using v4 only. [0] <https://aws.amazon.com/blogs/publicsector/aws-enables-us-federal-governments-move-ipv6/ https://aws.amazon.com/blogs/publicsector/aws-enables-us-fed...> [1] <https://aws.amazon.com/about-aws/whats-new/2016/12/announcing-internet-protocol-version-6-support-for-ec2-instances-in-amazon-virtual-private-cloud/ https://aws.amazon.com/about-aws/whats-new/2016/12/announcin...>

mike_d 2y ago
> a) According to [0], AWS has provided IPv6 addressing to EC2 instances since 2016. Yes, but that isn't what we are talking about. 2022 is when they added native IPv6 support, prior to that it was just a fancy NAT like translation.
- simoncion 2y ago
  > 2022 is when they added native IPv6 support, prior to that it was just a fancy NAT like translation. Are you sure about that? The relevant docs from 2019 (the Wayback Machine doesn't have anything earlier) sure make it seem like you're getting globally-reachable IPv6 addresses: From [0]: > To complete this exercise, do the following: ... > * Launch an Amazon EC2 instance into your subnet, and associate an IPv6 address with your instance during launch. An IPv6 address is globally unique, and allows your instance to communicate with the Internet. Yes, the last bit of that doesn't automatically mean that your instance is globally-reachable. Read on. From [1]: > IPv6 addresses are globally unique, and therefore reachable over the Internet. You can control whether instances are reachable via their IPv6 addresses by controlling the routing for your subnet, or by using security group and network ACL rules. For more information, see Security. From the "Inbound" table of the "Recommended Rules for Scenario 1" section of [2]: > | 170 | IPv6 address range of your home network | TCP | 22 | ALLOW | Allows inbound SSH traffic from your home network (over the Internet gateway). | Am I missing some part of the docs where they talk about how there was some fancy NAT-like translation box that made it so that these weren't globally-reachable IP addresses? Was AWS just lying in their docs? [0] <https://web.archive.org/web/20190131164146/https://docs.aws.amazon.com/vpc/latest/userguide/get-started-ipv6.html https://web.archive.org/web/20190131164146/https://docs.aws....> [1] <https://web.archive.org/web/20190801182729/https://docs.aws.amazon.com/vpc/latest/userguide/vpc-ip-addressing.html https://web.archive.org/web/20190801182729/https://docs.aws....> [2] <https://web.archive.org/web/20191021190354/https://docs.aws.amazon.com/vpc/latest/userguide/vpc-recommended-nacl-rules.html https://web.archive.org/web/20191021190354/https://docs.aws....>
  - mike_d 2y ago
    You seem to be confusing being able to reach IPv6 with native IPv6. With rare exceptions AWS does not document how their internal network functions because it is a trade secret. However for the longest time it was fairly easy to test: if you removed the IPv4 address from an instance it was no longer reachable via IPv6. AWS was never built with IPv6 in mind and it is mostly glued on. As of right now 88% of AWS services are IPv4 only: https://awsipv6.neveragain.de/ https://awsipv6.neveragain.de/ (uncheck the Hide IPv4 only box)