 NetDogPremium,VIP
join:2002-03-04
Parker, CO
kudos:4
 ·Comcast
| reply to NetFixer
Re: [IPv6] IPv6 Comcast Speedtest said by NetFixer:My guess would be a Netgear router. I have to reboot my WNR1000v2-VC about once a week because it loses IPv6 sync. The router's WAN and LAN, and attached devices still have valid looking IPv6 addresses, but they don't work anymore until I reboot the router, and it gets (and redistributes to its LAN devices) new IPv6 address assignments from Comcast.
What version of OS do you have on the WNR1000v2-VC, I will start asking questions.. |
|
NetDogPremium,VIP
join:2002-03-04
Parker, CO
kudos:4 Reviews:
·Comcast
| reply to ropeguru
said by ropeguru:Any comment on why the speedtest does not work for those of us on a tunnel? Has it been setup for comcast users only in Comcast IPv6 address space?
I am going to ask one of the guys that works on the Speedtest server to take a look at this post.. |
|
 ropeguruPremium
join:2001-01-25
Mechanicsville, VA | said by NetDog:said by ropeguru:Any comment on why the speedtest does not work for those of us on a tunnel? Has it been setup for comcast users only in Comcast IPv6 address space?
I am going to ask one of the guys that works on the Speedtest server to take a look at this post.. Thanks... I am willing to work with whoever to torubleshoot why this is happening. Might very well be an issue on my end but I can do traceroutes and pings from looking glass sites back into my host.
For some reason the thought of using a COmcast looking glass site had not occurred to me if such a thing is available. |
|
NetDogPremium,VIP
join:2002-03-04
Parker, CO
kudos:4 | ropeguru,
Can you paste a traceroute to the speedtest server please. I was told that it should not be firewalled on our end. |
|
ropeguruPremium
join:2001-01-25
Mechanicsville, VA
3 edits | said by NetDog:ropeguru,
Can you paste a traceroute to the speedtest server please. I was told that it should not be firewalled on our end.
Guess I should have started with the basics. Was assuming that I was even hitting your server in the first place when I was getting the connecting then the waiting in the browser. However, the traceroute shows a different story.
tracert -6 ipv6.speedtest.comcast.net
Tracing route to ipv6.speedtest.g.comcast.net [2001:558:1010:5:68:87:73:52]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 2001:4830:1621::254
2 31 ms 31 ms 27 ms gw-60.qas-01.us.sixxs.net [2001:4830:1600:3b::1]
3 40 ms 33 ms 25 ms sixxs-asbnva-gw.customer.occaid.net [2001:4830:e6:7::2]
4 28 ms 31 ms 27 ms sixxs-gw.hotnic.us.occaid.net [2001:4830:e6:7::1]
5 28 ms 27 ms 30 ms ibr01-ve96.asbn01.occaid.net [2001:504:0:2:0:3:71:1]
6 33 ms 35 ms 33 ms bbr01-p2-1.nwrk01.occaid.net [2001:4830:ff:f150::1]
7 41 ms 41 ms 40 ms tata.nwrk01.occaid.net [2001:4830:e2:a::2]
8 134 ms 153 ms 123 ms if-5-0-4.mcore4.nyy-newyork.ipv6.as6453.net [2001:5a0:400:500::15]
9 138 ms 139 ms 130 ms if-ae5.5.tcore1.nto-newyork.ipv6.as6453.net [2001:5a0:400:200::e]
10 Destination net unreachable.
Trace complete.
Edit: However, ping works... (But it is a different IP.)
ping -6 ipv6.speedtest.comcast.net
Pinging ipv6.speedtest.g.comcast.net [2001:558:1030:8:69:252:23:68] with 32 bytes of data:
Reply from 2001:558:1030:8:69:252:23:68: time=145ms
Reply from 2001:558:1030:8:69:252:23:68: time=138ms
Reply from 2001:558:1030:8:69:252:23:68: time=122ms
Reply from 2001:558:1030:8:69:252:23:68: time=121ms
Ping statistics for 2001:558:1030:8:69:252:23:68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 145ms, Average = 131ms |
|
 whfsdudePremium
