Guest Dan Posted October 27, 2006 Report Posted October 27, 2006 First of all I'd like to pre-thank to anyone that will respond to this answer.Few weeks ago I downloaded Subspace Continumm the last version (0.39 I think) after maybe 2 years I wasn't in subspace, I noticed that from the start I had very high ping and very high packetloss(and always S2C) which I didn't have before, even thought I upgraded my connection to a 3 mb connection, I had no idea what causing it so I tried running few tests.The first test was Pinging the server from the CMD (I'll talk mainly of the server of 66.36.241.110, which is the Trench Wars server, but I get the high packetloss in almost all servers). So I pinged the server, and out of 50 hops, I got that the avg ping was around the 263, and out of 50 packets sent, not even 1 got lost, I tried logging into the game just after I finished this test, and the result was current ping of 310 avg and packetlostt S2C of 13.2%. That was the result of the Ping : Pinging 66.36.241.110 with 32 bytes of data:Reply from 66.36.241.110: bytes=32 time=244ms TTL=114Reply from 66.36.241.110: bytes=32 time=340ms TTL=114Reply from 66.36.241.110: bytes=32 time=443ms TTL=114Reply from 66.36.241.110: bytes=32 time=322ms TTL=114Reply from 66.36.241.110: bytes=32 time=251ms TTL=114Reply from 66.36.241.110: bytes=32 time=259ms TTL=114Reply from 66.36.241.110: bytes=32 time=271ms TTL=114Reply from 66.36.241.110: bytes=32 time=268ms TTL=114Reply from 66.36.241.110: bytes=32 time=264ms TTL=114Reply from 66.36.241.110: bytes=32 time=284ms TTL=114Reply from 66.36.241.110: bytes=32 time=260ms TTL=114Reply from 66.36.241.110: bytes=32 time=256ms TTL=114Reply from 66.36.241.110: bytes=32 time=253ms TTL=114Reply from 66.36.241.110: bytes=32 time=262ms TTL=114Reply from 66.36.241.110: bytes=32 time=256ms TTL=114Reply from 66.36.241.110: bytes=32 time=279ms TTL=114Reply from 66.36.241.110: bytes=32 time=261ms TTL=114Reply from 66.36.241.110: bytes=32 time=256ms TTL=114Reply from 66.36.241.110: bytes=32 time=262ms TTL=114Reply from 66.36.241.110: bytes=32 time=270ms TTL=114Reply from 66.36.241.110: bytes=32 time=256ms TTL=114Reply from 66.36.241.110: bytes=32 time=262ms TTL=114Reply from 66.36.241.110: bytes=32 time=260ms TTL=114Reply from 66.36.241.110: bytes=32 time=267ms TTL=114Reply from 66.36.241.110: bytes=32 time=262ms TTL=114Reply from 66.36.241.110: bytes=32 time=266ms TTL=114Reply from 66.36.241.110: bytes=32 time=262ms TTL=114Reply from 66.36.241.110: bytes=32 time=260ms TTL=114Reply from 66.36.241.110: bytes=32 time=247ms TTL=114Reply from 66.36.241.110: bytes=32 time=250ms TTL=114Reply from 66.36.241.110: bytes=32 time=257ms TTL=114Reply from 66.36.241.110: bytes=32 time=260ms TTL=114Reply from 66.36.241.110: bytes=32 time=271ms TTL=114Reply from 66.36.241.110: bytes=32 time=258ms TTL=114Reply from 66.36.241.110: bytes=32 time=250ms TTL=114Reply from 66.36.241.110: bytes=32 time=277ms TTL=114Reply from 66.36.241.110: bytes=32 time=262ms TTL=114Reply from 66.36.241.110: bytes=32 time=256ms TTL=114Reply from 66.36.241.110: bytes=32 time=256ms TTL=114Reply from 66.36.241.110: bytes=32 time=251ms TTL=114Reply from 66.36.241.110: bytes=32 time=244ms TTL=114Reply from 66.36.241.110: bytes=32 time=247ms TTL=114Reply from 66.36.241.110: bytes=32 time=233ms TTL=114Reply from 66.36.241.110: bytes=32 time=238ms TTL=114Reply from 66.36.241.110: bytes=32 time=251ms TTL=114Reply from 66.36.241.110: bytes=32 time=247ms TTL=114Reply from 66.36.241.110: bytes=32 time=241ms TTL=114Reply from 66.36.241.110: bytes=32 time=246ms TTL=114Reply from 66.36.241.110: bytes=32 time=248ms TTL=114Reply from 66.36.241.110: bytes=32 time=240ms TTL=114 Ping statistics for 66.36.241.110: Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 233ms, Maximum = 443ms, Average = 263ms The second test I've done was Tracert through the cmd to the server. The result was that on the 3rd hop, it saw nothing, so as on the 7th on 8th hope, on the 9th hop (the server itself) I got avg of around 250 ms, again I logged into the game, and ping of 320 avg and packetloss of 15% and again S2C.Here's the result of the tracert : Tracing route to sls-cb9p7.dca2.superb.net [66.36.241.110]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms (my own router) 2 99 ms 99 ms 95 ms lo0.lns104.pt.nv.net.il [212.143.208.144] 3 * * * Request timed out. 4 116 ms 114 ms 125 ms gi1-0.core2.pt.nv.net.il [212.143.10.2] 5 176 ms 175 ms 173 ms pos2-6.brdr1.lnd.nv.net.il [212.143.12.3] 6 188 ms 188 ms 184 ms 207.138.95.197 7 * * * Request timed out. 8 * * * Request timed out. 9 263 ms 254 ms 248 ms sls-cb9p7.dca2.superb.net [66.36.241.110] Trace complete. At this point I've contacted my ISP to see if they can find a problem, they did tracert of their own, and they also did tracert from another ISP, the results were same to mine, even a bit higher, no matter the ISP. At this point I got pretty desperate and decided to run one final test. I read on the lag manual on this site about a program called Sub-O-Tronic, used to find info about the routers, I used to this program again to trace the route to 66.36.241.110 (Trench Wars' server) and the result : <FONT FACE="Courier"><PRE>Hop IP Address Host Name Sent Recv RTT Av RTT Min RTT Max RTT % Loss 1 (My Router Adress) [unknown] 2401 2401 0ms 0ms 0ms 10ms 0%2 212.143.208.144 lo0.lns104.pt.nv.net.il 2401 2401 79ms 91ms 40ms 499ms 0%3 --- [No response] --- --- --- --- --- --- ---4 212.143.10.2 gi1-0.core2.pt.nv.net.il 2401 2401 97ms 90ms 41ms 486ms 0%5 212.143.12.3 pos2-6.brdr1.lnd.nv.net.il 2401 2399 171ms 163ms 113ms 506ms 1%6 207.138.95.197 [unknown] 2401 2400 170ms 180ms 121ms 1237ms 1%7 --- [No response] --- --- --- --- --- --- ---8 --- [No response] --- --- --- --- --- --- ---9 66.36.241.110 sls-cb9p7.dca2.superb.net 2400 2399 241ms 245ms 194ms 602ms 1%</PRE></FONT> As you can see from 2400 packets sent, only 2 pacets were lost on the way, and avg ping of 245 on the server itself. I logged again into the game : Ping avg of 310 ms, S2C: 14.3%. That's the results of all the 3 tests I've performed, I read in another post that another guy had some problem and you offered him few solutions so I tried them : I defrag my hardwares, didn't help. I don't download anything. There's another pc on the network, but when I've done the tests it was shut off, and most of the time it's off. I have no idea what is causing this, and I hope maybe you can find the problem.
AceSpades Posted October 27, 2006 Report Posted October 27, 2006 I can see by your ping times that there's something wrong with you superb.net jump. What ISP are you on? And how far away from the servers do you live?
Guest Dan Posted October 28, 2006 Report Posted October 28, 2006 I can see by your ping times that there's something wrong with you superb.net jump. What ISP are you on? And how far away from the servers do you live?I live in Israel and I'm using ISP that is called NetVision. However I have some new info : I tried logging on my sister's pc, she has a different ISP, on 1.5 mb connection and I suffered from no packetloss and much lower ping althought the time was around 5 pm CST. And I also tried to disconnect my router and connecting to the internet directly, I still suffered from high lag. And the last thing is that I logged into the game today at 6 am CST and I didn't suffer from any lag, ping or what so ever, so I suspect it might be the ISP, cause on those hours, the lines are empty, what do you think?
Incomplete Posted October 28, 2006 Report Posted October 28, 2006 It sounds like your ISP.I remember when it used to get busy on my ISP I used to lag in similar ways to you.
»SOS Posted October 28, 2006 Report Posted October 28, 2006 It could be the ISP or it could be the network card or it could be a faulty cable or some interfering software or an ongoing download. The logs show nothing wrong, so maybe something is treating Continuum's UDP packets and the trace's ICMP packets differently. Possibly the ISP. Does Continuum work OK from the other computer on the same connection?
Guest Dan Posted October 28, 2006 Report Posted October 28, 2006 It could be the ISP or it could be the network card or it could be a faulty cable or some interfering software or an ongoing download. The logs show nothing wrong, so maybe something is treating Continuum's UDP packets and the trace's ICMP packets differently. Possibly the ISP. Does Continuum work OK from the other computer on the same connection? Well no, on the other pc I had exactly same ping/packetloss problem like in this pc, that's why I thought it can't be a problem with my pc/network card. I don't know about a software, I don't download anything. I didn't understand even a thing from the "The logs show nothing wrong..." but it sounds like an ISP problem, is there anything they can do about it? will it help if I call yelling or switch ISP?
»SOS Posted October 28, 2006 Report Posted October 28, 2006 It does sound like an ISP problem. An UDP connection test might help. I'll attach a tester I made. It will test the packetloss between your computer and mine. To use it, you will need the .Net Framework 2.0 which you can get from Windows Update (custom mode, optional upgrades). Simply unzip it and run the program. It has usage instructions in it. You'll just have to press a key and let it run for a while. Let it run for around 500 packets and see what the reults are. You can also try different settings and see if the packetloss changes with bigger/smaller packets or when you sent them faster. Post the results for all tests you do here (the statistics line - pressing D (display stats) or X (exit) will display the info). Make sure to do at least 500 packets per test - this makes sure the accuracy is good.UdpTester.zip
Danvis Posted October 28, 2006 Report Posted October 28, 2006 Alright, first of all I must thank you all for trying to help me : I've done few tests and I'll be specific on each, next. All the tests were around 8 pm CST, kinda rush hour of traffic. First test was a regular test, I allowed 500 packets to be sent, each packet's size is 400. Here the results: S2C: 17.03% C2S: 0.2% Sent: 500 Received: 414 Remotely received: 499 Second test I incresed speed, Packets per second : 2. Still size of 400. Results :S2C: 16.67% C2S: 0.2% Sent: 505 Received: 420 Remotely received: 504 Third test I incresed size of packets to 800. Packets per second : 1. Results :S2C: 18.02% C2S: 0.39% Sent: 518 Received: 423 Remotely received: 516 Forth test I decresed size of packets to 200. Packets per second : 1. Results :S2C: 18.36% C2S: 0.2% Sent: 502 Received: 409 Remotely received: 501 I think it's enough results since in any case you see the S2C and the C2S are kinda the same, if you need me to do more tests and check different things let me know.And the million dollars question, does it show it's my ISP's problem?
»SOS Posted October 28, 2006 Report Posted October 28, 2006 The million dollar answer is... maybe It does show that *something* is treating UDP packets differently from the normal ping/trace packets - those showed almost no loss in your testing. It could be the ISP or it could be something else on the path to the server. I once had this problem myself for several months because some network in another country was behaving badly - nothing to do with my ISP. But since the UDP test requires special software to be running on the server, it cannot be done for the servers on the path to TW - to determine which one is misbehaving. I think the best option would be to let the ISP know that UDP (game) packets are dropping but not ICMP (ping & trace) packets. Not much you can do about this on your own. If the problem is in the ISP's network then changing ISPs might work, of course, if that is an option for you. Or maybe you can get a hold of some competent technician who can figure out what is causing this. It most likely (but not 100% surely) is the ISP since you get this problem on all servers (which are located in different networks) and even to me (I am in Eastern Europe).
Guest Guest Posted October 29, 2006 Report Posted October 29, 2006 I am also getting the same as you Dan, my S2C is high over 10.0%, i have contacted my ISP and they saidits not there Network which is causing this, they said its the Host/Game which is giving you high S2C :S
Danvis Posted October 29, 2006 Report Posted October 29, 2006 I am also getting the same as you Dan, my S2C is high over 10.0%, i have contacted my ISP and they saidits not there Network which is causing this, they said its the Host/Game which is giving you high S2C :S Where are you from?
Danvis Posted October 30, 2006 Report Posted October 30, 2006 United Kingdom, England Well I've spoken with my ISP, they told me they do see a packetloss between me and the server and that it will be fixed in a week, I hope it will help, call your ISP and tell them to tracert to the server to see if there's a packetloss, and download the program that SOS gave to see if there's a packetloss between you and him.
Incomplete Posted October 30, 2006 Report Posted October 30, 2006 I am also getting the same as you Dan, my S2C is high over 10.0%, i have contacted my ISP and they saidits not there Network which is causing this, they said its the Host/Game which is giving you high S2C :S Does it happen all the time? I mean when your ISP is busy and when there's hardly anyone else using it? If it doesn't happen all the time then it could just be where your ISP is busy
The Apache Posted October 30, 2006 Report Posted October 30, 2006 United Kingdom, England LOL. England, United Kingdom. dummy.
Recommended Posts