7im wrote:ponley wrote: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.
Not everybody who reads the forum necessarily posts. 