|
[ADSL2] packet lossi seem to be having some issues with packet loss as soon as connections leave my lan. below is a pathping to the diablo3 America server. ignore the at&t 96% loss, this is normal as they respond to pings with a low priority, thus causing this.
Tracing route to 12.129.209.68 over a maximum of 30 hops
0 FireFang [10.0.0.112]
1 RT-AC68U [10.0.0.1]
2 10.11.1.1
3 at-2-0-0-1711.ALT2-CORE-RTR2.verizon-gni.net [130.81.9.221]
4 so-1-0-0-0.ALT2-CORE-RTR1.verizon-gni.net [130.81.18.162]
5 so-7-0-2-0.RES-BB-RTR1.verizon-gni.net [130.81.20.164]
6 0.xe-5-3-0.BR1.IAD8.ALTER.NET [152.63.37.49]
7 192.205.36.141
8 cr2.wswdc.ip.att.net [12.122.81.250]
9 * cr1.cgcil.ip.att.net [12.122.18.21]
10 cr2.dvmco.ip.att.net [12.122.31.85]
11 cr1.slkut.ip.att.net [12.122.30.25]
12 cr2.la2ca.ip.att.net [12.122.30.30]
13 gar20.la2ca.ip.att.net [12.122.128.181]
14 12-122-254-234.attens.net [12.122.254.234]
15 206.16.68.46
16 12.129.199.178
17 12.129.209.68
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 FireFang [10.0.0.112]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% RT-AC68U [10.0.0.1]
1/ 100 = 1% |
2 24ms 4/ 100 = 4% 3/ 100 = 3% 10.11.1.1
0/ 100 = 0% |
3 24ms 3/ 100 = 3% 2/ 100 = 2% at-2-0-0-1711.ALT2-CORE-RTR2.verizon-gni.net [130.81.9.221]
0/ 100 = 0% |
4 24ms 1/ 100 = 1% 0/ 100 = 0% so-1-0-0-0.ALT2-CORE-RTR1.verizon-gni.net [130.81.18.162]
2/ 100 = 2% |
5 39ms 3/ 100 = 3% 0/ 100 = 0% so-7-0-2-0.RES-BB-RTR1.verizon-gni.net [130.81.20.164]
0/ 100 = 0% |
6 36ms 3/ 100 = 3% 0/ 100 = 0% 0.xe-5-3-0.BR1.IAD8.ALTER.NET [152.63.37.49]
0/ 100 = 0% |
7 40ms 3/ 100 = 3% 0/ 100 = 0% 192.205.36.141
1/ 100 = 1% |
8 --- 100/ 100 =100% 96/ 100 = 96% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
9 --- 100/ 100 =100% 96/ 100 = 96% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
10 --- 100/ 100 =100% 96/ 100 = 96% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
11 --- 100/ 100 =100% 96/ 100 = 96% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
12 --- 100/ 100 =100% 96/ 100 = 96% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
13 --- 100/ 100 =100% 96/ 100 = 96% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
14 --- 100/ 100 =100% 96/ 100 = 96% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
15 --- 100/ 100 =100% 96/ 100 = 96% 206.16.68.46
0/ 100 = 0% |
16 --- 100/ 100 =100% 96/ 100 = 96% 12.129.199.178
0/ 100 = 0% |
17 109ms 4/ 100 = 4% 0/ 100 = 0% 12.129.209.68
Trace complete.
i would like for someone to check if anything is overloaded or otherwise. playing games on 100ms ping doesn't work too well (for reference other games seem to be having the same general issue, and it's affecting my web browsing a bit too (beyond the usual youtube peering crap). |
|
|
NormanSI gave her time to steal my mind away MVM join:2001-02-14 San Jose, CA TP-Link TD-8616 Asus RT-AC66U B1 Netgear FR114P
|
I don't know what to say about the 4% packet loss. But I show 102 ms from the West Coast to the East coast on an ADSL2+ connection with interleave on: Tracing route to at-2-0-0-1711.ALT2-CORE-RTR2.verizon-gni.net [130.81.9.221]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Chihiro [192.168.102.1]
2 25 ms 25 ms 26 ms 173-228-7-1.dsl.static.sonic.net [173.228.7.1]
3 24 ms 23 ms 23 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 24 ms 23 ms 24 ms 0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
5 25 ms 25 ms 28 ms xe-1-0-6.ar1.pao1.us.nlayer.net [69.22.130.85]
6 24 ms 23 ms 80 ms ae0-110g.cr1.pao1.us.nlayer.net [69.22.153.18]
7 25 ms 24 ms 24 ms ae1-70g.cr1.sjc1.us.nlayer.net [69.22.143.165]
8 26 ms 32 ms 28 ms ae1-40g.ar2.sjc1.us.nlayer.net [69.22.143.118]
9 28 ms 26 ms 27 ms TenGigE0-2-2-0.GW3.SJC7.ALTER.NET [152.179.48.21]
10 102 ms 103 ms 102 ms at-2-0-0-1711.ALT2-CORE-RTR2.verizon-gni.net [130.81.9.221]
Trace complete.
To the servers in Los Angeles, California, not so slow: C:\util\dig>tracert 12.129.209.68
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 <1 ms <1 ms 1 ms Chihiro [192.168.102.1]
2 24 ms 24 ms 25 ms 173-228-7-1.dsl.static.sonic.net [173.228.7.1]
3 24 ms 24 ms 23 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 24 ms 23 ms 24 ms 0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
5 23 ms 24 ms 24 ms ae2.0.gw.equinix-sj.sonic.net [50.0.2.14]
6 46 ms 24 ms 24 ms sonicnet-customer.xo.com [216.156.84.101]
7 28 ms 130 ms 26 ms 192.205.37.189
8 39 ms 38 ms 39 ms cr2.sffca.ip.att.net [12.122.86.122]
9 40 ms 41 ms 36 ms cr1.la2ca.ip.att.net [12.122.3.122]
10 35 ms 35 ms 35 ms gar29.la2ca.ip.att.net [12.122.129.241]
11 38 ms 206 ms 207 ms 12.122.251.190
12 36 ms 36 ms 36 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
13 36 ms 36 ms 36 ms 12.129.209.68
Trace complete.
|
|
WiFiguruTo infinity... and beyond Premium Member join:2005-06-21 Seattle, WA |
to Demonfang
Not sure if it is related, but VZ had some major issues the other night here in LA. Looked like they ended up swapping IP for an OCx link. |
|
dslx_nick ISP Employee join:2011-12-24 Chatsworth, CA |
Hrmmm. Well, good news and bad news.
Good news: He's definitely not affected by the LA issue (he's out east in PA). In fact, I've got a fairly good idea what might be causing it.
Bad news: Appears to be errors modem-side. This typically indicates one of three things: bad modem, bad IW, or expected distortion due to distance.
If it's a bad modem, the usual fix is to, of course, replace the modem. Demonfang's requested a D-Link specifically, but our current stock is Comtrends, so have been holding off on that; it's been a week since I last asked the shipping guys about stock so let me go poke them again.
If it's bad IW... well, will need to get a local tech to fix that one, I'm afraid. If possible, could try connecting modem directly to NID and re-testing, see if packet loss goes away or if it's still present (to effectively confirm/deny whether it's IW).
If it's just due to distance... that's one of the things that Interleave is used to compensate for. Which leaves us with a pretty Catch-22: keep Fastpath (which has lower ping time, good for games) and packet loss (bad for games, and, well, everything else), or go Interleave (higher ping time, but more stable)? |
|
|
i doubt it's packet loss caused by distance, as indicated by the rco on the modem being at or under 20%. also doubt iw, as it's all brand new (for this line anyway). perhaps send out a comtrend as a test to see if that will resolve it (if no d-link units are available that is). |
|
dslx_nick ISP Employee join:2011-12-24 Chatsworth, CA |
Some good news on this - one of the shipping guys found a returned D-Link modem from a closed account which tested good! So sending that one out for you, we'll see if that clears up the packet loss. |
|
|
yayyyyy |
|
Demonfang |
to dslx_nick
got new modem, seems like less of an issue now, but wanted to check to see if there are still modem side errors showing up for you or not. |
|
dslx_nick ISP Employee join:2011-12-24 Chatsworth, CA |
Still monitoring from this end (but it's harder to 'prove a negative', so definitely let me know if you're seeing packet loss from your end). |
|
|
somehow i don't think it was a modem issue directly. it was better for a couple days, but now back to random packet loss. if you don't mind, since it didn't help, can i keep the old modem? i plan on transferring back to my new house within a couple of weeks, and am going to set up both lines i have going into my new router (yay for dual wan). i figure it would save shipping charges for dslx. |
|
dslx_nick ISP Employee join:2011-12-24 Chatsworth, CA |
If you're still getting packet loss after replacing the modem, that would suggest it wasn't the modem causing the issue. Of course, if it's an inside wiring issue, that will be a moot point if you're moving to a new house... regarding holding onto the modem, let me check with Shipping this upcoming week (we track all modem shipments by account, so that might get things tangled up if you're using a modem shipment for this account with a different account). |
|