It's good to support it to resolve the chicken egg problem. If no service supports it, there is no sense in deploying it to the customers and the other way around.

Also you made the life better of people who have DS lite. They only get a public IPv6 and all their IPv4 traffic goes through a CGNAT.

▲

reddalo 3 hours ago | parent | next [-]

For people like me: DS Lite stands for "IPv6 dual-stack lite". My mind went directly to Nintendo and I was confused.

▲

ash 2 hours ago | parent | prev | next [-]

Unfortunately, individual actions would never be enough to solve the IPv6 chicken and egg problem. See djb's "IPv6 mess" article:

https://cr.yp.to/djbdns/ipv6mess.html

Yes, it is old, many examples are outdated, but the main points still hold. Decades later his suggestions for making IPv6 succeed are still not implemented.

▲

tormeh 2 hours ago | parent | next [-]

This stuff is obvious now, but I think back then this was probably quite clever.

▲

BadBadJellyBean 2 hours ago | parent | prev [-]

It's not a lot but it's better to be part of the solution than the problem even if it is an insignificant contribution.

	▲	commandersaki 14 minutes ago \| parent [-]
		Which is which?

▲

fc417fc802 3 hours ago | parent | prev [-]

For client server web browsing what's the downside of CGNAT? I'd understand if we were talking about self hosting a service from home but for typical consumer usage?

▲

gucci-on-fleek 2 hours ago | parent [-]

1. Peer-to-peer networking won't usually work correctly. And quite a bit of software uses P2P networking these days---BitTorrent, Zoom/Teams (via WebRTC), Tailscale, PlayStation/Xbox multiplayer, etc. Most of these services have automatic fallbacks when P2P networking doesn't work, but these fallbacks are usually slower and less reliable.

2. Most websites assume that 1 IPv4 address==1 household, so you'll often run into rate limits. Or even worse, you might be blocked entirely if your CGNAT neighbours are spammers or otherwise breaking website rules.

▲

hdgvhicv an hour ago | parent | next [-]

1) my stateful firewall is going to break most of that anyway

2) if cg nat is as popular as people claim then they won’t be doing that as it’s not an edge case

	▲	gucci-on-fleek 38 minutes ago \| parent [-]
		> 1) my stateful firewall is going to break most of that anyway Stateful firewalls and even regular NAT aren't much of an issue for P2P, but CGNAT is much more problematic [0]. > 2) if cg nat is as popular as people claim then they won’t be doing that as it’s not an edge case You'd hope, but people tend to be pretty slow to update their networking assumptions, so this is still pretty common. And it doesn't help that most CGNAT users tend to be either from poorer, since poorer countries and mobile data providers are far more likely to use CGNAT than legacy North American ISPs. [0]: https://tailscale.com/blog/how-nat-traversal-works

▲

fc417fc802 2 hours ago | parent | prev [-]

While true, neither of those are relevant in context (and I even explicitly acknowledged your first bullet in my comment above). It was suggested that a website operator deploying IPv6 would somehow improve the end user experience by virtue of avoiding CGNAT and I was questioning that. I do of course appreciate that going via CGNAT to a clueless operator that eagerly adds IPv4 bans can be problematic but that's more a question of why you as a consumer might want IPv6 connectivity not why a service provider would want to deploy it.

	▲	gucci-on-fleek an hour ago \| parent [-]
		> While true, neither of those are relevant in context (and I even explicitly acknowledged your first bullet in my comment above). Yeah, I just mentioned that because P2P networking is used a lot more than most people think these days, since even things like Zoom that look like typical client–server web browsing actually use P2P networking internally. > It was suggested that a website operator deploying IPv6 would somehow improve the end user experience by virtue of avoiding CGNAT and I was questioning that. Reliability and latency will be marginally better with IPv6 than with CGNAT, but this is so minor that I doubt that most people will notice this. And many CGNATs will RST connections that last too long, but most protocols have some sort of automatic retry/reconnect built in, so this shouldn't cause issues very often either. IPv6 addresses are quite a bit cheaper than IPv4 addresses in most clouds, but since most servers still need to support IPv4, this doesn't help you directly. Supporting IPv6 means that others using the cheaper IPv6-only cloud services will be able to connect to your server, but this doesn't matter for consumer-only services. So yeah, you're probably right that enabling IPv6 server-side won't have (m)any benefits. > I do of course appreciate that going via CGNAT to a clueless operator that eagerly adds IPv4 bans can be problematic but that's more a question of why you as a consumer might want IPv6 connectivity not why a service provider would want to deploy it. Being able to ban IP addresses without worrying about collateral damage is a pretty big benefit to the service provider though, for certain applications at least.