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

[Goddess Varwin]

A lot of basic network stuff explained in the topic, but it's really nothing relevant to GunZ or lag itself, and 99% of the people playing GunZ wouldn't benefit at all. So I'll give you my own version.

Here are the primary causes for higher pings:
1) Location. This is it for most people who play the game. The closer you live to someone, the lower your ping to them will be. You can get a good feel for where someone is at after you've played a while and learn the pings.(I live in TX, I get 50-55 ping to both east and west coast, 95-105 to Europe, and 70~ to most Canadians.) There's nothing you can do to change or fix this besides moving.

2) Bandwidth being used by other sources. If you're downloading anything through BitTorrent, limewire, or just downloading any file in general, this will lag your game and give you 200+ pings to just about everyone. Some people have background processes running that may update/downloading stuff in the background and they won't realize it. Also note that if you are on a network and there are other people in your house, if they are downloading something, you will lag.

3) Dialup connections are terrible and not suited for GunZ. If you are on one, get a job.

If you are still getting lag for some reason and you've gone over all this, start at the very top and start cutting things off, one by one, then testing to see if your lag problem goes away. It will allow you to narrow the problem down and, at the very least, let you know just what is causing your lag. If it was me, I'd do it something like this:

-Turn off all other computers on my network/in my house. If this fixes it, it means that one of those comps had processes running, be it downloads or some kind of background application that was hogging bandwidth.

-Run a full ad-aware/anti-virus scan on your computer and clear off any viruses, trojans, or malware you may have.

-Use a program like EndItAll to shut down ALL background processes running on your comp. If this fixes it, obviously one of those processe was hogging bandwidth.

-Unplug your router and plug your internet directly into your computer. If this fixes it, buy a new router.

-At this point if your lag still exists, then it's either a problem with your network card(very unlikely but who knows?), your OS or some kind of registry change that's affecting your network traffic(if you suspect this, format your drive, reinstall a decent OS like Windows XP, VISTA AS A LAST RESORT BECAUSE ITS TERRIBLE ATM)

-If it's neither of those, then chances are, you're ISP is just plain awful, you have a bad/low speed broadband connection, or both. If this is the case, switch to a new ISP.

-If none of the above fixed your problem, then you're a liar or you messed up along the way, because nothing else could be the cause of your problem, provided you aren't living in the 3rd world. But for most US/Canadian/Europeans, this should do it. Even though Europe is known for having terrible internet service and a awful technology industry in general, but whatever.

There's your advice from someone who has a degree in computer science and works in network administration for a living.

[Felony]

Here are the primary causes for higher pings:
1) Location. This is it for most people who play the game. The closer you live to someone, the lower your ping to them will be. You can get a good feel for where someone is at after you've played a while and learn the pings.(I live in TX, I get 50-55 ping to both east and west coast, 95-105 to Europe, and 70~ to most Canadians.) There's nothing you can do to change or fix this besides moving.

Changing isp can help in some situations. I went from dsl with 50 ping to a friend to cable to 20 to him.

2) Bandwidth being used by other sources. If you're downloading anything through BitTorrent, limewire, or just downloading any file in general, this will lag your game and give you 200+ pings to just about everyone. Some people have background processes running that may update/downloading stuff in the background and they won't realize it. Also note that if you are on a network and there are other people in your house, if they are downloading something, you will lag.

only true if you have either: 1. low bandwitdh to begin with, gunz doesnt use too much bandwitdh, i monitored mine and it randomly jumped up to 70kbps at the highest. i can download stuff on bittorrent at 400kbps and run gunz fine on my 10mbps line. 2. have a crap router that cant keep up with all the connections, i had lag with my linksys wrt54g constantly while downloading or while other people were online. On my new dlink gaming router i have no problems EVER.

[lordcarbo]

So what does this mean:





WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 625.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 2.70Mb/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 = 181.96 msec; the Packet size = 1452 Bytes; and
No packet loss - but packets arrived out-of-order 0.16% of the time
C2S throughput test: Packet queuing detected: 1.06%
S2C throughput test: Packet queuing detected: 1.87%
This connection is receiver limited 89.03% of the time.
This connection is network limited 10.79% 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 [192.168.1.45]

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

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

C:\Documents and Settings\Owner>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 dslrouter [192.168.1.1]
2 23 ms 23 ms 23 ms 10.5.84.1
3 23 ms 23 ms 23 ms so-2-0-3-0.CORE-RTR1.NWRK.verizon-gni.net [130.8
1.7.149]
4 23 ms 23 ms 23 ms so-7-2-0-0.BB-RTR1.NWRK.verizon-gni.net [130.81.
20.160]
5 23 ms 23 ms 23 ms 0.so-5-0-0.XL1.EWR6.ALTER.NET [152.63.19.177]
6 26 ms 26 ms 25 ms 0.so-6-1-0.XL3.NYC4.ALTER.NET [152.63.16.194]
7 26 ms 26 ms 26 ms 0.ge-6-0-0.BR3.NYC4.ALTER.NET [152.63.18.5]
8 26 ms 26 ms 25 ms nyc-brdr-01.inet.qwest.net [63.146.26.209]
9 26 ms 26 ms 26 ms ewr-core-02.inet.qwest.net [205.171.17.69]
10 25 ms 26 ms 26 ms jfk-core-02.inet.qwest.net [67.14.5.94]
11 26 ms 26 ms 26 ms jfk-edge-20.inet.qwest.net [205.171.230.17]
12 27 ms 26 ms 27 ms 205.171.37.10
13 43 ms 40 ms 40 ms 72.14.233.113
14 42 ms 42 ms 41 ms 66.249.94.90
15 41 ms 42 ms 41 ms 66.249.94.72
16 57 ms 45 ms 42 ms eh-in-f99.google.com [72.14.207.99]

Trace complete.

[lblay]

on the link i cannot find the start button..

[Fail9000]

C:\Users\Dominic>tracert google.co.uk

Tracing route to google.co.uk [216.239.59.104]
over a maximum of 30 hops:

1 7 ms 7 ms 7 ms 10.156.192.1
2 11 ms 12 ms 10 ms nott-t2cam2-a-v604.inet.ntl.com []
3 11 ms 11 ms 11 ms nott-t3core-1a-ge-116-0.inet.ntl.com [195.182.17
4.229]
4 13 ms 13 ms 13 ms lee-bb-a-as0-0.inet.ntl.com [213.105.174.169]
5 17 ms 19 ms 18 ms pop-bb-b-as1-0.inet.ntl.com [62.253.185.238]
6 18 ms 19 ms 18 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
7 19 ms 20 ms 18 ms 212.250.14.138
8 19 ms 21 ms 19 ms 209.85.252.76
9 90 ms 90 ms 89 ms 64.233.175.213
10 100 ms 100 ms 98 ms 209.85.248.216
11 119 ms 114 ms 116 ms 216.239.48.69
12 119 ms 116 ms 116 ms 72.14.232.215
13 117 ms 116 ms 116 ms 216.239.59.104
___________________________

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

------ Client System Details ------
OS data: Name = Windows Vista, Architecture = x86, Version = 6.0
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
Information: throughput is limited by other network traffic.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 210.12 msec; the Packet size = 1392 Bytes; and
There were 8 packets retransmitted, 47 duplicate acks received, and 50 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 1.59%
S2C throughput test: Packet queuing detected: 11.67%
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: OFF


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 [192.168.2.4]

It always felt to me that everyone had a fake ping to me (everyone) including low pings because i had to lead them and i would get slashed from long distances even though i was 18 ping to someone.

When i get all hits on people constantly and i knew people should of died everyone is like "u missed loads" when my opponent and the spectaters are around 20 ping, it's just.... annoying. hmmm

