derekivey
join:2006-03-30
Mechanicsburg, PA
kudos:1 Reviews:
 ·Verizon FiOS
1 edit | reply to whfsdude
Re: [IPv6] Comcast Speedtest Doesn't seem accurate. I'm on Verizon Fios (50/25) and using a HE tunnel. The test shows my IPv6 address. There's no way this is accurate, especially through the tunnel...
 |
|
 ropeguruPremium
join:2001-01-25
Mechanicsville, VA | reply to aveiga
Still not working here on a SiXXs tunnel. Can trace route and ping ok.
nslookup ipv6.speedtest.comcast.net
Server: UnKnown
Address: 2001:4830:1621::2
Non-authoritative answer:
Name: ipv6.speedtest.g.comcast.net
Address: 2001:558:1030:8:69:252:23:68
Aliases: ipv6.speedtest.comcast.net |
|
 graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | reply to aveiga
Thanks for keeping us informed. I do wonder why one poster can reach the site via an HE tunnel, but I cannot. |
|
ropeguruPremium
join:2001-01-25
Mechanicsville, VA | said by graysonf:Thanks for keeping us informed. I do wonder why one poster can reach the site via an HE tunnel, but I cannot.
Did you ever have any luck reaching the speedtest? I haven't. |
|
|
|
graysonfPremium,MVM
join:1999-07-16
Fort Lauderdale, FL | No, I have not, not on an HE tunnel. |
|
1 edit | reply to aveiga
Just tested it and the test results still come up as IPv4. Also it's an honor to help the engineers out 
 |
|
 RR ConductorNWP RR Inc.,serving NW CAPremium
join:2002-04-02
Redwood Valley, CA
kudos:1
1 edit | Here as well-
I love the distance too, I'm 170 miles northwest of San Jose, not 7,950 miles  |
|
 NetDogPremium,VIP
join:2002-03-04
Parker, CO
kudos:4
 ·Comcast
| reply to whfsdude
Sweet it worked for me..
I do like the fact that I am 7000mi from the server, should be more like 20 miles..
aveiga is this a bug or a feature? |
|
| reply to whfsdude
Also via HE tunnel...
$ telnet ipv6.speedtest.comcast.net 80
Trying 2001:558:1030:8:69:252:23:68...
Connected to ipv6.speedtest.comcast.net.
Escape character is '^]'.
GET / HTTP/1.1
Host: ipv6.speedtest.comcast.net:80
^]
telnet> quit
Connection closed.
That was over 3 minutes waiting there. So ... something the web server's doing is causing the problems. |
|
