Shock Posted April 28, 2007 Report Posted April 28, 2007 (edited) I've been experiencing some packetloss today. Tracing Zone: SSCC Metal Gear CTF IP Address: 209.59.175.210 Hop IP Address Host Name Loss(%) Min/Avg/Max Ping --- --------------- -------------------------------- ------- ---------------- 1 192.168.1.1 ******** 0.0 0 0 0 2 10.74.64.1 <unknown> 1.9 0 20 120 3 24.95.86.65 gig2-4-556.ptskoh1-ybr1.columbus 0.0 10 10 30 4 65.25.129.189 srp9-1.clmboh1-rtr1.columbus.rr. 3.8 10 20 60 5 65.25.129.98 srp12-0.clmboh1-rtr2.columbus.rr 0.0 10 20 50 6 65.25.128.138 pos14-0.clmboh1-rtr3.columbus.rr 1.9 10 20 40 7 65.25.128.229 son0-1-2.mtgmoh1-rtr0.columbus.r 0.0 10 20 70 8 4.78.216.13 te-3-2.car1.Cincinnati1.Level3.n 0.0 20 40 180 9 4.69.132.206 ae-5-5.ebr2.Chicago1.Level3.net 3.8 20 40 70 10 4.68.101.162 ae-21-56.car1.Chicago1.Level3.ne 98.0 30 30 30 11 4.71.182.14 WBS-CONNECT.car1.Chicago1.Level3 98.0 30 30 30 12 209.59.157.38 lw-core2-ge3.rtr.liquidweb.com 0.0 30 70 1000 13 209.59.157.54 lw-dc1-dist4-ge2.rtr.liquidweb.c 1.9 30 140 670 14 209.59.175.210 <unknown> 2.0 30 40 60 15 209.59.175.210 <unknown> 1.9 30 50 280 Cycles: 51 What's the problem and where does it start? Edited April 29, 2007 by Maverick Changed quote to code tags for easier reading.
rootbear75 Posted April 29, 2007 Report Posted April 29, 2007 well if you see the two 98%s on that table, that will tell you where the majority of it is happening.
Shock Posted April 29, 2007 Author Report Posted April 29, 2007 That's always there.. the other !@#$%^&* isn't.
Samapico Posted April 29, 2007 Report Posted April 29, 2007 Call Chicago and tell 'em to buy a new server nah seriously... this kind of things happen... actually i'm having a constant 10-30% C2S packetloss so... meh... (due to university's network slowing down non-essential ports)
Shock Posted April 29, 2007 Author Report Posted April 29, 2007 It's not that one. Those two 98%'s are always there, even on a good day. It's the other ones that are the problem. Btw, now you messed up my color tags. No I didn't! -Maverick
rootbear75 Posted April 30, 2007 Report Posted April 30, 2007 actually, now that i can easily read it, it looks like #12/13 on the list might be causing the problem. they have high ping, and the packet's TTL might expire if its too long.
Recommended Posts