[diegocg]

You can laugh but Google stats show nearly 50% of their global traffic being ipv6 (US is higher, about 56%), Facebook is above 40%.

[londons_explore]

As soon as we get to about 70%, I reckon some games and apps will stop supporting ipv4 on the basis that nat traversal is a pain and dual stack networking is a pain.

If you spend 2 days vibe coding some chat app and then you have to spend 2 further days debugging why file sharing doesn't work for ipv4 users behind nat, you might just say it isn't supported for people whose ISP's use 'older technology'.

After that, I reckon the transition will speed up a lot.

[gruturo]

> some games and apps will stop supporting ipv4 on the basis that nat traversal is a pain and dual stack networking is a pain

None of these are actually the game/app developers' problem. The OS takes care of them for you (you may need code for e2e connectivity when both are behind a NAT, but STUN/TURN/whatever we do nowadays is trivial to implement).

[eqvinox]

> None of these are actually the game/app developers' problem.

Except people complain to the game/app developer when it doesn't work.

[RedShift1]

What makes you think filesharing is going to work any better on IPv6?

[kccqzy]

NAT traversal not needed. Just need to deal with firewalls. So that's one fewer thing to think about when doing peer-to-peer file sharing over the internet.

[ectospheno]

“Just need to deal with firewalls.”

The only sane thing to do in a SLAAC setup is block everything. So no, it isn’t a solved problem just because you used ipv6.

[kccqzy]

No. Here's a simple strategy: the two peers send each other a few packets simultaneously, then the firewall will open because by default almost all firewalls allow response traffic. IPv6 simplifies things because you know exactly what address to send to.

[ectospheno]

That is my point. You hole punch in that scenario even without NAT. It is no easier.

[chasil]

It appears that my AT&T mobile data runs over IPv6.

If all the mobile is removed, what's the percentage then?

[zokier]

In North America there is some difference but worldwide it is more pronounced.

https://radar.cloudflare.com/explorer?dataSet=http&groupBy=i...

[grogenaut]

Younger folks are much less likely to have a PC. It may all (70%) be phones or phone like networks in 20 years

[avhception]

And yet here I am, fighting with our commercial grade fiber ISP over obscure problems in their IPv6 stack related to MTU and the phase of the moon. Sigh. I've been at this on and off for about a year (it's not a high priority thing, more of a hobby).

[LtWorf]

But how much of it is not natted?

[msk-lywenn]

Do they accept smtp over ipv6 now?

[rwmj]

They do, but I had to change my mail routing to use IPv4 to gmail because if I connect over IPv6 everything gets categorised as spam.

[betaby]

MX has IPv6:

~$ host gmail.com gmail.com has address 142.250.69.69 gmail.com has IPv6 address 2607:f8b0:4020:801::2005 gmail.com mail is handled by 10 alt1.gmail-smtp-in.l.google.com. gmail.com mail is handled by 30 alt3.gmail-smtp-in.l.google.com. gmail.com mail is handled by 5 gmail-smtp-in.l.google.com. gmail.com mail is handled by 20 alt2.gmail-smtp-in.l.google.com. gmail.com mail is handled by 40 alt4.gmail-smtp-in.l.google.com.

~$ host gmail-smtp-in.l.google.com. gmail-smtp-in.l.google.com has address 142.250.31.26 gmail-smtp-in.l.google.com has IPv6 address 2607:f8b0:4004:c21::1a

[stackskipton]

Yes. However SMTP these days is almost all just servers exchanging mail, IPv6 support is much less priority.

[1718627440]

How does your MUA sends the message to the server? That's also SMTP.

[creshal]

50%, after only 30 years.