Things you don't know about lag, and how to fix them.

[Felony]

Well, here is a few things most, if not all, of you guys wouldn't know about the lag in gunz.

ping is a good teller of lag but not in all cases. if you and someone have over 70 ping to eachother, obviously there is lag there. But, some of you have probably noticed that someone with 30 ping can feel like they have 130, and you need to lead them accordingly.
Well, im here to explain some of that and tell you what you can do to fix it.

Packet Queuing

packet queuing is when you have multiple computers in your household running off of 1 router.
when your computer cant handle all the information coming in at the same time, it makes the packets wait in a line. this causes you to have to wait longer for info. You cannot tell if someone has packet queuing going on, but ill give a link at the end of this post to find out if you have this going on at your home. packet queuing is caused by SLOW ROUTERS.

Network Congestion

network congestion is caused by the people in your neighborhood using the bandwidth alloted by the isp's node. This is similar to packet queuing but not just your household, its your whole block or more. This wil also make your packets wait in a line. think of it like your whole block connection to 1 big router. the link at the end will also detect this. you cannot fix this except by getting a new isp.

Tracerts

tracert stands for traceroute. A traceroute shows the time it takes from one place to another, kind of like ping, but it also displays the time between each "hop" in between.
here is an example, this is my traceroute to google.com

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\danny>tracert google.com

Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 10 ms 6 ms xx.xxx.xxx.x
3 14 ms 11 ms 7 ms ge-1-44-ur01.mchenry.il.chicago.comcast.net [68.
85.208.169]
4 11 ms 13 ms 13 ms te-3-1-ur02.algonquin.il.chicago.comcast.net [68
.87.230.25]
5 15 ms 11 ms 16 ms te-8-4-ur01.algonquin.il.chicago.comcast.net [68
.87.231.233]
6 12 ms 11 ms 13 ms po-10-ar01.area4.il.chicago.comcast.net [68.87.2
29.110]
7 12 ms 15 ms 11 ms te-3-1-ar01.chartford.ct.hartford.comcast.net [6
8.86.90.58]
8 13 ms 12 ms 11 ms pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.90.57]
9 14 ms 14 ms 13 ms xe-9-0-0.edge1.Chicago2.Level3.net [4.71.248.33]

10 17 ms 18 ms 17 ms ae-31-51.ebr1.Chicago1.Level3.net [4.68.101.30]

11 42 ms 40 ms 50 ms ae-2.ebr2.NewYork1.Level3.net [4.69.132.66]
12 52 ms 53 ms 54 ms ae-92-92.csw4.NewYork1.Level3.net [4.69.134.94]

13 42 ms 51 ms 40 ms ae-4-99.edge1.NewYork1.Level3.net [4.68.16.206]

14 44 ms 44 ms 44 ms GOOGLE-INC.edge1.NewYork1.Level3.net [4.71.172.8
6]
15 40 ms 41 ms 48 ms 216.239.43.146
16 48 ms 45 ms 46 ms 66.249.94.92
17 42 ms 39 ms 49 ms 66.249.94.50
18 43 ms 47 ms 40 ms eh-in-f99.google.com [72.14.207.99]

Trace complete.

This is VERY useful if your having packet loss or lagging really bad and want to find the reason why. here is how you can tell if your having issues in your household and u can fix them.

hop 1 <1 ms <1 ms <1 ms 192.168.0.1 this is to your router(if you have one) or to your modem if you dont have a router. this should always be <1 if its going to your router. if this is greater then 4 or 5, you might have faulty cables.

hop 2 10 ms 10 ms 6 ms xx.xxx.xxx.x if you have a router then this is to your modem, it should be pretty constant in ms, mine is a little off. if you see a huge jump, like
8ms 8ms 35ms then you have an issue, faulty cables and electromagnetic waves can cause this, move the modem away from anything running on electricty to fix it.
if you dont have a router then this hop goes to your blocks node, a real high lag time here can mean faulty cabling and youd need to call your isp to have them come replace them.

a traceroute is done by clicking start then run then typing cmd. when you get to the prompt type tracert google.com or someother address.

THE LINK!!!!!!!

this link here will tell you your upload and download speed.
after the test is done click on statistics and it will tell you if you are getting any packet queuing and also if your network is congested.

UC Santa CruZ NDT server

if any of you have questions just ask, ill be happy to help.

i hope some of you can fix some lag issues.

with no network congestion and no packet queuing i dont have to lead AT ALL on anyone under 70 ping, cool huh?

PEACE

[Mudkip]

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 292.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 379.75kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_10-beta

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 218.56 msec; the Packet size = 1460 Bytes; and
There were 8 packets retransmitted, 75 duplicate acks received, and 77 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 1.92%
S2C throughput test: Packet queuing detected: 14.08%
This connection is network limited 99.83% of the time.
Excessive packet loss is impacting your performance, check the auto-negotiate function on your local PC and network switch

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: ON

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [*******] but Client says [*******]

---------------------------

That's my statistics. I guess I has some packet queuing. ;<
I is from teh EU.
Got any tests with servers based in England? ;o

Btw, how do I fix the bit in red? lawl.

[Felony]

um u might want to remove where it says server says your ip.

anyway, run a tracert to somewhere like google.com

after u do right click and click select all then press ctrl and c, that will copy all the data. come make a post here and paste it and ill see if ican help.

[Precognition]

These are my statistics:

---------------------------------------------

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 167.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 824.00kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_12

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 231.9 msec; the Packet size = 1322 Bytes; and
There were 16 packets retransmitted, 86 duplicate acks received, and 94 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 6.99%
S2C throughput test: Packet queuing detected: 5.39%
This connection is receiver limited 2.1% of the time.
This connection is network limited 97.74% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [*********] but Client says [**********]

----------------------------------------

This the tracert

-----------------------------------------

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DesmondWong>tracert google.com

Tracing route to google.com [72.14.207.99]
over a maximum of 30 hops:

1 44 ms 24 ms 126 ms 10.32.44.1
2 128 ms 26 ms 43 ms at-3-3-0-1739.CORE-RTR2.NY325.verizon-gni.net [1
30.81.9.173]
3 60 ms 33 ms 151 ms 130.81.20.178
4 153 ms 31 ms 126 ms 0.so-4-3-0.XL4.NYC4.ALTER.NET [152.63.10.29]
5 129 ms 66 ms 217 ms 0.ge-7-0-0.BR3.NYC4.ALTER.NET [152.63.18.9]
6 26 ms 176 ms 151 ms 204.255.173.25
7 78 ms 29 ms 25 ms ewr-core-01.inet.qwest.net [205.171.17.61]
8 28 ms 29 ms 32 ms jfk-core-02.inet.qwest.net [67.14.5.94]
9 84 ms 45 ms 35 ms jfk-edge-20.inet.qwest.net [205.171.230.17]
10 50 ms 27 ms 39 ms 205.171.37.10
11 49 ms 50 ms 251 ms 72.14.233.113
12 278 ms 226 ms 127 ms 66.249.94.92
13 101 ms 76 ms 126 ms 72.14.236.134
14 128 ms 72 ms 154 ms eh-in-f99.google.com [72.14.207.99]

Trace complete.

-------------------------------------
I spike often when I play GunZ. I spike from 50-800 ping in clan wars. And I spike from 20-150 to my friend who lives 4 blocks away from me.

[Felony]

lol you have some modem issues there.

[Mudkip]

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

F:\*************\****>tracert BBC - Homepage

Tracing route to BBC - Homepage [212.58.251.195]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 14 ms 16 ms 9 ms 10.21.40.1
3 11 ms 19 ms 14 ms pc-62-30-254-97-du.blueyonder.co.uk [62.30.254.9
7]
4 9 ms 9 ms 7 ms pc-62-30-254-69-du.blueyonder.co.uk [62.30.254.6
9]
5 * * * Request timed out.
6 29 ms 29 ms 28 ms win-bb-a-ge-000-0.inet.ntl.com [213.105.172.161]

7 20 ms 22 ms 21 ms gfd-bb-b-so-100-0.inet.ntl.com [213.105.172.130]

8 * * * Request timed out.
9 20 ms 19 ms 21 ms 212.58.238.189
10 19 ms 19 ms 18 ms 212.58.238.149
11 23 ms 15 ms 24 ms 212.58.239.62
12 19 ms 17 ms 14 ms www-vip.telhc.bbc.co.uk [212.58.251.195]

Trace complete.

[Felony]

mudkip, run that tracert a few times and see if you have any "request timed out" in the first 2 hops. also see if it jumps relatively high.

[Felony]

precognition, i would get a new cable from your computer to the modem. your high times can also be caused by a VERY old modem. if your using an old one then you might want to look into getting a new one. 40 bucks well spent.

mudkip, if your getting request timed out on the later hops its because the networking of the isp, you cant fix it.

[Precognition]

i redid the tests. Apparently, something was slowing down my internet, but its gone now. But I still spike in Gunz. BTW, this spike started to happen after one of the patches this month. Before the patch, my ping in gunz to my nearby friends was always 10-25.
__________________________________
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 618.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 1.77Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_04

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 125.09 msec; the Packet size = 1322 Bytes; and
There were 5 packets retransmitted, 145 duplicate acks received, and 149 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 1.12%
S2C throughput test: Packet queuing detected: 3.18%
This connection is receiver limited 2.55% of the time.
This connection is network limited 97.27% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [*************] but Client says [*********]
_________________________________________________
heres the tracert
_________________________________________________


Tracing route to google.com [64.233.167.99]
over a maximum of 30 hops:

1 24 ms 24 ms 24 ms 10.32.44.1
2 24 ms 25 ms 24 ms at-3-3-0-1738.CORE-RTR1.NY325.verizon-gni.net [1
30.81.9.169]
3 25 ms 24 ms 24 ms 130.81.20.176
4 25 ms 25 ms 24 ms 0.so-4-3-0.XL3.NYC4.ALTER.NET [152.63.10.25]
5 37 ms 24 ms 24 ms 0.ge-4-2-0.BR3.NYC4.ALTER.NET [152.63.3.126]
6 24 ms 24 ms 25 ms 204.255.173.25
7 38 ms 32 ms 46 ms ewr-core-01.inet.qwest.net [205.171.17.61]
8 32 ms 32 ms 37 ms dcx-core-02.inet.qwest.net [67.14.32.117]
9 35 ms 38 ms 32 ms dcp-edge-01.inet.qwest.net [205.171.251.74]
10 37 ms 33 ms 41 ms 72.164.177.226
11 33 ms 33 ms 41 ms 209.85.130.18
12 50 ms 51 ms 58 ms 216.239.46.224
13 52 ms 53 ms 52 ms 72.14.238.90
14 63 ms 69 ms 64 ms 64.233.175.26
15 51 ms 59 ms 52 ms py-in-f99.google.com [64.233.167.99]

Trace complete.

[Felony]

24ms from your computer to the modem is kinda slow. you have an old modem? and if so, wut model/make?

[Felony]

network congestion, but you cant fix that.

[Slap]

Packet queuing detected

I got owned.

Too lazy to fix right now.

[Fishbowl]

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 388.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 719.05kb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_05

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 190.19 msec; the Packet size = 1460 Bytes; and
No packet loss was observed.
C2S throughput test: Packet queuing detected: 1.73%
S2C throughput test: Packet queuing detected: 5.51%
This connection is receiver limited 90.91% of the time.
Increasing the the client's receive buffer (17.0 KB) will improve performance
This connection is network limited 8.99% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF

Server 'nitro.ucsc.edu' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Packet size is preserved End-to-End
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [ipadressssss] but Client says [anotherone]

[Ella-May]

This seems like too much of a trouble. You could rather just look out the window and see if you can see the Eiffel tower or not.

[Traumatize]

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 147.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 1.42Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_06

------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 201.35 msec; the Packet size = 1452 Bytes; and
There were 12 packets retransmitted, 70 duplicate acks received, and 80 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 1.70%
S2C throughput test: Packet queuing detected: 3.18%
This connection is receiver limited 3.62% of the time.
This connection is network limited 96.22% of the time.

Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF




I have a couple questions

1) Theoretically would C2S or S2C give you "ghost lag" on GunZ?
2) Which number should I focus on reducing so other players don't have Ghost Lag, I am assuming C2S
3) What does Network is Limited to xx% mean?
4) What does Reciever limited to xx% mean?
5) I have 3 total computers hooked up to my network can I unplug like an ethernet cable and then the computer will be disconnected, to reduce how many are on my router?
6) My tracert numbers are all consistent every line, good thing right?