steam-for-linux
steam-for-linux copied to clipboard
ValveSoftware
IPv6 and NAT64
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.
+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.
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.
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?
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
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?
I don't know, it just worked! I cannot retest, different router and location
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.
+1 for this. IPv6 should be available for steam in 2017. Please make this happen.
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.
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.
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)
@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.
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.
It's 2023. Is Steam still using gethostbyname or what? Migrating to getaddrinfo really isn't that hard.
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.
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.
It has been working for me for quite a while. I just tested again on a pure NAT64 VPN, no IPv4 connectivity at all, no A records being returned by DNS - it works.
I tried both, with stripped A records and without. Without, it took a bit longer for v4 to time out and then worked as well.
Doesn't work for me, I added --filter-A to my dnsmasq service and on the Windows machine Steam says "NO CONNECTION" at the bottom. If I try to install a game it says "No internet connection".
It currently only works on macOS since Ventura where it automatically enables CLAT.