|
L3 Routing Problems?
|
| tholemu |
Posted on 07-01-2015 23:43
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
My latency jumping pretty high, over 200ms at times, and ran a trace from my laptop. Looks like once my ISP (charter) routes over to L3 in Texas, things get a bit crazy. Anyone else noticing a path similar to this? It gets real strange around hop 8, but look at the latency increase at hop 5.
Oh well. Guess I'll wait to play til it passes.
H:\>tracert -d 96.44.146.166
Tracing route to 96.44.146.166 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1 (wireless router)
2 * * * Request timed out. (cable modem)
3 11 ms 19 ms 12 ms 96.34.56.249 (charter)
4 18 ms 15 ms 23 ms 96.34.2.16 (charter)
5 * 1181 ms 1448 ms 4.71.221.41 (L3, Dallas)
6 * * 26 ms 4.69.145.145 (L3, Dallas)
7 26 ms 25 ms 25 ms 4.69.145.145 (L3, Dallas)
8 128 ms 128 ms 131 ms 77.67.71.221 (Neu Isenberg, Germany, AS3257 ) WTF?
9 118 ms 135 ms 137 ms 216.221.158.178 (Tinet, somewhere in US)
10 129 ms 131 ms 138 ms 96.44.146.166 (Dogz Iceworld/Funtimes)
Trace complete. |
| |
|
|
| tholemu |
Posted on 08-01-2015 09:15
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
Ah, much better. Looks like the server is hosted in space out of LA, rather than Dallas though. I used whois.domaintools.com for WHOIS info on the IPs.
H:\>tracert -d 96.44.146.166
Tracing route to 96.44.146.166 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 12 ms 11 ms 96.34.56.249
4 11 ms 13 ms 15 ms 96.34.2.16
5 * * * Request timed out.
6 24 ms 38 ms 24 ms 4.68.111.102 (L3, Dallas)
7 27 ms 24 ms 28 ms 154.54.6.53 (L3, Dallas)
8 25 ms 25 ms 24 ms 154.54.6.74 (L3, Dallas)
9 26 ms 28 ms 30 ms 38.122.58.58 (Cogent, LA)
10 34 ms 25 ms 31 ms 96.44.146.166 (Dogz, LA)
Trace complete. |
| |
|
|
| TigerOx |
Posted on 08-01-2015 19:35
|
Admin
Posts: 2280
Joined: 07/02/2008 13:29
|
Server is in Dallas. IPs are just registered to LA. |
| |
|
|
| tholemu |
Posted on 12-01-2015 22:24
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
I don't understand what is going on, but it's only the Dogz servers which are giving me problems. It's much worse at night, but there are issues during the day as well. Screenshot below shows the difference. Up until about a week ago I was getting consistent 20-30ms latency across all the Dogz servers.
http://cloud-4.st...F1CBB3E67/ |
| |
|
|
| TigerOx |
Posted on 12-01-2015 22:29
|
Admin
Posts: 2280
Joined: 07/02/2008 13:29
|
Try downloading WinMTR and posting the results of a 2 minute MTR test to one of our IPs.
I checked your return path and it does seem quite odd. If you post that MTR I will forward the info over to our provider.
Edited by TigerOx on 12-01-2015 22:37
|
| |
|
|
| tholemu |
Posted on 12-01-2015 22:41
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
It's something with L3. Copy that into notepad or wordpad for the easiest to read formatting.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 131 | 131 | 0 | 6 | 201 | 0 |
| No response from host - 100 | 27 | 0 | 0 | 0 | 0 | 0 |
|dtr01olvemo-tge-0-2-0-14.olve.mo.charter.com - 0 | 131 | 131 | 9 | 24 | 227 | 15 |
| bbr01olvemo-bue-5.olve.mo.charter.com - 0 | 131 | 131 | 10 | 29 | 228 | 25 |
| 7-2-30.ear1.Dallas1.Level3.net - 50 | 40 | 20 | 1191 | 1745 | 2918 | 2918 |
| ae-3-80.edge5.Dallas3.Level3.net - 22 | 71 | 56 | 25 | 42 | 241 | 34 |
| ae-3-80.edge5.Dallas3.Level3.net - 22 | 71 | 56 | 27 | 42 | 244 | 32 |
| ae13.dal33.ip4.gtt.net - 0 | 131 | 131 | 92 | 133 | 535 | 120 |
| db-transit-gw.ip4.gtt.net - 0 | 131 | 131 | 92 | 136 | 534 | 120 |
| nuke-96-166.dogzgaming.com - 0 | 131 | 131 | 93 | 129 | 535 | 116 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider |
| |
|
|
| tholemu |
Posted on 13-01-2015 09:31
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
Also, even when I am pinging ~15-20ms in the server, the traceroute reveals similar results. It's hard to say if it's how Charter is routing into L3 or how L3 is advertising back to Charter.
Thanks for your help. I've had people telling me that I am a bit choppy/jittery while playing, and the packet loss and such makes sense. I don't want to be that guy. |
| |
|
|
| terrowrist |
Posted on 13-01-2015 19:40
|
Fusioneer
Posts: 1277
Joined: 30/06/2011 01:13
|
Who is your ISP? Charter?
"Nobody really knows what they're doing. We're all just trying to figure out what makes us happy."
|
| |
|
|
| tholemu |
Posted on 13-01-2015 23:23
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
Yeah, Charter. I have ~110mb/5mb down/up connection. I've also noticed similar results when tethering my laptop through my phone, ATT 4G LTE, in an attempt to alleviate the issue. I wonder if it is something regional. When I was at work today I did a trace which goes through Eagan, MN and the excessive latency/packet loss to the L3 hop(s) was not there. |
| |
|
|
| TigerOx |
Posted on 14-01-2015 17:07
|
Admin
Posts: 2280
Joined: 07/02/2008 13:29
|
No loss and latency is good now. I will continue to monitor it.
Packet loss and increased latency at one hop is not an issue as long as it does not propagate to the destination. Some routes will drop icmp as it is a low priority packet.
 Code My traceroute [v0.85]
