Galaxy lag issues

[Agent_21]

can i has the updated files? Sense my server is the best server in all of kaillera.

You have your version lol "AS payback you will get to keep your Emulinker X v1.1"

 

[Smasherx74]

You have your version lol "AS payback you will get to keep your Emulinker X v1.1"

i want 1.2

 

[Agent_21]

i want 1.2

And I want a million dollars.

 

[firo]

I'm sorry that some of you are experiencing lag issues. I have brought this up with the hosting company and they found no problems with the server, and this was when 90+ users were on when Godweapons went down.

The problem is not universal - I for one have never experienced any ping spikes or above my usual 11 or 15 or any spontaneous lag at the two houses I normally log on at, and I'm on wireless. When you ping the server, all that is happening is a few messages being sent back and forth from your computer to the server. There really isn't a reason why ping would be acting up for some people and not others. Somewhere along the way, from wherever people are to New York, the connection becomes inconsistent. That is a problem with the ISP or your home connection (router, card, configuration, etc), not the server, especially for the high pingers. Always do a ping test to New York and trace the server's ip if you have ping issues. The server is not being strained or overloaded. It is a server that is made for 150 people to be playing, and little more than 50 log on during peak hours. Tons of lag spikes with 4 players is common but more often than not, the player with the most is the source (causing the other players to lag as a result). A simple drop test would be able to confirm the source of the lag.

Playing over kaillera is unlike other online games since every single packet sent must arrive correctly for the game to continue. The protocol is sensitive to connections and even slight interruptions can cause problems.

All of the infrastructure on the server side has been the same since the fall of last year. The hosting, configuration, and netcode have not been touched. The java version was updated today by the server people which could possibly have an impact, but probably won't. If anyone has a hosting company they know is reliable, feel free to send me a pm, but as of now there aren't any outstanding issues that would warrant such a change.

For those not experiencing issues on other servers, remember that the route the connection takes to other servers is different than the route to galaxy. I'm sure that people don't log into servers such as SCD nearly as often as galaxy so it is tough to make the comparison.

 

[Agent_21]

I'm sorry that some of you are experiencing lag issues. I have brought this up with the hosting company and they found no problems with the server, and this was when 90+ users were on when Godweapons went down.

The problem is not universal - I for one have never experienced any ping spikes or above my usual 11 or 15 or any spontaneous lag at the two houses I normally log on at, and I'm on wireless. When you ping the server, all that is happening is a few messages being sent back and forth from your computer to the server. There really isn't a reason why ping would be acting up for some people and not others. Somewhere along the way, from wherever people are to New York, the connection becomes inconsistent. That is a problem with the ISP, not the server, especially for the high pingers. Always do a ping test to New York and trace the server's ip if you have ping issues. The server is not being strained or overloaded. It is a server that is made for 150 people to be playing, and little more than 50 log on during peak hours. Tons of lag spikes with 4 players is common but more often than not, the player with the most is the source (causing the other players to lag as a result). A simple drop test would be able to confirm the source of the lag.

Playing over kaillera is unlike other online games since every single packet sent must arrive correctly for the game to continue. The protocol is sensitive to connections and even slight interruptions can cause problems.

All of the infrastructure on the server side has been the same since the fall of last year. The hosting, configuration, and netcode have not been touched. The java version was updated today by the server people which could possibly have an impact, but probably won't. If anyone has a hosting company they know is reliable, feel free to send me a pm, but as of now there aren't any outstanding issues that would warrant such a change.

That confirmed most of my suspicion. I know for sure I haven' touched ANY netcode in the server so I don't understand how all of a sudden network issues just pop up out of nowhere.

 

[rawrimamonster]

Well I know the ping issue is bust (for me) because I ping fine to all areas of new york, so like you said it has to be a hinderence on our connections on the way TO the server. We should be listing our isp's to see if that's a global problem there. I'm not entirely sure on how everything with internet packet sending stuff works but it could be recent upgrades by certain ISP's creating a inconsistency in our connections. Like with comcast they added the speed booster to everything. When they did that I'm sure they upgraded to a different software.

I will state I never had issues before using windows 7 though, so that might be it. As windows 7 becomes more widespread that could account for the issues with the ping/lag/other inconsistencies. That would also explain while despite many of us having separate ISP's why we get the same lag/large ping issues.

 

[firo]

Rawrimamonster, would you be able to go into the command line and type:
tracert 69.90.34.245
and paste it here (right click, select all, control+c)?

Ignore the time outs, this will show you the time it takes to ping the server. You should compare it to your ping on galaxy and do it a few times.

 

[rawrimamonster]

tracing the route my ping takes? Lol, mmmk. Just typed command into run

1st attempt

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\USERS\ADMINI~1>tracert 69.90.34.245

Tracing route to 69-90-34-245.ny.atlasservers.com [69.90.34.245]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 7 ms 9 ms 9 ms 68.85.85.177
4 9 ms 9 ms 9 ms te-9-2-ur02.wayne.mi.michigan.comcast.net [68.87
.190.93]
5 8 ms 8 ms 9 ms te-0-4-0-7-ar01.taylor.mi.michigan.comcast.net [
68.87.190.89]
6 24 ms 25 ms 23 ms pos-2-8-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.90.105]
7 24 ms 23 ms 23 ms pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.26]
8 22 ms 23 ms 23 ms 192.205.37.41
9 29 ms 30 ms 30 ms cr2.wswdc.ip.att.net [12.122.84.82]
10 30 ms 30 ms 35 ms cr2.n54ny.ip.att.net [12.122.3.37]
11 30 ms 30 ms 30 ms gar1.nyzny.ip.att.net [12.122.130.125]
12 49 ms 49 ms 45 ms 12.118.100.58
13 * * * Request timed out.
14 * * * Request timed out.
15 48 ms 49 ms 46 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Trace complete.

2nd attempt


C:\USERS\ADMINI~1>tracert 69.90.34.245

Tracing route to 69-90-34-245.ny.atlasservers.com [69.90.34.245]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 9 ms 68.85.85.177
4 19 ms 9 ms 8 ms te-9-2-ur02.wayne.mi.michigan.comcast.net [68.87
.190.93]
5 11 ms 11 ms 11 ms te-0-4-0-7-ar01.taylor.mi.michigan.comcast.net [
68.87.190.89]
6 24 ms 26 ms 23 ms pos-2-8-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.90.105]
7 25 ms 22 ms 23 ms pos-0-0-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.26]
8 25 ms 23 ms 23 ms 192.205.37.41
9 29 ms 30 ms 40 ms cr2.wswdc.ip.att.net [12.122.84.82]
10 30 ms 28 ms 31 ms cr2.n54ny.ip.att.net [12.122.3.37]
11 28 ms 28 ms 28 ms gar1.nyzny.ip.att.net [12.122.130.125]
12 43 ms 42 ms 43 ms 12.118.100.58
13 * * * Request timed out.
14 * * * Request timed out.
15 45 ms 43 ms 44 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Trace complete.

C:\USERS\ADMINI~1>

I think the last time I did something like this, the route was the same. I haven't changed ISP's within the last 2-3 years either.

 

[firo]

Yeah rawrimamonster, looking at the server database, your average ping is 50 which is right in line with what the trace is indicating. If you are having problems at a particular time, it probably would be useful to do this trace again.

Not that this says much, but a google search on the connection that increases your latency the most (12.118.100.58)

Brings up this page as the first result:
http://mailman.nanog.org/pipermail/nanog/2008-June/001610.html
Which describes a case of latency increases with an ISP of AT&T, which seems to be on the route comcast is taking the connection.

 

[Agent_21]

Thank you for comfirming to the ppl who claims Galaxy64 lags that it isn't Galaxy64.

 

[NTA]

wish i had comcast
could use some better dl speeds darn at&t
ipwnagent

 

[firo]

Thank you for comfirming to the ppl who claims Galaxy64 lags that it isn't Galaxy64.

There's always a possibility that the problem is server-based, but of course it's always good to explore all the possible solutions.

 

[ballin4life]

I used to get 97 ping on galaxy but now I get 101, which has bumped me up 2 frames of delay. 9 frames isn't really worth playing imo

 

[DMoogle]

I used to get 97 ping on galaxy but now I get 101, which has bumped me up 2 frames of delay. 9 frames isn't really worth playing imo

Ping spoof?

 

[SuPeRbOoM]

so yesterday I noticed for about 2 minutes on galaxy that people were getting lower pings(including me), then 2 minutes later everyone shot up again =/

 

[rawrimamonster]

Well all I know is my ping was (for years) and is naturally 27-31 to newyork, and only shot up the first time once the bad lag hit galaxy. Maybe the host is having bandwidth issues they don't know about?

@ boom

Yeah I had my original ping for like 2 hours or so and then it shot into the 60's.

 

[firo]

I'd encourage everyone who is having ping problems to post their traces to the server here so we could look at them. The more information we have about the problem, the better.

 

[UnholyWeapon]

JUst play the game !!!!!!!!!!!!!!!!!!!!!!!!!!!! :-)

 

[MONSTEROUS]

JUst play the game !!!!!!!!!!!!!!!!!!!!!!!!!!!! :-)

kinda hard to when someone complains about a few lag spikes

 

[rawrimamonster]

kinda hard to when someone complains about a few lag spikes

Lol, some ppl staying 45 FPS constant and getting over 150 spikes in one match isnt a few. XD

 

[NixxxoN]

hey monsterous, i'm certainly sure that the /lagstat thing sometimes fails. But maybe its server related

 

[firo]

hey monsterous, i'm certainly sure that the /lagstat thing sometimes fails. But maybe its server related

The lagstat can fail if a player lags during a four player game, causing everyone to have lag spikes. Usually the player with the most spikes is the culprit, but it could always be someone else. To my knowledge the lag isn't caused by the server though.

 

[Frogles]

Tracing route to 69-90-34-245.ny.atlasservers.com [69.90.34.245]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 8 ms 9 ms 68.85.48.145
4 13 ms 13 ms 11 ms 68.85.222.94
5 25 ms 25 ms 23 ms pos-2-9-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.90.117]
6 25 ms 26 ms 25 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.142]
7 26 ms 26 ms 25 ms 192.205.37.45
8 32 ms 33 ms 32 ms cr2.wswdc.ip.att.net [12.122.84.82]
9 31 ms 31 ms 30 ms cr2.n54ny.ip.att.net [12.122.3.37]
10 31 ms 30 ms 31 ms gar1.nyzny.ip.att.net [12.122.130.125]
11 47 ms 71 ms 49 ms 12.118.100.58
12 * * * Request timed out.
13 * * * Request timed out.
14 54 ms 52 ms 54 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Trace complete.

 

[NixxxoN]

Traza a la dirección 69-90-34-245.ny.atlasservers.com [69.90.34.245]
sobre un máximo de 30 saltos:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * 42 ms 42 ms 192.168.153.1
3 42 ms 42 ms 42 ms 241.Red-81-46-34.staticIP.rima-tde.net [81.46.34
.241]
4 44 ms 199 ms 44 ms So-3-0-0-0-grtbcntb1.red.telefonica-wholesale.ne
t [84.16.9.245]
5 96 ms 78 ms 70 ms So5-3-0-0-grtparix3.red.telefonica-wholesale.net
[84.16.12.134]
6 151 ms 155 ms 152 ms Xe6-1-0-0-grtwaseq2.red.telefonica-wholesale.net
[213.140.36.118]
7 144 ms 140 ms 150 ms Xe2-1-0-0-grtwaseq5.red.telefonica-wholesale.net
[84.16.14.217]
8 153 ms 148 ms 153 ms 192.205.35.109
9 161 ms 161 ms 167 ms cr2.wswdc.ip.att.net [12.122.134.22]
10 150 ms 162 ms 155 ms cr2.n54ny.ip.att.net [12.122.3.37]
11 166 ms 161 ms 159 ms gar1.nyzny.ip.att.net [12.122.130.125]
12 158 ms 148 ms 149 ms 12.118.100.58
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
15 155 ms 149 ms 157 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Traza completa.

I wonder wtf happens between 1st and 2nd jump 42 ms ... >.>

 

[Frogles]

Tracing route to 69-90-34-245.ny.atlasservers.com [69.90.34.245]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 8 ms 9 ms 68.85.48.145
4 13 ms 13 ms 11 ms 68.85.222.94
5 25 ms 25 ms 23 ms pos-2-9-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.90.117]
6 25 ms 26 ms 25 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.142]
7 26 ms 26 ms 25 ms 192.205.37.45
8 32 ms 33 ms 32 ms cr2.wswdc.ip.att.net [12.122.84.82]
9 31 ms 31 ms 30 ms cr2.n54ny.ip.att.net [12.122.3.37]
10 31 ms 30 ms 31 ms gar1.nyzny.ip.att.net [12.122.130.125]
11 47 ms 71 ms 49 ms 12.118.100.58
12 * * * Request timed out.
13 * * * Request timed out.
14 54 ms 52 ms 54 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Trace complete.

My ping is usually normal around nighttime so I thought I'd do another one. TRACE 2:

Tracing route to 69-90-34-245.ny.atlasservers.com [69.90.34.245]
over a maximum of 30 hops:

1 2 ms 1 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 68.85.48.145
4 12 ms 11 ms 12 ms 68.85.222.94
5 26 ms 25 ms 23 ms pos-2-9-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.90.117]
6 26 ms 25 ms 26 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.86.142]
7 61 ms 31 ms 45 ms 192.205.37.45
8 31 ms 31 ms 30 ms cr2.wswdc.ip.att.net [12.122.84.82]
9 32 ms 30 ms 30 ms cr2.n54ny.ip.att.net [12.122.3.37]
10 31 ms 30 ms 30 ms gar1.nyzny.ip.att.net [12.122.130.125]
11 30 ms 30 ms 31 ms 12.118.100.58
12 * * * Request timed out.
13 * * * Request timed out.
14 31 ms 30 ms 31 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Trace complete.

 

[Ownasaurus]

Traza a la dirección 69-90-34-245.ny.atlasservers.com [69.90.34.245]
sobre un máximo de 30 saltos:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * 42 ms 42 ms 192.168.153.1
3 42 ms 42 ms 42 ms 241.Red-81-46-34.staticIP.rima-tde.net [81.46.34
.241]
4 44 ms 199 ms 44 ms So-3-0-0-0-grtbcntb1.red.telefonica-wholesale.ne
t [84.16.9.245]
5 96 ms 78 ms 70 ms So5-3-0-0-grtparix3.red.telefonica-wholesale.net
[84.16.12.134]
6 151 ms 155 ms 152 ms Xe6-1-0-0-grtwaseq2.red.telefonica-wholesale.net
[213.140.36.118]
7 144 ms 140 ms 150 ms Xe2-1-0-0-grtwaseq5.red.telefonica-wholesale.net
[84.16.14.217]
8 153 ms 148 ms 153 ms 192.205.35.109
9 161 ms 161 ms 167 ms cr2.wswdc.ip.att.net [12.122.134.22]
10 150 ms 162 ms 155 ms cr2.n54ny.ip.att.net [12.122.3.37]
11 166 ms 161 ms 159 ms gar1.nyzny.ip.att.net [12.122.130.125]
12 158 ms 148 ms 149 ms 12.118.100.58
13 * * * Tiempo de espera agotado para esta solicitud.
14 * * * Tiempo de espera agotado para esta solicitud.
15 155 ms 149 ms 157 ms 69-90-34-245.ny.atlasservers.com [69.90.34.245]


Traza completa.

I wonder wtf happens between 1st and 2nd jump 42 ms ... >.>

Yeah that 2nd hop is really high. Your ISP should check that out

 

[777sc1]

gerard


nada lag por favor

 

[Agent_21]

Cheap ****s blame us for your **** internet

 

[rawrimamonster]

Cheap ****s blame us for your **** internet

More like our ping routes to the server is disrupted/changed by something, I dont think its either fault of ours. But the majority wins in this situation, the server should at the very least move from where its hosted.

Or get a different host in general, all hosts will say there is nothing wrong on their end because there is simply no way forthem to detect a problem from their side. But the fault obviously lies somewhere to or before where its hosted.

 

[Agent_21]

More like our ping routes to the server is disrupted/changed by something, I dont think its either fault of ours. But the majority wins in this situation, the server should at the very least move from where its hosted.

Or get a different host in general, all hosts will say there is nothing wrong on their end because there is simply no way forthem to detect a problem from their side. But the fault obviously lies somewhere to or before where its hosted.

Oh well, it's different when we're told we suck and **** you know.

 

[Battlecow]

The Galaxy does deserve some respect. They provide a place for us to play, and although I couldn't say whether or not they're causing you lag, they've never caused me lag. It's not like they're making money off of it; the least you could do is be polite. NY is a good place for a server IMO, and there are servers on the west coast if you want to play on 'em.

 

[Korrupshen]

I don't know if this works for everybody, but to make Galaxy 64 lag less I recommend switching over to DMZ instead of Static Nat, and after that you should change your security to medium so less traffic can pass. Less traffic.....less lag, only ports that been fowarded can pass through the security. It worked for me and my ping shot down from a "30 to 121" ping range toa steady "21". I did this some while ago when I still played ssb64, hope this helps out someone.

 

[NovaSmash]

I don't know if this works for everybody, but to make Galaxy 64 lag less I recommend switching over to DMZ instead of Static Nat, and after that you should change your security to medium so less traffic can pass. Less traffic.....less lag, only ports that been fowarded can pass through the security. It worked for me and my ping shot down from a "30 to 121" ping range toa steady "21". I did this some while ago when I still played ssb64, hope this helps out someone.

how do u do this

 

[Korrupshen]

how do u do this

If don't have a DMZ option in your configuration or a router "YOU CAN'T DO THIS"

I'm not responsible for what's done to your router. You taking the risk is not my responsibility


1. You need to find out your Default Gateway ip or DNS Servers ip, my Gateway is 96.250.180.1 and my DNS Server ip 192.168.1.1. Your DNS might be the same as mine but to make sure, open up your command prompt. To do this proceed to the following instructions to your OS

Vista/Windows 7: In the search program and files box type in "cmd" [without quotes]
XP: Click run and type in "cmd.exe" [without quotes]


2. Once you type it in click enter and you should get a box like this

3. Next thing your gonna do is type in "ipconfig/all" and whole bunch of stuff with pop up, but you'll only need one either one of the ips.

4. Choose either the DNS Server ip, mines is "192.168.1.1" or the Default Gateway ip "96.250.180.1" then open up your browser and type it in your address bar. [Remember use your ips not mine, unless we have the same DNS Server]

5. Click enter and you should get a page where you configure your router settings. This is mine, I blacked out some of the parts cuz I didn't know if they we're important or not. [Take note that every Router configuration page is different]

6. Go to firewall settings and you might get a pop asking for a password and username. The password and name by default is admin. If you don't know the password there is a program called RouterPassView which recovers the lost password. It supports a limited number of router models. The password can also be reset if you push a button on the back of your router. [I am not responsible for actions you take upon your router and will not accept any charges lol]

http://www.nirsoft.net/utils/router_password_recovery.html

7. After you login, they'll send you directly to the firewall settings. This how it looks like on mine. For some reason when I change this I can't get online on my ps3. I guess I gotta open the ports for it since my NAT is strict.

9. Next click on DMZ Host and it might tell you something like "Any changes made in this section may affect your device's performance and configuration" and that "Do you want to proceed ?"
Click "yes"

10. Next they'll ask you which device you want to enable it on. The device I'm using is Andrew-PC lol my name :3 click "enable" and it'll restart your router. Sometimes the router doesn't restart properly and you'll get a problem loading page error so when this happens turn off the router and turn it back on.

[Remember not everyone has the same router config page mines is different I just gave you the idea of whats suppose to be done if you we're trying to enable DMZ and decrease the lag, and again I'm not responsible for what's done to your router. You taking the risk is not my responsibility]

This **** took forever to type lol

 

[NixxxoN]

wtf? Am I wrong or this is supposed to work only on certain routers and ISP's...
edit: I can't see how this would make decrease your ping, unless you have some garbage on your pc that takes connection and makes it unstable

 

[Korrupshen]

wtf? Am I wrong or this is supposed to work only on certain routers and ISP's...
edit: I can't see how this would make decrease your ping, unless you have some garbage on your pc that takes connection and makes it unstable

**** I forgot to mention not all routers have DMZ so if you don't have it your screwed. *Goes to edit post*

EDIT: Its suppose to restrict firewall traffic, traffic increases ping. The DMZ Host setting allows one local user to be exposed to the Internet to use a special-purpose service such as Internet gaming or Video-conferencing. That's why I enable DMZ host cuz back then I had a hard time connecting to Galaxy 64 but now I can with DMZ enabled. Even with DMZ enabled I had horrible lag spike with a extremely low ping. So I checked my firewall and set it to medium to restrict some of the traffic giving me hardly no lag at all. My computer specs are WAY beyond the minimal and recommended requirements for PRJ64K. Plus I always play Project64k with nothing runnning in my background.

I can play any pc game on my computer with the exception of Crysis and some games of Dolphin. Project 64k was the only thing I ever had to configure **** for. So if anything gonna be called garbage around here it ain't gonna be my computer, it ain't be my internet provider, it ain't gonna be Galaxy 64, its that Kaillera **** with its dirty *** coding that someone needs to pick up and update

 

[rawrimamonster]

wtf? Am I wrong or this is supposed to work only on certain routers and ISP's...
edit: I can't see how this would make decrease your ping, unless you have some garbage on your pc that takes connection and makes it unstable

From my experience it wont do jack squat for your ping, I always have all of the proper ports forwarded and it does nothing for me. Though I myself do not LAG on galaxy (except for the rare occasions, which is my isp's fault im 100% sure of this) I still have a jacked up ping, but the reason for this is already known.

 

[Korrupshen]

From my experience it wont do jack squat for your ping

I starting to feel like I typed that **** for no reason

 

[Battlecow]

erm... It was very well done? A professional piece of web-advice fo sho. You're an inspiration to us all.

 

[Korrupshen]

erm... It was very well done? A professional piece of web-advice fo sho. You're an inspiration to us all.

Sarcasm ?