Many ISPs are no longer handing out even 1 public ipv4 address per account, and instead opting for CGnat which further breaks and stratifies the internet.

Tmobile for example is 464xlat which is even worse than cgnat since it requires tampering with dns responses.

Given the situation many ISP are in, most serious companies offering services on the internet have supported ipv6 for a long time now in order to offer the most competitive service possible. And with cloudflare now serving up a large amount of traffic, a lot of all traffic is v6.

Believe it or not, but IPv6 is here and gaining ground.

[–] thorbot@lemmy.world 3 points 2 years ago (1 children)

Most ISPs already use it, what are you on about

[–] railsdev@programming.dev 1 points 2 years ago (2 children)

My ISP routinely has problems on IPv4. Even while it’s fully operational with very low ping, IPv4 performance is poor compared to IPv6. Add in NAT, port forwarding and all the mess IPv4 brings into the picture I can’t believe people are still advocating for disabling IPv6.

[–] thorbot@lemmy.world 1 points 2 years ago (1 children)

Yeah, people who think this just don't know what the hell they are talking about

[–] Bo7a@lemmy.ca -1 points 2 years ago

Don't be so quick to paint everyone with the same brush. I have had my Ccna since 2003, he.net ipv6 sage since like 2009, netadmin for literally millions of nodes. Architect for even more.

And I still disable ipv6 on most machines for personal use.

[–] aniki@lemm.ee -1 points 2 years ago (2 children)

Have you ever tried NATing v6 on a router from 2019? good fucking luck

[–] dragonfly4933@lemmy.dbzer0.com 1 points 2 years ago (1 children)

As long as your ISP is handing out a block of IPs, you don't need NAT for v6.

[–] aniki@lemm.ee 2 points 2 years ago

I'm talking about NATing your v4 app over v6.

[–] railsdev@programming.dev 0 points 2 years ago

Why would I want to support IPv4 in 2023? Lol