nuke (0.0.0.0) Wed Jan 14 17:06:57 2015
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. nuke-96-161.dogzgaming.com 0.0% 154 0.3 6.0 0.2 212.7 27.4
2. ip4.gtt.net 0.0% 154 0.3 1.1 0.2 28.0 2.8
3. as3356.ip4.gtt.net 1.3% 154 0.3 0.9 0.3 42.8 4.4
4. ae-4-3507.ear1.Dallas1.Level3.ne 98.7% 154 23908 24012 23908 24116 147.2
5. ae-4-3507.ear1.Dallas1.Level3.ne 98.0% 154 23824 23916 23824 24028 103.4
6. CHARTER-COM.edge2.Dallas1.Level3 0.0% 154 23.0 19.2 15.2 23.1 2.2
7. ???
8. ???
9. ???
10. ???
11. 96-35-61-97.dhcp.stls.mo.charter 0.0% 153 21.8 26.9 21.3 45.4 5.1
|
| |
|
|
| tholemu |
Posted on 14-01-2015 17:31
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
TigerOx wrote:
No loss and latency is good now. I will continue to monitor it.
Packet loss and increased latency at one hop is not an issue as long as it does not propagate to the destination. Some routes will drop icmp as it is a low priority packet.
Code My traceroute [v0.85]
nuke (0.0.0.0) Wed Jan 14 17:06:57 2015
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. nuke-96-161.dogzgaming.com 0.0% 154 0.3 6.0 0.2 212.7 27.4
2. ip4.gtt.net 0.0% 154 0.3 1.1 0.2 28.0 2.8
3. as3356.ip4.gtt.net 1.3% 154 0.3 0.9 0.3 42.8 4.4
4. ae-4-3507.ear1.Dallas1.Level3.ne 98.7% 154 23908 24012 23908 24116 147.2
5. ae-4-3507.ear1.Dallas1.Level3.ne 98.0% 154 23824 23916 23824 24028 103.4
6. CHARTER-COM.edge2.Dallas1.Level3 0.0% 154 23.0 19.2 15.2 23.1 2.2
7. ???
8. ???
9. ???
10. ???
11. 96-35-61-97.dhcp.stls.mo.charter 0.0% 153 21.8 26.9 21.3 45.4 5.1
I still tend to think those L3 hops showing high latency and loss are problematic though. I don't see the same type of problem when tracing from my work PC, which takes an entirely different route.
Can you do the same test to another destination and produce the same loss and high response times?
Code |------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.91.38.3 - 0 | 248 | 248 | 0 | 0 | 50 | 0 |
| 10.91.12.5 - 0 | 248 | 248 | 0 | 0 | 1 | 0 |
| 10.10.16.181 - 0 | 248 | 248 | 1 | 1 | 10 | 1 |
| 162.8.250.225 - 0 | 248 | 248 | 24 | 25 | 40 | 25 |
| 10.108.66.5 - 0 | 248 | 248 | 24 | 25 | 36 | 26 |
| 10.118.8.9 - 0 | 248 | 248 | 23 | 23 | 35 | 23 |
| 10.118.8.10 - 0 | 248 | 248 | 23 | 23 | 23 | 23 |
| 10.213.2.135 - 0 | 248 | 248 | 23 | 23 | 42 | 23 |
| 10.213.2.230 - 0 | 248 | 248 | 23 | 23 | 59 | 24 |
| 167.68.124.137 - 0 | 248 | 248 | 24 | 29 | 214 | 24 |
| 167.68.124.82 - 0 | 248 | 248 | 24 | 24 | 89 | 24 |
| hagg-01-ae0-994.mnpl.twtelecom.net - 0 | 248 | 248 | 24 | 25 | 161 | 24 |
| chi2-pr1-xe-0-3-0-0.us.twtelecom.net - 0 | 248 | 248 | 33 | 36 | 181 | 33 |
| eqx.10ge.ord.bboi.NET - 0 | 248 | 248 | 33 | 34 | 168 | 33 |
| nsh-t4-3-2200-chi-vl2200.bboi.net - 0 | 248 | 248 | 54 | 56 | 210 | 210 |
| dal-ten2-1-nsh-ten1-4.bboi.net - 0 | 248 | 248 | 57 | 57 | 80 | 57 |
| 8011-on-net-cust.bboi.net - 0 | 248 | 248 | 56 | 60 | 214 | 56 |
| nuke-96-166.dogzgaming.com - 0 | 248 | 248 | 55 | 56 | 122 | 56 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|
| |
|
|
| terrowrist |
Posted on 14-01-2015 19:10
|
Fusioneer
Posts: 1277
Joined: 30/06/2011 01:13
|
I will post my results later.
Maybe others could chime in.
"Nobody really knows what they're doing. We're all just trying to figure out what makes us happy."
|
| |
|
|
| TigerOx |
Posted on 14-01-2015 22:05
|
Admin
Posts: 2280
Joined: 07/02/2008 13:29
|
I still tend to think those L3 hops showing high latency and loss are problematic though. I don't see the same type of problem when tracing from my work PC, which takes an entirely different route.
Those L3 hops are not affecting your traffic. You can see by looking at the last entry on the MTR. This is the loss/latency values to reach our servers. Our reverse route shows no loss and pretty good latency to your computer. The route you take to our servers is controlled by your ISP. The route from us to you we can control and is optimal at the moment.
Can you do the same test to another destination and produce the same loss and high response times?
I will need the IP to run the test. |
| |
|
|
| tholemu |
Posted on 26-01-2015 18:48
|
Junior Member
Posts: 32
Joined: 27/12/2014 18:12
|
Looks like I may have figured out the culprit. I experience lag spikes when connecting using my internal wireless card, but no spikes when I connect directly to the switch using a cable. I then tried a USB WNIC and had no problems. Can't say for sure, but I suspect it may be related to how hot my laptop gets when I'm gaming, which could in turn affect the internal card. Grasping at straws, but at least I am quite sure it's been fixed.
Unless anyone who I have been playing with over the past couple days has seen the jittery movement from me... I'm not seeing the latency spikes though, so I assume it's all good. |
| |
|
Current Donations
