Page 1 of 2
Posted: Tue Feb 10, 2009 1:55 am
by Kyosuke Aoki
For some reason I lag like crazy on Planet with around 100-1000+ ms of latency, and 0-80% packet loss randomly. Sometimes I can play with no lag, sometimes I teleport around randomly. If I try another server, like GPZ, my network card soon crashes and doesn't respond to anything but a hard restart. Can anyone help with this?
I live in California, so Planet shouldn't lag at all, and I have broadband (3 Mbps down, 1.5 Mbps up) so bandwidth should not be an issue either.
Thanks!
Posted: Tue Feb 10, 2009 3:30 am
by FreeBeer
run a tracert to planet and gpz and post the results, please.
Posted: Tue Feb 10, 2009 4:30 am
by Kyosuke Aoki
Planet
Code: Select all
>tracert planet.dras.us
Tracing route to planet.dras.us [70.86.91.82]
over a maximum of 30 hops:
1 2 ms 2 ms 1 ms 192.168.1.254
2 20 ms 21 ms 26 ms xx-x-xx-x.lightspeed.sntcca.sbcglobal.net [xx.x.
xx.x]
3 * * * Request timed out.
4 23 ms 24 ms 23 ms 71.145.0.12
5 24 ms 25 ms 27 ms 71.145.0.4
6 23 ms 22 ms 23 ms 151.164.43.214
7 24 ms 22 ms 24 ms ex2-p14-0.eqsjca.sbcglobal.net [151.164.95.214]
8 22 ms 22 ms 23 ms asn3356-level3.eqsjca.sbcglobal.net [151.164.251
.246]
9 36 ms 33 ms 35 ms vlan99.csw4.SanJose1.Level3.net [4.68.18.254]
10 33 ms 34 ms 35 ms ae-93-93.ebr3.SanJose1.Level3.net [4.69.134.237]
11 34 ms 35 ms 33 ms ae-2.ebr3.LosAngeles1.Level3.net [4.69.132.10]
12 33 ms 33 ms 35 ms ae-93-93.csw4.LosAngeles1.Level3.net [4.69.137.4
6]
13 49 ms 35 ms 33 ms ae-92-92.ebr2.LosAngeles1.Level3.net [4.69.137.2
9]
14 62 ms 70 ms 71 ms ae-3.ebr3.Dallas1.Level3.net [4.69.132.78]
15 77 ms 67 ms 69 ms ae-73-73.csw2.Dallas1.Level3.net [4.69.136.158]
16 63 ms 66 ms 61 ms ae-24-79.car4.Dallas1.Level3.net [4.68.19.70]
17 64 ms 64 ms * THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]
18 112 ms 209 ms 201 ms te9-2.dsr02.dllstx3.theplanet.com [70.87.253.30]
19 62 ms 64 ms 67 ms po32.dsr02.dllstx5.theplanet.com [70.85.127.110]
20 66 ms 65 ms 67 ms 1e.fe.5746.static.theplanet.com [70.87.254.30]
21 158 ms 165 ms 164 ms planet.dras.us [70.86.91.82]
Trace complete.
GPZ
Code: Select all
>tracert server.german-borg.de
Tracing route to server.german-borg.de [84.243.253.92]
over a maximum of 30 hops:
1 1 ms * 1 ms 192.168.1.254
2 29 ms 27 ms 20 ms xx-x-xx-x.lightspeed.sntcca.sbcglobal.net [xx.x.
xx.x]
3 * 33 ms 26 ms 71.145.12.206
4 * * * Request timed out.
5 * * * Request timed out.
6 23 ms 24 ms 24 ms 151.164.43.214
7 24 ms 23 ms 23 ms ex1-p10-0.eqsjca.sbcglobal.net [151.164.191.66]
8 23 ms 24 ms 23 ms asn6461-abovenet.eqsjca.sbcglobal.net [151.164.2
51.42]
9 31 ms * 23 ms so-1-0-0.mpr1.sjc2.us.above.net [64.125.30.174]
10 122 ms 111 ms 101 ms so-1-0-0.mpr1.lga5.above.net [64.125.26.230]
11 183 ms 184 ms 181 ms so-1-0-0.mpr1.ams1.nl.above.net [64.125.27.186]
12 181 ms 181 ms 214 ms k234.grafix.ams4.nl.above.net [82.98.253.68]
13 186 ms 183 ms 185 ms server.german-borg.de [84.243.253.92]
Trace complete.
Posted: Tue Feb 10, 2009 7:18 pm
by FreeBeer
To planet, it looks like there's two significant (relatively speaking) delays. That's probably the source of the difficulties and it's outside of your control. The good news is that these often disappear or correct themselves in a few days.
The GPZ numbers look normal. There's a single delay, which I interpret as the Atlantic Ocean jump. That's only to be expected.
Posted: Wed Feb 11, 2009 1:59 am
by Kyosuke Aoki
Any explanation as to why my network card locks up when on GPZ for extended periods of time?
Thankfully Planet only lags irregularly, and as you said, the lag has (sorta) disappeared.
Thanks for the help!
Posted: Wed Feb 11, 2009 3:04 am
by FreeBeer
Kyosuke Aoki wrote:QUOTE (Kyosuke Aoki @ Feb 10 2009, 09:59 PM) Any explanation as to why my network card locks up when on GPZ for extended periods of time?
I have no direct experience, but I suppose it could be an indication of hardware failure or a heat related issue. Luckily, network cards are cheap should you need to replace it.
Posted: Wed Feb 11, 2009 4:09 pm
by Grimmwolf_GB
Replace the network card with a new one. If it was wireless, use cabled instead.
I don't know your setup, but this should NOT happen:
1 ms * 1 ms 192.168.1.254
This is your router messing up! What kind of router is this? How old is it? Try a different one if you have access to one. (I just bought a Linksys WRT54GL and replaced the firmware with a Open source firmware and so far it works very well. But I only had it for about a week...)
Posted: Thu Feb 12, 2009 10:27 pm
by Kyosuke Aoki
I'm using a wireless card, but running a cable to my computer would go past the Ethernet specifications for cable distance. My router is a 3wire router/modem/cable combo. It usually doesn't have any issues, and has longer range than my Airlink AW430 DDWRT, but I don't see the point of linking up my Airlink router to another one.
Posted: Thu Feb 12, 2009 10:45 pm
by peet
You can always run "pathping server.german-borg.de" to collect some statistical network data. Your network card should not generate a * (timeout).
Posted: Fri Feb 13, 2009 12:07 am
by Kyosuke Aoki
Funny thing is, it only happens on GPZ, and my network card only locks up on GPZ.