search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.2k stars 174 forks source link

IPv6 and NAT64 #2912

Open x414e54 opened 10 years ago

x414e54 commented 10 years ago

I am having some issues connecting to Steam on IPv6. My home connection uses NAT64 which translates the old fashioned IPv4 addresses to IPv6 and allows me to connect to IPv4. Internally my network is single stack IPv6 so my computer does not have an IPv4 address other than loopback.

Programs such as Chromium and Firefox work correctly on IPv4 and IPv6 sites.

WhyNotHugo commented 10 years ago

+1 on this. My entire network is pure-IPv6 (+NAT64 at a gateway/ISP level) and Steam is one of the three appications I've found in months that assume there's native-IPv4 connectivity.

This issue is critical, as it does not allow users to even log into steam, and there's absolutely no workaround.

simonbru commented 10 years ago

Steam still doesn't work on NAT64. Most incompatible applications work with a sock proxy which has access to IPv4 internet, but Steam doesn't support it, even as a system-wise setting.

WhyNotHugo commented 10 years ago

Entire months being unable to play any game with absolutely no workaround is an extremely critical issue (and reflects the issues of propietary distribution mechanisms such as Steam). Is there an ETA on this?

mxdpeep commented 9 years ago

Steam does not work over IPv6-in-IPv4 (RFC4213), testing now using HE.NET tunneling (no IPv4 connectivity here), only some parts work - like chat

WhyNotHugo commented 9 years ago

Steam does not work over IPv6-in-IPv4 (RFC4213), testing now using HE.NET tunneling (no IPv4 connectivity here), only some parts work - like chat

Really? I've found that authentication does not work on IPv6 (even with NAT64). How did you manage to log in with no IPv4?

mxdpeep commented 9 years ago

I don't know, it just worked! I cannot retest, different router and location

Maverik commented 7 years ago

IPV6 issues opened in 2013 - still valid in 2017.. says heaps about how much Valve cares about its clients. Sitting here on IPV6 only network, unable to use any of my purchases because it's steam is clearly connecting based off hardcoded IPV4 addresses rather than using hostnames otherwise DNS64 would have kicked in and I wouldn't be writing this.. 4 years after the first time this issue was opened.

Please put some effort into this. 4 years is enough time to put such a core issue on backburner.

fabiscafe commented 7 years ago

+1 for this. IPv6 should be available for steam in 2017. Please make this happen.

No0ne commented 5 years ago

+1 ... 2019 is approaching!

treysis commented 5 years ago

And still a no-no. At least on Linux. Didn't try Windows.

elsbrock commented 5 years ago

Classic Volvo.

No0ne commented 4 years ago

+1 ... 2020 is approaching!

ghost commented 4 years ago

I'm affected as well by this. As my IPv4 connection (DS-lite) of my cable provider is not 100% stable, I hoped that Steam would just use IPv6, but no, it doesn't work at all. If IPv4 is down, Steam refuses to start.

fourbytes commented 4 years ago

Also affected. Come on.

Nicholas-Johnson-opensource commented 4 years ago

Not spending money on Steam on this until this is fixed. Also, in a few years when residential ISPs start going NAT64, you do not want them charging extra fees to allow IPv4 to use Steam. It will be bad PR.

No0ne commented 3 years ago

+1 ... 2021 is approaching!

koutsie commented 3 years ago

please?

No0ne commented 1 year ago

Now MacOS Ventura automatically setups an integrated CLAT if it detects a NAT64/DNS64 network an Steam works! (see https://www.youtube.com/watch?v=zQk6YMO-7fw)

fabiscafe commented 1 year ago

@No0ne But how is this relevant in here? We all know that steam works on IPv4. If this is native or via any form of translation doesnt really matter. What we need is IPv6 support.

No0ne commented 1 year ago

True! absolutely!

TeamLinux01 commented 1 year ago

Please Valve, run a dual stack for your servers and services. We want to move to an IPv6 only future.

I don't want to worry about port overlaps or relying on UPnP. If I could just open the TCP/UDP ports for each IPv6 address, I would enjoy that very much.

Midar commented 1 year ago

It's 2023. Is Steam still using gethostbyname or what? Migrating to getaddrinfo really isn't that hard.

sgryphon commented 5 months ago

Steam can't even merge duplicate issues for this same problem; one since 2013, one 2014 -- that's over 10 years!

https://github.com/ValveSoftware/steam-for-linux/issues/2912 https://github.com/ValveSoftware/steam-for-linux/issues/3372

In that time IPv6 usage has grown from 2% to 45% (varies by country, some at 80-90%). There are now many IPv6-only networks -- several major mobile carriers, several ISPs, and IPv6-only is also common on guest networks (as phones and tablets support it well).

Steam is one of the major reasons why I haven't been able to switch my network over to IPv6-only, for easier single-stack management.

juliaszone commented 1 month ago

Vouch for IPv6 support, even if only with DNS64/NAT64 or all the way to native support on all servers. Slowly migrating more and more away from Dualstack to IPv6-only (absolutely no NAT64) or IPv6-mostly (using NAT64+DNS64), but it looks like devices/servers running Steam need to have a clat configured. More unnecessary work, only for Steam and like 1 or 2 other programs.