[chaosdog]

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

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

------ 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 = 224.84 msec; the Packet size = 1452 Bytes; and
There were 33 packets retransmitted, 156 duplicate acks received, and 200 SACK blocks received
The connection was idle 0 seconds (0%) of the time
C2S throughput test: Packet queuing detected: 2.11%
S2C throughput test: Packet queuing detected: 1.10%
This connection is network limited 99.83% 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: 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]
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 [58.110.71.138] but Client says [192.168.0.12]

1 * * * Request timed out.
2 3 ms 2 ms 2 ms 10.1.1.1
3 35 ms 33 ms 34 ms sun12.ba.optusnet.com.au [198.142.129.20
4 33 ms 34 ms 34 ms sun4-vl420.gw.optusnet.com.au [211.31.13
5 32 ms 33 ms 33 ms sun1-ge14-0.gw.optusnet.com.au [198.142.

6 48 ms 46 ms 46 ms mas3-ge2-0-0-811.gw.optusnet.com.au [211
11]
7 202 ms 202 ms 202 ms 203.208.192.97
8 205 ms 206 ms 209 ms ge-4-0-0-0.laxow-dr2.ix.singtel.com [203
.34]
9 208 ms 204 ms 204 ms 203.208.169.58
10 205 ms 205 ms 205 ms 216.239.46.180
11 265 ms 206 ms 266 ms 216.239.43.125
12 269 ms 268 ms 268 ms 216.239.47.1
13 275 ms 268 ms 276 ms 216.239.47.1
14 285 ms 268 ms 287 ms 216.239.49.226
15 268 ms 268 ms 275 ms jc-in-f99.google.com [64.233.187.99]

ive tweaked my comp meaning well orginely plan was on 2mb now its upto 3 some sites sais upto 4.5mbps

you prob already know im aussie b4 the last gg update i used to have upto 100 150 pings lock now its 180+

[lblay]

varwin explained it a little better than you did and i have fought people with 30 ping and it felt like 130

[Juice]

TCP/Web100 Network Diagnostic Tool v5.4.12
click START to begin
Connected to: nitro.ucsc.edu -- Using IPv4 address
Another client is currently being served, your test will begin within 135 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 428.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 737.44kb/s
Your PC is connected to a Cable/DSL modem
Information: Other network traffic is congesting the link

click START to re-test
Connected to: nitro.ucsc.edu -- Using IPv4 address
Another client is currently being served, your test will begin within 45 seconds
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 416.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 4.99Mb/s
Your PC is connected to a Cable/DSL modem

click START to re-test



Nice




And gratz if you can fix this problem:

Pingbugs with ppl that i used to have 20 ping with.

Dutch and french ppl have mostly 75 ping to me now.

thats + 50 ping >>

[itzjasondd]

This is really nice

[Fail9000]

C2S throughput test: Packet queuing detected: 1.59%
S2C throughput test: Packet queuing detected: 11.67%

does this mean i have lagsheild? i tested again and i got 14%+ S2C packet queuing

[KlNETIC]

so much to read so little time

[lordcarbo]

chaosdog you should probably edit out your external IP address

[chaosdog]

Originally Posted by lordcarbo

chaosdog you should probably edit out your external IP address

na its all good many ppl got my ip not normal ppl blackhats ect im secured

[Slap]

Web100 reports the Round trip time = 483.3 msec; the Packet size = 1460 Bytes; and
No packet loss - but packets arrived out-of-order 3.54% of the time
C2S throughput test: Packet queuing detected: 2.42%
S2C throughput test: Packet queuing detected: 7.68%
This connection is receiver limited 86.31% of the time.
Increasing the the client's receive buffer (63.0 KB) will improve performance
This connection is network limited 13.53% of the time.

Packets arrive out of order ehhh?

How do I look Fel?

[Felony]

you seem to be pretty good,slap.

i also get the out of order thing at my other house, which oddly, seems to have a better connection to peers.