join:2003-04-05
Washington, DC
 ·T-Mobile US
| reply to NetFixer
said by NetFixer:The »ipv6.speedtest.comcast.net site does not seem to work very well with IPv6 tunnels. I have even tried it using Comcast's 6to4 tunnel, and it did not even work with Comcast's own tunnel. Sometimes the site start page would load, but the test never worked. The actual speed test would either never start or it would hang busy and never finish. If you don't have native IPv6, that test site appears to be useless.
More specifically OCCAID (his tunnel pop) doesn't peer directly w/Comcast and their TATA link is really congested.
Comcast <> OCCAID congested (via TATA) path.
traceroute6 to 2001:4830:1600:3b::2 (2001:4830:1600:3b::2) from 2001:559:800c:1005:da2:6e15:8afd:76fb, 64 hops max, 12 byte packets
1 2001:559:800c:1005::1 0.236 ms 0.171 ms 0.154 ms
2 2001:559:0:84::1 0.513 ms 0.694 ms 0.448 ms
3 ae-19-0-ar04.capitolhghts.md.bad.comcast.net 0.734 ms 0.875 ms 0.866 ms
4 pos-5-7-0-0-cr01.ashburn.va.ibone.comcast.net 4.261 ms
pos-5-5-0-0-cr01.ashburn.va.ibone.comcast.net 6.240 ms
pos-5-3-0-0-cr01.ashburn.va.ibone.comcast.net 3.217 ms
5 *
pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net 3.699 ms 3.390 ms
6 2001:559::326 2.462 ms 2.383 ms 2.445 ms
7 if-ae8.1508.tcore2.lvw-losangeles.ipv6.as6453.net 122.699 ms 78.642 ms 87.403 ms
8 if-ae2.2.tcore1.lvw-losangeles.ipv6.as6453.net 112.629 ms
if-9-0-0.14.mcore3.laa-losangeles.ipv6.as6453.net 78.776 ms 79.002 ms
9 pos4-0-0.mse2.sv1-santaclara.ipv6.as6453.net 95.135 ms 94.792 ms
if-10-0-0.12.mcore3.laa-losangeles.ipv6.as6453.net 82.782 ms
10 if-2-14.mse1.sv1-santaclara.ipv6.as6453.net 90.863 ms 91.578 ms 94.991 ms
11 2001:5a0:2400::1e 99.262 ms 93.483 ms
if-2-14.mse1.sv1-santaclara.ipv6.as6453.net 89.469 ms
12 bbr01-v442.lsan01.occaid.net 109.294 ms
2001:5a0:2400::1e 97.966 ms 102.619 ms
13 bbr01-p1-2.dlls01.occaid.net 103.772 ms
bbr01-v442.lsan01.occaid.net 115.556 ms 113.422 ms
14 bbr01-p1-0.atln01.occaid.net 106.508 ms 98.197 ms 99.149 ms
15 bbr01-g0-1.asbn01.occaid.net 95.134 ms 98.948 ms 94.130 ms
16 bbr01-g0-1.asbn01.occaid.net 103.847 ms 99.379 ms
equi6ix.dc.hotnic.net 95.526 ms
17 sixxs-asbnva-gw.customer.occaid.net 105.065 ms 94.856 ms
equi6ix.dc.hotnic.net 95.391 ms
18 sixxs-asbnva-gw.customer.occaid.net 102.587 ms
gw-60.qas-01.us.sixxs.net 104.700 ms 104.430 ms
19 cl-60.qas-01.us.sixxs.net 124.735 ms 131.397 ms 121.519 ms
|
|
ropeguruPremium
join:2001-01-25
Mechanicsville, VA | said by whfsdude:said by NetFixer:The »ipv6.speedtest.comcast.net site does not seem to work very well with IPv6 tunnels. I have even tried it using Comcast's 6to4 tunnel, and it did not even work with Comcast's own tunnel. Sometimes the site start page would load, but the test never worked. The actual speed test would either never start or it would hang busy and never finish. If you don't have native IPv6, that test site appears to be useless.
More specifically OCCAID (his tunnel pop) doesn't peer directly w/Comcast and their TATA link is really congested. There are a couple more traceroutes that I sent to NetDog via IM. When I clear DNS and try again I get a different ip almost every time. Some of the IP's traceroutes work and some do not. However, the web page never loads even if I leave it for 20 minutes. I have done some packet captures where the initial tcp handshake goes through but when the http get is done by the browser the comcast server never replies.
Maybe a return path routing issue? |
|
whfsdudePremium
join:2003-04-05
Washington, DC Reviews:
·T-Mobile US
| said by ropeguru:Maybe a return path routing issue?
Have a Linux box with tracepath6? I'm guessing PMTUD issues. |
|
 owlynPremium,MVM
