Packet loss to Valve Maps 1 - Printable Version
+- SourceOP (http://forums.sourceop.com)
+-- Forum: SourceOP Server (http://forums.sourceop.com/SourceOP-Server-forum)
+--- Forum: Problems/Help (http://forums.sourceop.com/Problems-Help-forum)
+--- Thread: Packet loss to Valve Maps 1 (/Packet-loss-to-Valve-Maps-1-thread)
+- SourceOP (http://forums.sourceop.com)
+-- Forum: SourceOP Server (http://forums.sourceop.com/SourceOP-Server-forum)
+--- Forum: Problems/Help (http://forums.sourceop.com/Problems-Help-forum)
+--- Thread: Packet loss to Valve Maps 1 (/Packet-loss-to-Valve-Maps-1-thread)
Packet loss to Valve Maps 1 - Norbule - Nov 15, 2010
DF,
Just some additional information, ran some traceroutes again to the server to see if I could find the problem, it looks like a hop inside your datacenter's network at Softlayer may be the issue.
10 62 ms 140 ms 139 ms po6.dar01.sr01.dal01.networklayer.com [173.192.18.211]
10 101 ms 33 ms 34 ms po6.dar01.sr01.dal01.networklayer.com [173.192.18.211]
10 147 ms 223 ms 213 ms po6.dar01.sr01.dal01.networklayer.com [173.192.18.211]
10 119 ms 127 ms 34 ms po6.dar01.sr01.dal01.networklayer.com [173.192.18.211]
Additional note, it's pretty intermittent, I had to run 10 or so traceroutes to get those examples, other traces ran fine.
Packet loss to Valve Maps 1 - Norbule - Nov 16, 2010
DF,
Can you have Softlayer look at whatever equipment is at that IP address (173.192.18.211)? They're more likely to listen to a paying customer rather than myself. I've run external traceroutes and seen the same random increases in response times from that IP address and a continuous ping of that IP sees it shoot up from 30ms to 150-300ms intermittently. This just doesn't seem normal at all.
Packet loss to Valve Maps 1 - Drunken F00l - Nov 16, 2010
They'll give me the typical response "pings and tracerts are low priority so you cannot use them to locate the source of the issue." You're the only one with the issue anyways.
Have you at least tried reducing your rate to see if loss goes away? Yes, choke will increase.
I assume you're posting from the IP you play with?
The outbound trace looks good
Code:
traceroute to yourip 30 hops max, 40 byte packets
1 mpdedicated.com (174.37.110.65) 0.389 ms 0.510 ms 0.798 ms
2 po105.dar01.sr01.dal01.networklayer.com (66.228.118.220) 0.313 ms 0.434 ms 0.503 ms
3 ae6.bbr01.eq01.dal03.networklayer.com (173.192.18.210) 0.241 ms 0.244 ms 0.243 ms
4 be-10-404-pe01.1950stemmons.tx.ibone.comcast.net (75.149.228.33) 1.155 ms 1.155 ms 1.153 ms
5 pos-2-3-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.153) 1.152 ms 1.151 ms 1.149 ms
6 pos-0-12-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.158) 22.773 ms 22.634 ms 22.630 ms
7 so-7-0-0-0-ar01.b0atlanta.ga.atlanta.comcast.net (68.86.93.202) 22.360 ms 22.397 ms 22.404 ms
8 xe-0-0-0-0-sur01.n1alpharetta.ga.atlanta.comcast.net (68.85.108.230) 24.038 ms 24.087 ms 24.082 ms
9 xe-11-3-0-0-sur01.n2alpharetta.ga.atlanta.comcast.net (68.85.108.234) 24.580 ms 24.686 ms 24.675 ms
10 68.85.68.54 (68.85.68.54) 25.054 ms 25.070 ms 25.324 ms^C173.192.18.210 is likely the other side of 173.192.18.211, so it doesn't look like that's the problem.