New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam doesn't work on IPv6-only (NAT64/DNS64) networks #3372

Open
oerdnj opened this Issue Jun 23, 2014 · 12 comments

Comments

Projects
None yet
@oerdnj

oerdnj commented Jun 23, 2014

I understand that my request might look like coming from Mars :), but there's an issue in the official steam client using a way to connect to steam servers the is not Internet Protocol compatible. (Yeah, I am not speaking about legacy IP ;)).

I am running on IPv6-only + NAT64/DNS64 network and Steam fails to connect to the servers although the connectivity works as expected - the IPv4 gets remapped to IPv6 addresses, so every application should not notice the difference unless:

a) you use some strange/ancient API to connect to TCP sockets
b) you use IP addresses instead of domain names to connect to steam servers

The fix is obvious:

a) add native support for IPv6 into steam and prefer IPv6 if found
b) use DNS to resolve the names of steam servers or have IPv6 address that gets used when IPv6 is detected.

I do not expect this to be solved quickly, but a record in internal tracker with some future fix would be nice.

DNS64 example:

$ dig IN AAAA store.steampowered.com @2001:1488:fffe:20::34

; <<>> DiG 9.9.5-4-Ubuntu <<>> IN AAAA store.steampowered.com @2001:1488:fffe:20::34
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64038
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;store.steampowered.com.        IN  AAAA

;; ANSWER SECTION:
store.steampowered.com. 5   IN  AAAA    2001:1488:fffe:30:ffff:ffff:173f:40c0

;; AUTHORITY SECTION:
steampowered.com.   9320    IN  NS  a8-66.akam.net.
steampowered.com.   9320    IN  NS  a24-64.akam.net.
steampowered.com.   9320    IN  NS  a1-164.akam.net.
steampowered.com.   9320    IN  NS  a11-67.akam.net.
steampowered.com.   9320    IN  NS  a26-65.akam.net.
steampowered.com.   9320    IN  NS  a9-67.akam.net.

;; Query time: 1 msec
;; SERVER: 2001:1488:fffe:20::34#53(2001:1488:fffe:20::34)
;; WHEN: Mon Jun 23 10:08:09 CEST 2014
;; MSG SIZE  rcvd: 211
@mxdpeep

This comment has been minimized.

Show comment
Hide comment
@mxdpeep

mxdpeep Feb 9, 2015

I am testing Steam over IPv6 only (using HE.NET tunnel), chat is working, no images or Steam news, updater does not work either

that means = there's some basic functionality within Steam for IPv6??

mxdpeep commented Feb 9, 2015

I am testing Steam over IPv6 only (using HE.NET tunnel), chat is working, no images or Steam news, updater does not work either

that means = there's some basic functionality within Steam for IPv6??

@cheako

This comment has been minimized.

Show comment
Hide comment
@cheako

cheako Apr 7, 2015

[0406/210657:WARNING:dns_config_service_posix.cc(292)] Failed to read DnsConfig.
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844

cheako commented Apr 7, 2015

[0406/210657:WARNING:dns_config_service_posix.cc(292)] Failed to read DnsConfig.
nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844

@gangsta2oo9

This comment has been minimized.

Show comment
Hide comment
@gangsta2oo9

gangsta2oo9 Dec 5, 2015

Why is Steam dont updating to ipv6 ? -.-

gangsta2oo9 commented Dec 5, 2015

Why is Steam dont updating to ipv6 ? -.-

@fiveghz

This comment has been minimized.

Show comment
Hide comment
@fiveghz

fiveghz Feb 28, 2016

I can confirm that the Steam client does not operate on an IPv6 only network, using NAT64/DNS64. This is on Mac OS 10.11.3 and Steam client built Feb 4 2016.

fiveghz commented Feb 28, 2016

I can confirm that the Steam client does not operate on an IPv6 only network, using NAT64/DNS64. This is on Mac OS 10.11.3 and Steam client built Feb 4 2016.

@vician

This comment has been minimized.

Show comment
Hide comment
@vician

