ERROR:WU00:FS00:Exception: Failed to connect

[Son_of_Man]

I'm trying to start a folding team at my forum, but I can't even get the program to download work. This error repeats over and over in the log.

Code: Select all

14:37:11:WU00:FS00:Connecting to www.stanford.edu:80
14:37:11:ERROR:WU00:FS00:Exception: Failed to connect to www.stanford.edu:80: The requested address is not valid in its context. 

Does anyone know how to fix this? If it helps, I'm running FAH v7.1.52.

[7im]

Disable IPv6.

[ponley]

Kind of a head in the sand fix isn't it?

[7im]

Kind of a head in the sand fix isn't it?

Talk to Microsoft. Not a fah problem.

[sortofageek]

Does anyone know how to fix this? If it helps, I'm running FAH v7.1.52.

See this Microsoft Knowledge Base article: http://support.microsoft.com/kb/2533454

[ponley]

Kind of a head in the sand fix isn't it?

Talk to Microsoft. Not a fah problem.

I run Linux and have been struggling with installation of the V7 client and
this is the last stumbling block.

http://www.stanford.edu is CNAMEd to www-v6.stanford.edu which has an
IPv6 address. MOST Linux distros give IPv6 addresses priority so the fact
that there is an IPv6 address available means that MOST Linux distros will try to
use the IPv6 address.

Code: Select all

root@Asthmatic:/home/paul/folding# dig aaaa www.stanford.edu

; <<>> DiG 9.8.1-P1 <<>> aaaa www.stanford.edu
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30259
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 7

;; QUESTION SECTION:
;www.stanford.edu.              IN      AAAA

;; ANSWER SECTION:
www.stanford.edu.       158     IN      CNAME   www-v6.stanford.edu.
www-v6.stanford.edu.    46      IN      AAAA    2607:f6d0:0:925a::ab43:d7c8

;; AUTHORITY SECTION:
stanford.edu.           45736   IN      NS      Aerathea.stanford.edu.
stanford.edu.           45736   IN      NS      Avallone.stanford.edu.
stanford.edu.           45736   IN      NS      Argus.stanford.edu.
stanford.edu.           45736   IN      NS      Atalante.stanford.edu.

;; ADDITIONAL SECTION:
Argus.stanford.edu.     46      IN      A       171.64.7.115
Argus.stanford.edu.     46      IN      AAAA    2607:f6d0:0:9113::ab40:773
Aerathea.stanford.edu.  46      IN      A       152.3.104.250
Atalante.stanford.edu.  46      IN      A       171.64.7.61
Atalante.stanford.edu.  46      IN      AAAA    2607:f6d0:0:d32::ab40:73d
Avallone.stanford.edu.  46      IN      A       171.64.7.88
Avallone.stanford.edu.  46      IN      AAAA    2607:f6d0:0:9116::ab40:758

;; Query time: 30 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Wed Aug  8 04:15:40 2012
;; MSG SIZE  rcvd: 320

A ping6 of http://www.stanford.edu indicates that 2607:f6d0:0:bbb::ab42:ffa5
claims that http://www.stanford.edu (2607:f6d0:0:925a::ab43:d7c8) is unreachable.
This means that a router at 2607:f6d0:0:bbb::ab42:ffa5 will not forward or
has no route to http://www.stanford.edu.

Code: Select all

root@Asthmatic:/home/paul/folding# ping6 www.stanford.edu
PING www.stanford.edu(www-v6.Stanford.EDU) 56 data bytes
From 2607:f6d0:0:bbb::ab42:ffa5 icmp_seq=1 Destination unreachable: Address unreachable
From 2607:f6d0:0:bbb::ab42:ffa5 icmp_seq=2 Destination unreachable: Address unreachable
From 2607:f6d0:0:bbb::ab42:ffa5 icmp_seq=3 Destination unreachable: Address unreachable
^C
--- www.stanford.edu ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2002ms

A quick check of whois shows that that router belongs to:

OrgName: Stanford University
OrgId: STANFO
Address: 241 Panama Street
Address: Pine Hall, room 125
City: Stanford
StateProv: CA
PostalCode: 94305-4102
Country: US

Code: Select all

root@Asthmatic:/home/paul/folding# whois 2607:f6d0:0:bbb::ab42:ffa5
#
# The following results may also be obtained via:
# http://whois.arin.net/rest/nets;q=2607:f6d0:0:bbb::ab42:ffa5?showDetails=true&showARIN=false&ext=netref2
#

NetRange:       2607:F6D0:: - 2607:F6D0:FFFF:FFFF:FFFF:FFFF:FFFF:FFFF
CIDR:           2607:F6D0::/32
OriginAS:       AS32
NetName:        SUNET-V6
NetHandle:      NET6-2607-F6D0-1
Parent:         NET6-2600-1
NetType:        Direct Allocation
RegDate:        2008-11-24
Updated:        2012-03-02
Ref:            http://whois.arin.net/rest/net/NET6-2607-F6D0-1

OrgName:        Stanford University
OrgId:          STANFO
Address:        241 Panama Street
Address:        Pine Hall, room 125
City:           Stanford
StateProv:      CA
PostalCode:     94305-4102
Country:        US
RegDate:        
Updated:        2011-09-24
Ref:            http://whois.arin.net/rest/org/STANFO

OrgAbuseHandle: RR959-ARIN
OrgAbuseName:   Roberts, Rosalea 
OrgAbusePhone:  +1-650-723-3352 
OrgAbuseEmail:  [email protected]
OrgAbuseRef:    http://whois.arin.net/rest/poc/RR959-ARIN

OrgTechHandle: RR959-ARIN
OrgTechName:   Roberts, Rosalea 
OrgTechPhone:  +1-650-723-3352 
OrgTechEmail:  [email protected]
OrgTechRef:    http://whois.arin.net/rest/poc/RR959-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

The reason that all of your clients must turn off IPv6 for V7 to function is that
http://www.stanford.edu resolves to an unreachable IPv6 address. You are thus asking anyone
who is kind enough to donate cpu cycles to your project to sever their connectivity
to the IPv6 network because you are serving bad DNS information. This problem can be
solved by undreds of people inconviencing themselves, you could change one line in your zone file
so that http://www.stanford.edu does not resolve to an IPv6 address, or you can fix the routing problem
between 2607:f6d0:0:bbb::ab42:ffa5 and the http://www.stanford.edu server.

[7im]

And where is the OS IPv6 failover functionality to IPv4?

In any case, I'll make sure PG sees this detailed analysis, but that device is likely outside their control.

[ponley]

And where is the OS IPv6 failover functionality to IPv4?.

I would have to see the code to see exactly what the error message means.

Code: Select all

ERROR:WU00:FS00:Exception: Failed to connect to www.stanford.edu:80: The requested address is not valid in its context. 

Actually looks like the code may be confused by the IPv6 address where it expects to see an IPv4 address but that is only a guess with out knowing what is going on in the code. If the code is infact IPv6 aware and trying to connect to the IPv6 address then the FAH client is likely timing out and throwing it's error BEFORE the OS if failing over. If you want to go that route then you could try increasing the timeout value before FAH throws the server unreachable error but that fact still remains that it really is not the OS's responsibility to find a different address for the server, DNS said it is at 2607:f6d0:0:925a::ab43:d7c8 but there is no route to that address. Running MTR shows that the route makes 14 hops between here and 2607:f6d0:0:bbb::ab42:ffa5 with 0% loss before hitting a wall.

In any case, I'll make sure PG sees this detailed analysis, but that device is likely outside their control.

My guess is that the device is functioning EXACTLY as they want it to. IPv6 brings to the table many new security issues that many networks are not yet prepared for so by not admitting ANY IPv6 traffic the security issue becomes moot. The best fix at this time is to stop DNS from resolving http://www.stanford.edu to an IPv6 address. That is a simple matter of removing the AAAA record from www-v6.stanford.edu or remove CNAME record from http://www.stanford.edu and give it it's own A record. That fact is that you have a CNAME record that sends all traffic bound to http://www.stanford.edu to www-v6.stanford.edu instead and www-v6 sure looks like it's intended to be an IPv6 server but it can't be reached.

As an aside, I would bet that since the problem shows up on the first device on stanfords network (the hop before 2607:f6d0:0:bbb::ab42:ffa5 belongs to CENIC) anyone working on campus might never see this problem as they do not need to travers this router.

[gwildperson]

Stanford is not likely to disable IPv6 for the entire campus just because of a minor problem with one server. They're more likely to find and fix the underlying problem.

[7im]

I don't think anyone suggested disabling IPv6 at all of Stanford, just on that one donor's computer having this "minor" issue.

It wouldn't be minor to me if it prevented me from folding...

[ponley]

Stanford is not likely to disable IPv6 for the entire campus just because of a minor problem with one server. They're more likely to find and fix the underlying problem.

The underlying problem is that the DNS records tell the world that http://www.stanford.edu is at 2607:f6d0:0:925a::ab43:d7c8. but Stanford has decided to disconnect that address from the internet. There are two right ways to fix the problem, fix the connection from the internet to 2607:f6d0:0:925a::ab43:d7c8 (assuming the connection is broken), or don't tell the world that the server can be reached there (if Stanford does not want people to be able to connect to this address). Both are Proper ways to fix the problem depending on whether you want to be able to access the server on IPv6 or not.

As I mentioned above, IPv6 brings new security issues to the table so Stanford may well not want this address routable. While IPv4 has private unroutable address ranges effectively offering a layer of insulation or security almost all IPv6 addresses are world routable giving the 'bad guys' a much more direct route to your network.

[ponley]

I don't think anyone suggested disabling IPv6 at all of Stanford, just on that one donor's computer having this "minor" issue.

It wouldn't be minor to me if it prevented me from folding...

You must know some people in high places 7im, it seems that http://www.stanford.edu now has IPv6 connectivity.

Code: Select all

paul@Asthmatic:/home/paul/folding# ping6 -n www.stanford.edu
PING www.stanford.edu(2607:f6d0:0:925a::ab43:d7c8) 56 data bytes
64 bytes from 2607:f6d0:0:925a::ab43:d7c8: icmp_seq=1 ttl=34 time=92.7 ms
64 bytes from 2607:f6d0:0:925a::ab43:d7c8: icmp_seq=2 ttl=34 time=91.4 ms
64 bytes from 2607:f6d0:0:925a::ab43:d7c8: icmp_seq=3 ttl=34 time=91.2 ms
64 bytes from 2607:f6d0:0:925a::ab43:d7c8: icmp_seq=4 ttl=34 time=91.8 ms


paul@Asthmatic:/home/paul/folding# telnet www.stanford.edu 80
Trying 2607:f6d0:0:925a::ab43:d7c8...
Connected to www.stanford.edu.
Escape character is '^]'.

[bruce]

You must know some people in high places 7im, it seems that http://www.stanford.edu now has IPv6 connectivity.

He probably does, but I know for fact that he's not the only one. Not everybody who reads the forum necessarily posts.

[ponley]

Point taken.

Thank You to whoever got this taken care of.

I was not looking forward to shutting down my IPv6 connectivity every time fah wanted to phone home.

[uncle_fungus]

The question now is, will the FAHclient, now that the address is correctly resolvable, actually connect and download work over IPv6?