join:2004-06-05
Newtown, PA
·Comcast
| reply to NetFixer
said by NetFixer:said by NetDog:said by owlyn:Yes, had it backwards. 2001 on the WAN side, 2601 on the LAN side. I still couldn't get it to work right, so I set my router to 6to4 Tunnel and tried the readiness site, and it worked, so I changed it back to DHCP, and got the IPV6 addresses again, and now I'm fine. Readiness 10/10, speedtest 52 down/10.5 up (Blast).
What type of router do you have? Sounds like you had to reset your settings to clear your DHCPv6 info. A little odd me so I would like to look into this. Router Type and version would be great start. My guess would be a Netgear router. I have to reboot my WNR1000v2-VC about once a week because it loses IPv6 sync. The router's WAN and LAN, and attached devices still have valid looking IPv6 addresses, but they don't work anymore until I reboot the router, and it gets (and redistributes to its LAN devices) new IPv6 address assignments from Comcast. Yes, it is a Netgear WNDR3400. I've had this problem before, and switching it to tunnel and back again fixes it. Don't have to reboot, but still, it shouldn't be happening. My symptoms are the same as yours (IP6 addresses all look good, but IP6 doesn't work). |
|
|
|
 NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro
·Comcast Business..
 ·Vonage
·Cingular Wireless
·Comcast
2 edits | reply to NetDog
said by NetDog:said by NetFixer:My guess would be a Netgear router. I have to reboot my WNR1000v2-VC about once a week because it loses IPv6 sync. The router's WAN and LAN, and attached devices still have valid looking IPv6 addresses, but they don't work anymore until I reboot the router, and it gets (and redistributes to its LAN devices) new IPv6 address assignments from Comcast.
What version of OS do you have on the WNR1000v2-VC, I will start asking questions.. Here is the OpenWRT [KAMIKAZE (7.09)] OS version information:
Linux version 2.6.15 (chao.zhang@dni-l-sw01) (gcc version 3.4.4 (OpenWrt-2.0)) #199 Tue Apr 17 12:29:38 EDT 2012
Here is the Comcast/Netgear firmware information:
Hardware Version: WNR1000v2-VC
Firmware Version: V1.2.2.56NA
GUI Language Version: V1.0.0.71
EDIT:
If you are going to be bugging the Comcast/Netgear WNR1000v2-VC firmware writers, please also ask them to fix the bug that was introduced with Firmware Version: V1.2.2.56NA that prevents doing port forwarding for port 80 if Remote Management is enabled. It does not matter what port is used for Remote Management; if it is enabled, you can't do port forwarding for port 80 (DMZ also blocks inbound port 80 if Remote Management is enabled). There is also a long standing bug in all of the WNR1000v2-VC firmware versions that prevents UDP port 123 from being port forwarded as well (that also does not work with DMZ either).
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
When governments fear people, there is liberty. When the people fear the government, there is tyranny. |
|
NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast
| reply to owlyn
said by owlyn:Yes, it is a Netgear WNDR3400. I've had this problem before, and switching it to tunnel and back again fixes it. Don't have to reboot, but still, it shouldn't be happening. My symptoms are the same as yours (IP6 addresses all look good, but IP6 doesn't work).
Actually, I can simply disable IPv6, save that setting, and then reselect DHCP for the IPv6 connection type, and the IPv6 connectivity resumes. But if I do it that way, the router actually keeps the old IPv6 address assignment along with the new IPv6 address assignment, so I prefer a reboot which provides a clean start.
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
When governments fear people, there is liberty. When the people fear the government, there is tyranny. |
|
ropeguruPremium
join:2001-01-25
Mechanicsville, VA | reply to whfsdude
Have a linux box. Just need to get IPv6 up and running on it. Will try and do that tomorrow. |
|
ropeguruPremium
join:2001-01-25
Mechanicsville, VA | reply to whfsdude
said by whfsdude:said by ropeguru:Maybe a return path routing issue?
Have a Linux box with tracepath6? I'm guessing PMTUD issues. Here ya go:
tracepath6 -n 2001:558:1010:5:68:87:73:52
1?: [LOCALHOST] pmtu 1500
1: 2001:4830:1621:1::254 0.218ms
1: 2001:4830:1621:1::254 0.064ms
2: 2001:4830:1621:1::254 0.053ms pmtu 1480
2: 2001:4830:1600:3b::1 28.512ms
2: 2001:4830:1600:3b::1 28.653ms
3: 2001:4830:e6:7::2 27.411ms asymm 2
4: 2001:4830:e6:7::1 28.620ms asymm 3
5: 2001:504:0:2::6939:1 82.043ms
6: 2001:470:0:191::2 163.217ms asymm 16
7: 2001:5a0:600:500::1 130.622ms asymm 13
8: 2001:5a0:600:500::76 134.819ms asymm 14
9: 2001:558:0:f5c3::1 131.244ms asymm 15
10: 2001:558:0:f6ab::2 129.553ms asymm 18
11: no reply
12: no reply
13: no reply
14: no reply
15: no reply
16: no reply
17: no reply
18: no reply
19: no reply
20: no reply
21: no reply
22: no reply
23: no reply
24: no reply
25: no reply
26: no reply
27: no reply
28: no reply
29: no reply
30: no reply
31: no reply
Too many hops: pmtu 1480
Resume: pmtu 1480 |
|
 plencnerbPremium
