-
Notifications
You must be signed in to change notification settings - Fork 181
Description
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