vician Apr 11, 2016

Please fix it. Steam still doesn't work on IPv6 only network (with NAT64/DNS64).

vician commented Apr 11, 2016

Please fix it. Steam still doesn't work on IPv6 only network (with NAT64/DNS64).

@palaughton

This comment has been minimized.

Show comment
Hide comment
@palaughton

palaughton Apr 30, 2016

Strictly speaking, I'm not sure I'd consider this a Linux-specific issue, given that the Windows installer doesn't work behind NAT64, either: "Steam needs to be online to update. Please confirm your network connection and try again."

20160430 1 steam-ipv6

palaughton commented Apr 30, 2016

Strictly speaking, I'm not sure I'd consider this a Linux-specific issue, given that the Windows installer doesn't work behind NAT64, either: "Steam needs to be online to update. Please confirm your network connection and try again."

20160430 1 steam-ipv6

@pHr34kY

This comment has been minimized.

Show comment
Hide comment
@pHr34kY

pHr34kY Oct 22, 2016

I'm also unable to connect on my NAT64 setup. Even in after selecting offline mode, Portal2 throws a "STEAM validation rejected" error even when attempting single player mode. The source engine probably needs to have its socket code inspected as well.

Also, this ticket appears to be a duplicate of #2912.

pHr34kY commented Oct 22, 2016

I'm also unable to connect on my NAT64 setup. Even in after selecting offline mode, Portal2 throws a "STEAM validation rejected" error even when attempting single player mode. The source engine probably needs to have its socket code inspected as well.

Also, this ticket appears to be a duplicate of #2912.

@hsaito

This comment has been minimized.

Show comment
Hide comment
@hsaito

hsaito Sep 3, 2017

This also started affecting double-stack setting (e.g. Comcast, etc.) on Linux. The client loads sometimes, but the game fails to download.

hsaito commented Sep 3, 2017

This also started affecting double-stack setting (e.g. Comcast, etc.) on Linux. The client loads sometimes, but the game fails to download.

@mikaabra

This comment has been minimized.

Show comment
Hide comment
@mikaabra

mikaabra Oct 19, 2017

I tried again now with all-updated steam on fully updated Win10 with yesterdays fall creators update. On an IPv6 only network (with NAT64+DNS64), Steam won't even start. After trying this, it won't even start if I go back to dual stacked network. I actually have to reboot Win10 on the dual stack network for Steam to start again.

Microsoft has fixed Win10 so multiple normal functions now work on an NAT64+DNS64 network, software updates work nowadays for instance. But, Steam is a complete blocker. It won't even start and give an error message on an IPv6 only network (again, with IPv4 reachability through NAT64+DNS64).

mikaabra commented Oct 19, 2017

I tried again now with all-updated steam on fully updated Win10 with yesterdays fall creators update. On an IPv6 only network (with NAT64+DNS64), Steam won't even start. After trying this, it won't even start if I go back to dual stacked network. I actually have to reboot Win10 on the dual stack network for Steam to start again.

Microsoft has fixed Win10 so multiple normal functions now work on an NAT64+DNS64 network, software updates work nowadays for instance. But, Steam is a complete blocker. It won't even start and give an error message on an IPv6 only network (again, with IPv4 reachability through NAT64+DNS64).

@GroverChouT

This comment has been minimized.

Show comment
Hide comment
@GroverChouT

GroverChouT Jun 4, 2018

It has been four years ago, still no any actions?

GroverChouT commented Jun 4, 2018

It has been four years ago, still no any actions?

@cheako

This comment has been minimized.

Show comment
Hide comment
@cheako

cheako Jun 4, 2018

Thus no solution to the high price of address blocks.

cheako commented Jun 4, 2018

Thus no solution to the high price of address blocks.

@No0ne

This comment has been minimized.

Show comment
Hide comment
@No0ne

No0ne Sep 27, 2018

+1 ... 2019 is approaching!

No0ne commented Sep 27, 2018

+1 ... 2019 is approaching!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment