13 ms·
AWS to start charging for IPv4 usage, but critical services don't support IPv6
- bell-cot 3y ago"A price hike by any other name costs just as much." (I didn't bother looking for the quote's source.)
- cassianoleal 3y agoIt's James T. Kirk's. I think.
- thowaway91234 3y agoAbraham Lincoln, I'm pretty sure.
- ryandvm 3y agoIPv6 and Python3 are case studies in how not to roll out a new version unless you're cool with multi-decade upgrade windows.
- paulgb 3y agoIs there an alternative, though? Both Python3 and IPv6 both solve problems that would have been at least as painful to do incrementally, IMHO.
- danpalmer 3y agoAgreed, while I recognise that both look bad, I'm skeptical as to how bad they actually are. Some comparisons against good examples of these sorts of transitions would be good.
- JoshTriplett 3y agoIPv6 provided some features people needed (larger addresses), made some changes born from experience (removing IP-level header checksums in favor of packet checksums like those in UDP and TCP, removing fragmentation), and then bundled in a pile of mandatory added complexity (DAD, SLAAC and router advertisements rather than DHCP, initially mandatory IPsec). If IPv6 had left out the mandatory added complexity, and just focused on the larger addresses and cleanups, it would have been easier to adopt. The other changes could have happened via other standards, rather than bundling them all into "IPv6".
- throw0101b 3y ago> […] and then bundled in a pile of mandatory added complexity (DAD, SLAAC and router advertisements rather than DHCP, initially mandatory IPsec). SLAAC and RA reduce complexity as you no longer need 'extra' infrastructure (DHCP) to get going: plug in and the router sends the information and you're done. You also get rid of the complexity of STUN/ICE/etc as you no longer need NAT, so you just need hole punching for SPI firewall (also needed with NAT for port forwarding, so no change there).
- marcinzm 3y agoExcept you still need all that complexity as you need to support IPv4 as well.
- betaby 3y agoThere is NAT64 for that https://en.wikipedia.org/wiki/NAT64 https://en.wikipedia.org/wiki/NAT64 Many mobile operators use that, in USA that is Sprint/T-mobile, Bell in Canada. All modern OSes support that pretty well.
- rescbr 3y agoOnce you add up the real world factor of half-assed implementations and bad business/tech decisions, you end up with DHCP and NAT (or its IPv6 cousin, NPT) to solve issues.
- JoshTriplett 3y ago> plug in and the router sends the information and you're done. If you want the network to come up in a timely fashion, the new system needs to poke the network to get information proactively sent to it as soon as possible, at which point you have about the same level of complexity as poking a DHCP server. (With added bonus "this could happen asynchronously at any time and you never reliably know when your network is actually done being configured".) If those standards are so valuable, they should have stood on their own, as optional things people could have adopted if they wanted to do things completely differently from IPv4. Meanwhile, people already have DHCP servers, and could have just told those DHCP servers to start giving out IPv6 addresses too. The reaction I have every time I interact with IPv6 is that it seems incredibly hard to make a system just use the configuration you tell it to use and never ever listen to any configuration from the network.
- gray_-_wolf 3y agoI think that if IPv6 would just be IPv4 with bigger addresses, the rollout would be much easier. Sure, you would still need new hardware, but the basic operations would still be the same as IPv4. Currently, it is far from that.
- oarsinsync 3y agoAre there recommendations that result in IPv6 looking like something more than just IPv4 with bigger addresses? Yes. Is there anything stopping you from effectively running IPv6 networks the same way as you run IPv4 networks, but with larger address pools? No. You can do NAT66, you can do DHCPv6, you can run every network as a /120 (IPv6 equivalent of a /24 - 256 addresses) if you want to as well. You can even (outside of whatever prefix is delegated to you) only use numbers for the host addressing portion if you want to, and not bother with letters. Just because the recommendations and standards say you SHOULD do things a particular way, it doesn’t mean you MUST.
- gray_-_wolf 3y agoSure, I don't have to, but everything in the stack assumes I would run it in the recommended way. I gave up trying to setup my LAN to support IPv6 after I wasted more than 2 hours on convincing my router, and devices behind it, to somehow work with the /128 address I got from my ISP. Should it be technically possible? Yes, definitely. Is there any value for me in spending a lot of time on it? No, there is not, everything is reachable on IPv4 anyway. This would not be a problem if it would be just bigger IPv4 and there still was NAT, DHCP and everything. But that is not the way you are expected to be doing IPv6...
- oarsinsync 3y ago> Sure, I don't have to, but everything in the stack assumes I would run it in the recommended way. > This would not be a problem if it would be just bigger IPv4 and there still was NAT, DHCP and everything. Irony, I remember life before DHCP/NAT44 defaults, and having to struggle so much to do it myself. Mind, this was 1997, and IPv6 was already a defined standard, which then never got any traction because NAT44 ended up being “good enough” for most people who didn’t think about what they lost in the process. > Should it be technically possible? Yes, definitely. Is there any value for me in spending a lot of time on it? There was a lot of value in me spending a lot of time and effort on setting up DHCP and NAT in my home environment in the 90s. Nobody else I knew thought it was worthwhile though, and thought I was insane. There was a lot of value in me spending a lot of time and effort on dual stacking my LAN too. I see a parallel here that’s amusing to me :-)
- throw0101b 3y ago> Is there an alternative, though? Certainly some people didn't like the changes of ND vs ARP and such, but once you're changing the address length, you have to alter the data structure on every bit of networking code, and any transition is going to be a slog. IPv4 data structures have four bytes/octets (4B) for addresses. So how do you fit 8B of addresses in 4B structures? You don't. So you have to update every network element—host (desktop, laptop, mobile, embedded), router, switch, firewall—to have a new data structure (and maybe new function/system calls, as the old ones assume the old structures). So all devices have to have updated network stacks, including long-lived ones that sometimes are not touched for a decade+. And not just pure networking code: anything that touches (e.g.) DNS as well, as A records are 4B-only as well, so you need a new record type and deploy new DNS server and resolver code everywhere. But of course if you have a 4B-only network elements/devices, they cannot talk to 8B-only devices/services, so you have to create translation mechanisms because some devices may not yet have the update 8B-capable network stack. And sometimes an 8B network is an island in a sea of 4B, so you have to have tunneling. Of course some may have both 4B and 8B, and want to talk to something has also has 4B and 8B, so now you have to have code for source/destination selection. And of course as long as IPv4 works there's little inherent motivation to go to any kind of IPng. See "TCP and UDP with Bigger Addresses (TUBA), A Simple Proposal for Internet Addressing and Routing" for part of the discussion from back in the day (1993): * https://datatracker.ietf.org/doc/html/rfc1347 https://datatracker.ietf.org/doc/html/rfc1347
- oneshtein 3y agoIn practice, port number is used as part of address, or, VPN, with tagging, are used. We can make convention that top 4 bits of port number are part of the host address. It will increase number of available addresses by up to 16x. For example, we have router at 1.2.3.4/192.168.0.254, and 15 hosts behind it, then, by convention, we can access 192.168.0.1 from public internet as 1.2.3.4:32848 (port 32767+1+80), host 192.168.0.3 as 1.2.3.4:32849, and so on.
- devit 3y agoA much simpler and compatible solution would be to assign a single IPv4 address per AS and then use IP options to pass additional address bits to identify the specific host within the AS.
- Dagger2 3y agoThat wouldn't be simple or compatible, but also... v6 basically already has what you're suggesting here, except forget every AS: every single v4 address already has a /48 of v6 space tunnelled to it.
- candiddevmike 3y agoThey're more a case study on institutional inertia and not providing a good justification for businesses to upgrade. Gotta sell the benefits. I think cloud providers charging for IPv4 is a great stick, since the initial carrots (easier subnetting, huge networks, multiple IPs per host, encryption, etc) didn't work. I do wish they provided NAT64 services though.
- deleted 3y ago[deleted]
- noirscape 3y agoAt least with Python3, there was eventually Python 2.7 to permit a compatibility layer to move over. It took ages, but there was at least a "best effort" to help people write code that could be easily moved between 2 and 3. (In spite of apparent behavior from the Python developers at the time). IPv6's hard break with IPv4 means that the switchover likely won't happen anytime soon.
- cesarb 3y ago> At least with Python3, there was eventually Python 2.7 to permit a compatibility layer to move over. [...] IPv6's hard break with IPv4 means that the switchover likely won't happen anytime soon. There was no hard break. The same way you have compatibility layers between Python 3.x and Python 2.7, we have compatibility layers between IPv4 and IPv6. For instance, 6to4 meant that anyone with an IPv4 address automatically had an IPv6 network, and could talk to IPv6 hosts; I used it for a while, and it worked nicely. Another one was Teredo, which worked even if your IPv4 host was behind an IPv4 NAT. Nowadays, the preference is for newer transition mechanisms, like NAT64/DNS64 and 464XLAT. On the software side, IPv4-mapped IPv6 addresses allow software written for IPv6 to transparently use the host's IPv4 stack to connect to an IPv4 address; this last one is very similar to the preferred approach of writing Python 3 code and using a compatibility layer to make it run on Python 2.7.
- hot_gril 3y agoIMO they should've just conceded and added a `print` syntax to Py3 similar to Py2. Stupid as it sounds, that was often the only reason someone's script was Py2-only. That and the integer division should've stayed the same.
- ciguy 3y agoAnyone that is surprised by this behavior from AWS probably has very little experience using it. The whole console is full of dark pattens to get you to setup larger than needed defaults and accidentally leave things running.
- hotpotamus 3y agoI'm always surprised that people think they're getting a good deal from a guy who spent a billion dollars to launch a dick into space. The days of the door desk are long gone.
- seanhunter 3y agoDo the other cloud providers give you IPv4 endpoints for free? I didn't think that was the case. (ie I thought AWS was just falling into line with the others on charging). As for the "critical services not supporting IPv6" in the post I was quite surprised that it's such a short list of things that don't work - I would have expected more. They've obviously made a ton of progress.
- tebbers 3y agoDigitalOcean do.
- charcircuit 3y agoAzure and Google Cloud don't, and they didn't have full ipv6 support when making the change either
- apparentorder 3y agoBut did they tell you to "think about accelerating your adoption of IPv6 as a modernization and conservation measure" when they announced the charges? Because AWS did.
- Uehreka 3y ago> Examples include: I get the feeling this is far from an exhaustive list. I think this person just mentioned two things that they had run into and could say didn’t support IPv6 without having to look it up.
- wongarsu 3y agoHetzner is charging 0.50€/month, compared to AWS's $3.60/month. Which I guess is in line with the usual price difference between the two, but usually AWS does a better job justifying the price difference.
- throw555chip 3y agoOracle Cloud does. Linode did, I don't know if they still do. I believe Vultr may. It would take some time for someone to research all cloud providers.
- Hamuko 3y agoGlobal IPv6 adaptation is currently at around 40%, so maybe don't unassociate that IPv4 address from your load balancer just yet. https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- luhn 3y agoALB doesn't support IPv6-only, so I couldn't even if I wanted to.
- milesward 3y agoIt's called a price increase folks, don't overthink it.
- londons_explore 3y agoIp addresses have an actual market value now. They cost 50 cents a month to lease. AWS is charging $3.60 per month. Which isn't orders of magnitude off when you consider AWS probably has a poor utilization rate (can only advertise /24's) and profit margins to consider.
- Sebguer 3y agoIP addresses were intended to be a public good. The fact that AWS has monopolized so many of them, and now that they own a significant fraction of them is deciding to charge for them. It's ridiculous.
- ThunderSizzle 3y agoThen don't use AWS and discourage others from using AWS. I guess that might also include all Amazon businesses if you really want to try to send a message, not that it'd really hurt Amazon that much if more people don't actually follow through with going to alternatives. Or you can complain about it with no results or actions.
- hughesjj 3y ago> IP addresses were intended to be a public good. Were they though? The first few blocks auctioned off all went to large tech institutions
- wmf 3y agoThe Internet was designed by hippies and IP addresses weren't auctioned in the old days; they were given for free. When IPv4 runout was in sight the hippies argued loudly that addresses should be rationed instead of sold.
- blibble 3y agowould be interested to see what they do to their lightsail prices if you add these new charges onto the existing prices their offering becomes completely uncompetitive
- supriyo-biswas 3y agoThe comment by Adi Santhanam[1] who is an AWS product manager for networking has indicated a Lightsail pricing increase for IPv4 later this year[2]. > Yes, Lightsail is revising instance bundle pricing to accommodate IPv4 and new pricing will be published later this year. We understand the importance of bundled and predictable pricing for Lightsail, so revised pricing will include the IPv4 conservation charge in a monthly bundle cost and not as a separate charge. [1] https://www.linkedin.com/in/adityasanthanam/ https://www.linkedin.com/in/adityasanthanam/ [2] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/ https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address...
- throw555chip 3y ago> IPv4 conservation charge It's stunning, the hypocrisy that permeates Amazon now. I left AWS Lightsail for Oracle Cloud. When they announced Prime members would be shown Ads in movies and shows, we cancelled Prime.
- demondemidi 3y agoSwitched to heroku. 1/5th the price with Postgres service. Still use s3 for storage though.
- ramshanker 3y agoOne day will come, when network admins will be so happy to finally turn off IPv4 on their stack. When router manufacturers will feel happy to support only IPv6. It is definitely coming within my lifetime. So, these intermediate steps are just cooking the final dish. Peace. ;)
- flumpcakes 3y agoI don't think that will ever happen... Too many big businesses squatting on their IPv4 allocations to ever want to spend the money to implement IPv6. They don't need to worry about allocation running out or charging for IPs because they've got theirs. They would need to be forced to move by customers, probably through an ISP being IPv6 only. And that probably won't ever happen as the customers of those ISPs would drop them for one that does support IPv4 because they expect access to the same big businesses mentioned earlier. I think the whole thing has lots of inertia to not move to IPv6 and there's no incentive to force it.
- _trampeltier 3y agoNot just that, there are other networks too on IPv4. In industry automation, IPv6 is no thing at all yet.
- SamuelAdams 3y agoOnce GitHub works with ipv6 I’ll start to take it seriously.
- urda 3y agoYup and AWS CDK doesn’t support it either. Not happy that AWS is pushing this and they don’t even fully support it.
- supriyo-biswas 3y agoNot having mature IPv6 support for VPC network, even though regrettable, is understandable, but not supporting it for public endpoints like {s3,ec2,lambda,sqs,...}.{region}.amazonaws.com is a real head scratcher. Perhaps AWS could run these endpoints through Cloudfront in order to get IPv6 reachability.
- radarsat1 3y agoTo be fair I have a bunch of instances with public IP addresses just so I can ssh into them easily. This situation made me look into how I'd get into these instances otherwise and indeed you can set up an appropriate endpoint and then run "aws ec2 instance-connect" to make a tunnel that gets you an ssh connection without needing the public IP, so just like that my needs for public IPs actually goes down pretty drastically. On the other hand, on my first try I couldn't get "instance-connect" to work and it turned out I needed a different package "awscliv2" which I had no idea existed.. I've been using "awscli" for the longest time and didn't know there was an alternative and more up to date package available. What a mess. Also, when running the new one apparently it does a bunch of weird docker magic in the background instead of just being a normal Python program so not sure what to think but I guess it works. If anyone knows a leaner solution to opening an instance-connect tunnel I'd love to know.
- calamari4065 3y agoIt spins up docker containers to create an ssh connection?!
- abadpoli 3y agoAre you using a docker image to run AWS CLI or something? It shouldn’t have anything to do with docker at all if you’re just running the bare ‘aws’ command.
- lightlyused 3y agoaws ec2-instance-connect doesn't use docker, it just sets up a short lived ssh key in the instance metadata that you can use to connect. You can connect either via a public ipv4, ipv6, or a vpc private endpoint.
- radarsat1 3y agoI don't really know any details, but all I can tell you is that this is the output of running it in a fresh environment (masked out the instance details and snipped some output..): $ docker rmi amazon/aws-cli <snip> $ cd /tmp $ python3 -m venv venv <snip> $ . venv/bin/activate $ pip install awscliv2 <snip> $ ssh -i mykey.pem ec2-user@i-masked -o ProxyCommand='awsv2 ec2-instance-connect open-tunnel --instance-id i-masked' Unable to find image 'amazon/aws-cli:latest' locally latest: Pulling from amazon/aws-cli 6ebddf7084e9: Pull complete eb7d160dbc3b: Pull complete af71d24e41d0: Pull complete cf26adf9ea98: Pull complete 2491adb1df28: Pull complete Digest: sha256:a8c8edb4641672d9ef61873594aa02d1c493341ca30f96e257fdc4d3da17ef9c Status: Downloaded newer image for amazon/aws-cli:latest A newer release of "Amazon Linux" is available. <snip> And now I am logged into the machine. You can clearly see that it downloaded an AWS docker image. Exit from ssh, back to local terminal, and now there is an image on my machine: $ docker images | grep aws-cli amazon/aws-cli latest 817d1061df76 3 hours ago 384MB So I don't know if I agree that aws ec2-instance-connect doesn't use docker. And also, I don't necessarily have a problem that it does, it just surprised me a bit.
- MagicMoonlight 3y ago[flagged]
- throw0101b 3y ago> And this is why I think we need to just modify IPv4 to add more numbers. There is no "just" in this. Copy-pasting from my other comment: -- IPv4 data structures have four bytes/octets (4B) for addresses. So how do you fit 8B of addresses in 4B structures? You don't. So you have to update every network element—host (desktop, laptop, mobile, embedded), router, switch, firewall—to have a new data structure (and maybe new function/system calls, as the old ones assume the old structures). So all devices have to have updated network stacks, including long-lived ones that sometimes are not touched for a decade+. And not just pure networking code: anything that touches (e.g.) DNS as well, as A records are 4B-only as well, so you need a new record type and deploy new DNS server and resolver code everywhere. But of course if you have a 4B-only network elements/devices, they cannot talk to 8B-only devices/services, so you have to create translation mechanisms because some devices may not yet have the update 8B-capable network stack. And sometimes an 8B network is an island in a sea of 4B, so you have to have tunneling. Of course some may have both 4B and 8B, and want to talk to something has also has 4B and 8B, so now you have to have code for source/destination selection. -- So "just" expanding IPv4 to IPv4+ ends up being the exact same amount of work as ended up with IPv6. Only only thing you could say with "just" more addresses is keeping ARP and the like (instead of DAD, etc).
- lucb1e 3y agoIn what way would this have "Complete backwards compatibility"? Maybe read https://en.wikipedia.org/wiki/Internet_Protocol https://en.wikipedia.org/wiki/Internet_Protocol first, specifically the part where it specifies the on-the-wire format. What backwards compatible change would you actually propose there?
- justsomedood 3y agoThe IPv4 header is a fixed size. You can't include a source or destination address outside of 4 bytes. Hence, IPv6 as the replacement.
- 3y ago
- exabrial 3y ago[flagged]
- jjjjmoney 3y ago> ok, but why? Because NAT breaks a lot of services. > Is that going to change with ipv6? Yes. You no longer need NAT, so port negotiation is much easier (even when inbound is blocked) > Are you _really_ just going to allow random traffic into your network? Common misconception! Even without NAT, the router can have port/traffic policies. There's just no address translation happening. There's a lot of good stuff about IPv6, and I would encourage more people to learn about it and try it out. - ULAs can act like static internal LAN addresses - A "strong" NAT is easier to avoid and no longer breaks connections to things that are sensitive like gaming consoles - Randomized, temporary IPv6 public addresses are a nice feature, and mostly turned on by default - The biggest one is people seem to equate NAT = router/firewall. This is absolutely not the case, and they are distinctly different. You can absolutely have a router/firewall without NAT! - CG-NAT is becoming more popular due to the lack of IPv4 addresses, and I hate everything about that. - You can even run a NAT64 to provide IPv4 access to your IPv6-only devices
- exabrial 3y ago[flagged]
- jjjjmoney 3y agoYou might not but NAT has many different flavors, and many people don't get to choose which is used on their network. https://serverfault.com/questions/208522/what-is-strict-moderate-and-open-nat https://serverfault.com/questions/208522/what-is-strict-mode... This can particularly play havoc with sensitive protocols like STUN. I believe many game consoles make use of this when in multiplayer matches. I have personally run into this using OpenBSD's pf, but I'm fortunate enough to have access and the known-how to fix it for my consoles. It's one of those things that's fine until you run into "edge cases," and unfortunately NAT configurations can introduce a lot of undefined behavior from the user perspective.
- deathanatos 3y agoSame story on every cloud, AFAICT. Admittedly this was a couple years ago, but last I checked, Azure managed PG didn't support v6. (We're mostly moving away from Azure for other reasons … so I'll probably never re-check.) GKE on GCP doesn't really support v6. (If you selected the v2 "data plane" when you created your cluster, then it can, assuming the vnet can. If not, then not yet, and there's no way to upgrade data planes presently.) Peering VPCs doesn't work with v6-only, meaning if I want to peer VPCs, I pretty much am forced to solve all the problems v4 has with that … which defeats the entire point of a v6 peering. Cloud NAT doesn't support v6, so I'm super not clear on how ULA VPCs are supposed to work.
- ianburrell 3y agoI'm not sure what the AWS services not supporting IPv6 has to do with charging for public IPv4 usage. Private IPv4 is still free so can access services over endpoints. NAT gateways cost the same and can access services over public IPv4 network. AWS also added IPv6 NAT64 gateway so it should be possible to run IPv6-only internally and still access AWS services and the rest of the Internet.
- supriyo-biswas 3y agoThis would be acceptable if this internal route was already configured for free. However, it appears VPC endpoints have their own pricing[1], at which point one must carefully consider whether paying up for the IPv4 address is the better option. [1] https://aws.amazon.com/privatelink/pricing/ https://aws.amazon.com/privatelink/pricing/
- GabeIsko 3y agoI'm curious, why can't you use an elastic IP?
- supriyo-biswas 3y agoThis entire thread is about the additional costs imposed on a publicly accessible IP[1]. Granted, there are other (but similarly expensive) workarounds such as NAT gateways[2] for outbound connectivity or the cheaper NAT instance method which AWS doesn't support any more, but there are alternatives[3]. However, for use cases requiring inbound connectivity such as setting up websites on EC2 instances, or using an ELB which need internet access, you need an IPv4 address and these charges definitely rack up. [1] https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/ https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address... [2] https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gat... [3] https://fck-nat.dev https://fck-nat.dev
- GabeIsko 3y ago
- wenbin 3y agoWe [1] just went through a process to remove public ipv4 IPs for some of our internal facing EC2 instances. Just in case some people are on the same boat. Here's a simple process [2] to remove public ipv4 IPs from existing EC2 instances (no need to shutdown / reboot) - 1) Create a new elastic ip with autoassigned ipv4 IP - https://us-west-1.console.aws.amazon.com/ec2/home?region=us-west-1#Addresses https://us-west-1.console.aws.amazon.com/ec2/home?region=us-...: 2) Associate this new elastic ip to an existing EC2 instance. This will replace existing public ipv4 ip of this instance. 3) Create a new network interface - https://us-west-1.console.aws.amazon.com/ec2/home?region=us-west-1#NIC https://us-west-1.console.aws.amazon.com/ec2/home?region=us-...: 4) Attach this new network interface to the EC2 instance. Now the EC2 instance has two network interfaces, thus two private ipv4 IPs. 5) Disassociate the new elastic ip & release the ip - https://us-west-1.console.aws.amazon.com/ec2/home?region=us-west-1#Addresses https://us-west-1.console.aws.amazon.com/ec2/home?region=us-...: By this point, the EC2 instance doesn't have a public ipv4 ip anymore. --- [1] https://www.listennotes.com/ https://www.listennotes.com/ [2] https://stackoverflow.com/questions/38533725/can-i-remove-the-public-ip-on-my-instance-without-terminating-it https://stackoverflow.com/questions/38533725/can-i-remove-th...
- redox99 3y agoHad IPv6 been a superset of IPv4, we would have switched 10 years ago. IPv4 1.2.3.4 becomes IPv6 0.0.0.0.1.2.3.4 Owning IPv6 0.0.0.0.1.2.3.4 means you also own IPv4 1.2.3.4, because addresses that begin with 4 zeroes mean they also own the equivalent IPv4 address. Owning 2.2.2.2.1.2.3.4 means you do not fully own an IPv4 address. In this case you'll have a NAT IPv4 address. If you connect to 1.2.3.4 you use the IPv4 protocol. If you connect to 0.0.0.0.1.2.3.4 or 2.2.2.2.1.2.3.4 you use IPv6 packets that are identical but larger header to accommodate the bigger address. As long as you have an IPv6 that begins with 4 zeroes, you are fully compatible with everything, without needing any kind of NAT. If you have an IPv6 2.2.2.2.1.2.3.4 then you'll need NAT to connect to IPv4 addresses, but can connect directly to IPv6 addresses.
- hot_gril 3y agoI agree and have said similar things. The address exhaustion thing is an excuse for tons of unrelated changes in v6, plus resetting ownership.
- ianlevesque 3y agoThis comes up every time, but it doesn't make any sense. Routers, software, IT professionals, would've all been just as happy to not support IPv4.1 as they have been to not support IPv6. At this point though the inflection point has already been passed adoption-wise and AWS needs to just do the thing already.
- hot_gril 3y agov6 introduces more hurdles. New different kinds of addresses (link-local, etc). No more NAT by default. Existing v4 addresses not accessible over it. In contrast, switching to this "v4.1" would be low-risk. You just support longer addresses, that's it.
- snuxoll 3y agoSupporting longer addresses still means there's no forwards compatibility from v4. Neighbor discovery replacing ARP, link local addresses, etc. are not really the source of headache when it comes to v6 deployments - the legacy environment that v4 created is.
- bell-cot 3y agoHmm... How much is human psychology - Scarce & Expensive is Desirable; Cheap & Plentiful is Low Class - discouraging migration from IPv4 to IPv6?
- deleted 3y ago[deleted]
- dluga93 3y agoI think you have it the wrong way around. Scarce & Desirable is Expensive; Low Class & Plentiful is Cheap It doesn't always go both ways.
- djbusby 3y agoNa, cause if it's scarce and you charge a lot it becomes desirable - is a psych trick.
- hot_gril 3y agoYou wanna bring psychology into it, it seems like v6 abuses the crisis of low address supply to sneak in a bunch of unrelated changes. If the solution were truly just aimed at adding more addresses, it would've looked very different, for instance the existing ipv4 addresses would've been carried over to ipv6. Another thing about humans, addresses like 2001:4860:4860::8888 look awful. You gonna tell me that's an upgrade over 8.8.8.8? And 192.168.1.2 becomes fe80::1c03:b6d1:9222:3a02. Why can't I keep 192.168.1.2?
- LinAGKar 3y agoWhy carry over mistakes from IPv4 when they have an opportunity to fix them? When else are they gonna make those changes? And how would you propose making larger addresses without making them longer?
- hot_gril 3y agoThere isn't a strong enough consensus that these were mistakes, aside from making the address size too small. Maybe removing fragmenting was uncontroversial, but aside from that, ipv6 seems more complicated than ipv4 in many ways. Special kinds of addresses (link-local, v4-mapped, ULA, etc), special ways to write them, and so on. > And how would you propose making larger addresses without making them longer? Pre-existing ones don't need to be longer. If my IP before was 1.2.3.4, it stays that way. If a new ISP can't afford /32s for its customers, maybe it hands out /48s like 1.2.3.4.5.6, and if there are ever 282 trillion users, the next one is 1.2.3.4.5.6.7. At home on my LAN, ofc 192.168.1.2 is free and I keep it. IPv6 addrs are only long because they're spread out.
- throw555chip 3y agoThe Reddit commenter who said "Everyone is charging for IPv4, except AWS (until now)" is uninformed or lying. I've been on Oracle Cloud Always Free selfhosting my mail and web services for months now including free IPv4 public addresses.
- Shorn 3y agohttps://awsipv6.neveragain.de/ https://awsipv6.neveragain.de/ IPv4 only: 91% If you want a more visceral feel to it - turn off "Hide IPv4-only services" and behold the sea of red.