join:2000-09-25
Elgin, IL
kudos:2 | reply to ropeguru
said by ropeguru:tracert -6 ipv6.speedtest.comcast.net
Tracing route to ipv6.speedtest.g.comcast.net [2001:558:1010:5:68:87:73:52]
Edit: However, ping works... (But it is a different IP.)
ping -6 ipv6.speedtest.comcast.net
Pinging ipv6.speedtest.g.comcast.net [2001:558:1030:8:69:252:23:68] with 32 bytes of data:
For what its worth, if I try a ping or a traceroute, I get the same IP, which is 2001:558:1030:8:69:252:23:68 (the same IP that you get when you do a ping).
I'm wondering what happens if you try to do a trace to the IP directly? Does that work?
Could it be a DNS issue? I would think that a ping and trace route to the same host name would return the same IP.
nslookup does not appear to work on an IPv6 IP (at least for me). I was going to try that and see what it would come back with, but it did not return a result.
--Brian
--
============================
--Brian Plencner
E-Mail: CoasterBrian72Cancer@gmail.com
Note: Kill Cancer to Reply via e-mail |
|
NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro Reviews:
·Comcast Business..
·Vonage
·Cingular Wireless
·Comcast
| said by plencnerb:Could it be a DNS issue? I would think that a ping and trace route to the same host name would return the same IP.
nslookup does not appear to work on an IPv6 IP (at least for me). I was going to try that and see what it would come back with, but it did not return a result.
--Brian
The nslookup utility is a bit long in the tooth. You need to get a newer DNS lookup tool for the 21st century. You can install the dig utility for Windows from the BIND 9.9.2-P1 Windows package at »www.isc.org/downloads
C:\>dig -t AAAA ipv6.speedtest.comcast.net
; <<>> DiG 9.9.2 <<>> -t AAAA ipv6.speedtest.comcast.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38612
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;ipv6.speedtest.comcast.net. IN AAAA
;; ANSWER SECTION:
ipv6.speedtest.comcast.net. 2241 IN CNAME ipv6.speedtest.g.comcast.net.
ipv6.speedtest.g.comcast.net. 30 IN AAAA 2001:558:1030:8:69:252:23:68
;; Query time: 93 msec
;; SERVER: 192.168.9.2#53(192.168.9.2)
;; WHEN: Wed Feb 20 21:36:19 2013
;; MSG SIZE rcvd: 114
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
When governments fear people, there is liberty. When the people fear the government, there is tyranny. |
|
ropeguruPremium
join:2001-01-25
Mechanicsville, VA | reply to plencnerb
Ping and traceroute. Both work for that IP but some other IP's I tend to get may or may not.
ping 2001:558:1030:8:69:252:23:68
Pinging 2001:558:1030:8:69:252:23:68 with 32 bytes of data:
Reply from 2001:558:1030:8:69:252:23:68: time=121ms
Reply from 2001:558:1030:8:69:252:23:68: time=118ms
Reply from 2001:558:1030:8:69:252:23:68: time=119ms
Reply from 2001:558:1030:8:69:252:23:68: time=117ms
Ping statistics for 2001:558:1030:8:69:252:23:68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 121ms, Average = 118ms
tracert 2001:558:1030:8:69:252:23:68
Tracing route to 2001:558:1030:8:69:252:23:68 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 2001:4830:xxx::254
2 28 ms 26 ms 27 ms gw-60.qas-01.us.sixxs.net [2001:4830:1600:3b::1]
3 28 ms 29 ms 25 ms sixxs-asbnva-gw.customer.occaid.net [2001:4830:e6:7::2]
4 28 ms 27 ms 27 ms sixxs-gw.hotnic.us.occaid.net [2001:4830:e6:7::1]
5 27 ms 27 ms 26 ms ibr01-ve96.asbn01.occaid.net [2001:504:0:2:0:3:71:1]
6 33 ms 33 ms 33 ms bbr01-p2-1.nwrk01.occaid.net [2001:4830:ff:f150::1]
7 39 ms 40 ms 41 ms tata.nwrk01.occaid.net [2001:4830:e2:a::2]
8 174 ms 123 ms 122 ms if-5-0-4.mcore4.NYY-NewYork.ipv6.as6453.net [2001:5a0:400:500::15]
9 124 ms 119 ms 120 ms if-ae5.5.tcore1.NTO-NewYork.ipv6.as6453.net [2001:5a0:400:200::e]
10 122 ms 126 ms 123 ms if-15-1-0.17.core3.NTO-NewYork.ipv6.as6453.net [2001:5a0:12:100::e]
11 133 ms 128 ms 122 ms 2001:5a0:a00:200::32
12 132 ms 130 ms 132 ms pos-1-12-0-0-cr01.newyork.ny.ibone.comcast.net [2001:558:0:f5b0::1]
13 119 ms 143 ms 119 ms he-0-0-0-0-cr01.350ecermak.il.ibone.comcast.net [2001:558:0:f620::2]
14 132 ms 128 ms 131 ms pos-0-15-0-0-ar01.roseville.mn.minn.comcast.net [2001:558:0:f794::2]
15 132 ms 128 ms 128 ms te-4-1-ur01.roseville.mn.minn.comcast.net [2001:558:30:18::1]
16 122 ms 119 ms 120 ms te-8-3-ur02.roseville.mn.minn.comcast.net [2001:558:30:17::2]
17 118 ms 121 ms 119 ms 2001:558:1030:8:69:252:23:68
Trace complete. |
|
 camperPremium
join:2010-03-21
Bethel, CT
·Comcast
| reply to camper
said by camper:
I can get to the »www.test-ipv6.comcast.net/ site, and I get two 10/10's. I cannot get to the Comcast IPv6 speedtest site, though. It just times out.
I wonder if Comcast is restricting their speedtest site to Comcast IPv6 only --- I am using a he.net tunnel for IPv6.
Just to complete this comment, I can now reach the Comcast IPv6 test site. The image is above. |
|
