> I've seen claims of providers putting IPv6 behind NAT, so don't think full IPv6 acceptance will solve this problem.
I get annoyed even when what's offered is a single /64 prefix (rather than something like a /56 or even /60), but putting IPv6 behind NAT is just ridiculous.
This shouldn't be mistaken for an anti-IPv6 post. There's also some steps you have to go through to enable IPv6 on your VPS networks, and there's still stuff like GitHub not handling IPv6. So, much as we need to migrate, we still have to support IPv4 connectivity for the foreseeable future.
> and there's still stuff like GitHub not handling IPv6.
And virtually everything inside of AWS still requires IPv4 so even if you have zero need to reach out to WAN, if you need any number of private AWS endpoints, you're going to be allocating some ipv4 blocks to your VPC :(.
I've worked at four tech companies and never saw a hint of IPv6 (except for some tests that verified that third-party networking code accepted that address family).
Instead I played with IPv6 at home to make sure I understood it well enough should it ever come up at work. We'll see!
There absolutely are annoyences IPv6 get rid of, that are much embedded in IT culture we only see them if we look.
Port forwarding, external/internal address split, split horizon DNS, SNI proxies, NAT, hairpin routing - some of the hacks made mostly because of shortage in IP space.
In theory.. but what happens when you want to change ISPs or your ISP doesnt assign static ipv6 blocks? Its recomnended but ISPs have no incentive to give a shit about you. Now all internal infra is not routable.
bilegeek|3 months ago
2.) Market segmentation: keeps home users from easily hosting their own services without spending $$$ on an upgraded plan.
3.) Adding on to #2, I've seen claims of providers putting IPv6 behind NAT, so don't think full IPv6 acceptance will solve this problem.
ls65536|3 months ago
I get annoyed even when what's offered is a single /64 prefix (rather than something like a /56 or even /60), but putting IPv6 behind NAT is just ridiculous.
unquietwiki|3 months ago
Shoutout to Hacker News for having IPv6 support!
baby_souffle|3 months ago
And virtually everything inside of AWS still requires IPv4 so even if you have zero need to reach out to WAN, if you need any number of private AWS endpoints, you're going to be allocating some ipv4 blocks to your VPC :(.
MathMonkeyMan|3 months ago
Instead I played with IPv6 at home to make sure I understood it well enough should it ever come up at work. We'll see!
sidewndr46|3 months ago
trueismywork|3 months ago
For someone just getting started with networking and learning things, this seems rhe best way to go forward.
bongodongobob|3 months ago
mrsssnake|3 months ago
Port forwarding, external/internal address split, split horizon DNS, SNI proxies, NAT, hairpin routing - some of the hacks made mostly because of shortage in IP space.
Tractor8626|3 months ago
somanyphotons|3 months ago
waynesonfire|3 months ago
abcdefg12|3 months ago