So Called Lag - Show Us Your Ping & Tracert

[SkankyMoe]

HELLO EVERYONE

THERE IS A GROUP OF PEOPLE THAT SEEM TO HAVE SOME LAG ISSUES PLAYING ON THE SERVER.
I'D LIKE TO ASK THOSE EXPERIENCING LAG OR NOT TO POST YOUR PING AND TRACERT RESULTS HERE PLEASE.
HERE'S MINE BELOW, OBVISOULY I DONT EXPERIENCE ANY LAG ISSUES, IM IN BRISBANE.
COMPARE YOUR RESULTS TO MINE, IF YOU HAVE ANYTHING HIGHER, LETS HAVE A LOOK.

OPEN A DOS COMMAND PROMPT AND COPY AND PASTE THE RED PARTS BELOW

G:\>ping 202.60.82.196

Pinging 202.60.82.196 with 32 bytes of data:

Reply from 202.60.82.196: bytes=32 time=36ms TTL=122
Reply from 202.60.82.196: bytes=32 time=36ms TTL=122
Reply from 202.60.82.196: bytes=32 time=36ms TTL=122
Reply from 202.60.82.196: bytes=32 time=36ms TTL=122

Ping statistics for 202.60.82.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 36ms, Average = 36ms

G:\>tracert 202.60.82.196

Tracing route to 202.60.82.196 over a maximum of 30 hops

1 1 ms <1 ms <1 ms http://www.routerlogin.com [192.168.1.1]
2 17 ms 17 ms 17 ms nexthop.qld.iinet.net.au [203.55.228.88]
3 17 ms 16 ms 16 ms gi1-1.bne-pipe-bdr2.iinet.net.au [203.215.8.12]
4 18 ms 17 ms 17 ms as24238-2.brisbane.pipenetworks.com [218.100.0.68]
5 35 ms 36 ms 35 ms xr1.syd.dedicatedservers.net.au [118.127.9.185]
6 36 ms 35 ms 34 ms 202.60.82.196

Trace complete.

 

[gemanix]

Not so sure this is a good way of measuring et performance. While it goes some way to proving basic network connectivity, it doesnt show what goes on when 20 players are firing all around you.
An interesting experiment would be to chart the pings while in-game and set up a hotkey to mark timestamps where lag appeared to happen.

fwiw my tracert/ping below.


C:\Users\Gem>tracert 202.60.82.196

Tracing route to 202.60.82.196 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 26 ms 26 ms 27 ms x.x.x.x
3 23 ms 23 ms 29 ms ge-0-0-3-201.cre1.nct.orcon.net.nz [121.98.9.65]
4 23 ms 23 ms 25 ms ge-0-3-0-0.cre1.sky.orcon.net.nz [121.98.9.10]
5 24 ms 26 ms 26 ms vocus1.ape.net.nz [192.203.154.123]
6 50 ms 50 ms 49 ms ip-96.192.31.114.VOCUS.net.au [114.31.192.96]
7 107 ms 49 ms 50 ms ge-0-3-0-130.bdr02.syd01.nsw.VOCUS.net.au [114.31.192.81]
8 49 ms 50 ms 49 ms as45425.syd01.nsw.VOCUS.net.au [114.31.193.54]
9 51 ms 49 ms 50 ms 202.60.82.196

Trace complete.

C:\Users\Gem>ping -t 202.60.82.196

Pinging 202.60.82.196 with 32 bytes of data:
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=49ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=49ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=49ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=49ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=46ms TTL=119
Reply from 202.60.82.196: bytes=32 time=48ms TTL=119
Reply from 202.60.82.196: bytes=32 time=47ms TTL=119

Ping statistics for 202.60.82.196:
Packets: Sent = 45, Received = 45, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 49ms, Average = 47ms
Control-C
^C

 

[Black Racoon]

ping on average is time=25ms | ttl= 116



1 192.168.0.1 unknown 0ms
2 58.160.16.1 unknown 16ms
3 58.160.23.254 unknown 0ms
4 172.18.241.33 unknown 16ms
5 203.45.53.241 Bundle-Ether11.woo9.Brisbane.telstra.net 16ms
6 203.50.44.9 Bundle-Ether2.woo-core1.Brisbane.telstra.net 16ms
7 203.50.50.40 TenGigabitEthernet7-2.cha30.Brisbane.telstra.net 16ms
8 202.60.82.196 unknown 16ms
9 114.31.195.38 as24238.bne01.qld.VOCUS.net.au 16ms
10 118.127.9.34 cr2.bne.dedicatedservers.net.au 16ms
11 118.127.9.185 xr1.syd.dedicatedservers.net.au 31ms
12 202.60.82.196 unknown 31ms

 

[Baker Street]

Pinging 202.60.82.196 with 32 bytes of data:

Reply from 202.60.82.196: bytes=32 time=27ms TTL=122
Reply from 202.60.82.196: bytes=32 time=27ms TTL=122
Reply from 202.60.82.196: bytes=32 time=28ms TTL=122
Reply from 202.60.82.196: bytes=32 time=28ms TTL=122

Ping statistics for 202.60.82.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

C:\>tracert 202.60.82.196

Tracing route to 202.60.82.196 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 15 ms 14 ms 16 ms bri-pow-que-lns2-lo-30.tpgi.com.au [202.7.162.157]
3 15 ms 16 ms 16 ms bri-nxg-alf-csw1-vlan-1.tpgi.com.au [220.245.180.193]
4 16 ms 15 ms 16 ms bri-nxg-alf-crt1-port-channel-1.tpgi.com.au [202.7.171.93]
5 27 ms 28 ms 27 ms syd-pow-cla-crt1-po8.tpgi.com.au [202.7.171.162]
6 28 ms 29 ms 27 ms as24238.sydney.pipenetworks.com [218.100.2.13]
7 29 ms 29 ms 29 ms 202.60.82.196

 

[morbit]

>tracert 202.60.82.196

Tracing route to 202.60.82.196 over a maximum of 30 hops


2 30 ms 30 ms 30 ms 172.18.113.141
3 269 ms 30 ms 30 ms 172.18.66.150
4 31 ms 31 ms 31 ms 172.18.239.161
5 31 ms 31 ms 30 ms Bundle-Ether11.ken39.Sydney.telstra.net [203.45.
17.25]
6 32 ms 31 ms 31 ms Bundle-Ether6.ken-core4.Sydney.telstra.net [203.
50.6.145]
7 31 ms 31 ms 31 ms TenGigabitEthernet7-1.ult2.Sydney.telstra.net [2
03.50.20.51]
8 30 ms 30 ms 31 ms as4826-nsw.lnk.telstra.net [165.228.170.90]
9 31 ms 31 ms 31 ms ge-0-0-2.bdr02.syd01.nsw.VOCUS.net.au [114.31.19
2.37]
10 32 ms 31 ms 32 ms as45425.syd01.nsw.VOCUS.net.au [114.31.193.54]
11 31 ms 31 ms 31 ms 202.60.82.196

Trace complete.

>ping 202.60.82.196

Pinging 202.60.82.196 with 32 bytes of data:
Reply from 202.60.82.196: bytes=32 time=32ms TTL=117
Reply from 202.60.82.196: bytes=32 time=31ms TTL=117
Reply from 202.60.82.196: bytes=32 time=30ms TTL=117
Reply from 202.60.82.196: bytes=32 time=30ms TTL=117

Ping statistics for 202.60.82.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 32ms, Average = 30ms

and with larger packet size

>ping 202.60.82.196 -l 512

Pinging 202.60.82.196 with 512 bytes of data:
Reply from 202.60.82.196: bytes=512 time=43ms TTL=117
Reply from 202.60.82.196: bytes=512 time=42ms TTL=117
Reply from 202.60.82.196: bytes=512 time=43ms TTL=117
Reply from 202.60.82.196: bytes=512 time=43ms TTL=117

Ping statistics for 202.60.82.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 43ms, Average = 42ms

>ping 202.60.82.196 -l 1024

Pinging 202.60.82.196 with 1024 bytes of data:
Reply from 202.60.82.196: bytes=1024 time=55ms TTL=117
Reply from 202.60.82.196: bytes=1024 time=56ms TTL=117
Reply from 202.60.82.196: bytes=1024 time=56ms TTL=117
Reply from 202.60.82.196: bytes=1024 time=56ms TTL=117

Ping statistics for 202.60.82.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 56ms, Average = 55ms

really best way would be to ping server for say 30 mins and see if there any packet loss or spikes in ping
ping 202.60.82.196 -l 100 -t

this will ping server with 100bytes until you stop it by pressing control+c

>ping 202.60.82.196 -l 100 -t
Ping statistics for 202.60.82.196:
Packets: Sent = 624, Received = 624, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 36ms, Average = 31ms
Control-C
^C

but hey im just making sure there is big wall of text for trigger lol ;-)

 

[the whole cake]

Normally there is absolutely no lag on the server. Ever.
There was one exception the other night. There was lag on the ISP of the server, altar.net:

tracepath -n 202.60.82.196
1:  11.-------          0.165ms pmtu 1500
1:  11.-------          1.224ms
1:  11.-------          0.829ms
2:  11.-------          0.815ms pmtu 1492
2:  CakesSecretIP     35.063ms asymm  3
3:  no reply
4:  202.37.244.221   53.495ms asymm  5
5:  202.50.232.77    52.897ms asymm  6
6:  202.50.232.37    52.951ms asymm  7
7:  122.56.127.42    76.344ms asymm  8
8:  202.50.232.242   77.601ms asymm  9
9:  no reply
10:  203.8.183.74     77.322ms asymm 12
11:  210.80.34.49     77.095ms asymm 13
12:  210.80.33.190    77.322ms asymm 14
13:  203.166.43.34   230.625ms asymm 12
14:  114.31.193.54   211.834ms asymm 10
15:  202.60.82.196   241.376ms reached
     Resume: pmtu 1492 hops 15 back 117

    nslookup 210.80.33.190
    Non-authoritative answer:
    190.33.80.210.in-addr.arpa   name = 0.so-3-0-0.GW8.SYD2.ALTER.NET.

    nslookup 203.166.43.34
    Non-authoritative answer:
    34.43.166.203.in-addr.arpa   name = vocus-syd-gw.customer.alter.net.

But that was a very rare occasion and it not the servers fault. Hey Skanky did u know ur avatar is a walking diddle?

 

[Riff_Raff]

there is nothing wrong with the server...its some of the clients isp,s.. ya going to lag some from nz and with low up and down bandwidth,with other clients as well,,thing is to play with pb off is stupid, reason is i see hacks everyday in oz server...lastat is right et is diein and cheating no pb servers dont help..if ya laggy then up ya isp speed if ya serous to want to play online games if not stop wingin and go play ps2..server admins should run a server and put in what is needed so clients play to server cfg
if clients dont like it tuff ..dont let clients with crap pc,s and band width dictate what they want...that way the server
would encurrage a better lot of players and with pb on would seperate the personal cfg,s ppl have to cheat and some cheat progs..I know its a clan server but really what sort of clan would encourage no pb and hacks
Players Get your pkt flow and settings correct to match the server and you will see less probs :)

Racoon You need to take control of your server not the clients

To finish i was inthe server when the driver ishue was resulved and pb was on..my fps was 90 my ping was 24..30
and all was well..sept for the kicks i was watching with others with pb violations.

my 2c
Riff :)

 

[blusky]

lot of players and with pb on would seperate the personal cfg,s ppl have to cheat and some cheat progs..I know its a clan server but really what sort of clan would encourage no pb and hacks

OZ don't encourage hacking, don't be silly - ALL the admins and moderators only show disgust towards hacking and exploiting. The fact that PB is off shows that BR listens to the MASSES. Furthermore, the players that are considered to have xxxxxsuper tweaked configsxxxxxxx play on GA(PB enabled servers) competitively, If one was banned for hacking the word would spread quickly.

lreason is i see hacks everyday in oz server

Like whom?

The only hacker that KEEPS coming back is Celine Dion - he/she is banned in about 2 minutes.

 

[Antagonist]

ping 202.60.82.196

Pinging 202.60.82.196 with 32 bytes of data:

Reply from 202.60.82.196: bytes=32 time=74ms TTL=119
Reply from 202.60.82.196: bytes=32 time=75ms TTL=119
Reply from 202.60.82.196: bytes=32 time=75ms TTL=119
Reply from 202.60.82.196: bytes=32 time=75ms TTL=119

Ping statistics for 202.60.82.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 75ms, Average = 74ms


tracert 202.60.82.196

Tracing route to 202.60.82.196 over a maximum of 30 hops

1 14 ms 32 ms 32 ms 192.168.1.1
2 17 ms 20 ms 19 ms lo1.l1-45sgt-7206-d.wa.amnet.net.au [203.161.65.
228]
3 21 ms 18 ms 20 ms ge1-20.cr01.wa.amcom.net.au [192.168.4.17]
4 19 ms 20 ms 19 ms ge1-1.br01.wa.amcom.net.au [203.161.64.5]
5 18 ms 19 ms 17 ms vocus.ix.waia.asn.au [198.32.212.55]
6 79 ms 79 ms 79 ms ge-0-0-1-60.bdr01.syd01.nsw.VOCUS.net.au [114.31
.192.50]
7 79 ms 78 ms 79 ms ge-0-0-2.bdr02.syd01.nsw.VOCUS.net.au [114.31.19
2.37]
8 75 ms 76 ms 74 ms as45425.syd01.nsw.VOCUS.net.au [114.31.193.54]
9 75 ms 75 ms 75 ms 202.60.82.196

Trace complete.

i dont really understand what all this means? can someone explain it simply?
and even if theres no one on the server im still 100 ping, why would it say 74? ID LOVE 74 PING!!!

 

[i0nwr1t3r]

ping 202.60.82.196

Pinging 202.60.82.196 with 32 bytes of data:

Reply from 202.60.82.196: bytes=32 time=20ms TTL=122
Reply from 202.60.82.196: bytes=32 time=19ms TTL=122
Reply from 202.60.82.196: bytes=32 time=20ms TTL=122
Reply from 202.60.82.196: bytes=32 time=26ms TTL=122

Ping statistics for 202.60.82.196:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 26ms, Average = 21ms

tracert 202.60.82.196

Tracing route to 202.60.82.196 over a maximum of 30 hops

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 20 ms 21 ms 20 ms 202.60.82.196

Trace complete.

I should point out that I connect to my ISP through a static IP from my modem/router & my ping looks good but my tracert looks like a "fail".

 

[the whole cake]

OK cake is going to give....
An impromptu lession to all the noobs about internet connections.
Nothing technical - just explaining it in noob terms so you can get the drift of what these nerds are talking about.

Its not good enough to just say your internet connection is good or bad. Why? Because there are two (count em: two) very important things to look at when judging an internet connection:

Throughput: How fast information can be sent through the pipe. (for example 50 bazillion gigs per second)
And:
Latency(lag, ping, etc): How long it takes for a signal to go from your computer to somewhere else, and back again. (for example: 20 seconds to reach mommas house and back)

Now, getting a kickass experience in ET or any game involves matching your ET settings to the throughput (speed) and latency (lag) between you and the server. How do you do this? Well first of all, you need to know a little bit about your connection. You want to find out how fast your connection is, and what the latency is (called lag, or ping).

When you know what your internet connections latency is, and how fast it goes, then you can match it to the server. Remember folks, traffic goes both ways - so pay attention to how fast you can upload as well as download

For example, my home DSL service has a latency of 60ms to the OZ ET server. I know this cos I pinged it myself. My speed to Australia was found out by doing a speed test but I forgot what it was.

Example Scenarios:
You have a fast connection but a high ping: You must tell your client to send packets at large intervals, but make them big packets.
You have a fast connection with low ping: You can tell your client to send frequent and big packets.
You have a slow connection with nice ping: Small packets but send em frequently.
You have a slow connection with a big ping: You are probably Debo.

Youll notice I havent mentioned anything about console commands. Thats because I think its more important to understand whats going on, instead of hearsay of magical console numbers that 'make it better'.
Please bug the moderators or admins for support channels for instructions about the exact commands, like rate and hunkmegs. I actually dont know what they are. To be honest Im half asleep. And Im out of Just Juice so Im cranky.

 

[Riff_Raff]

well im shocked...The whole Cake i applude you you no what its all about....with latency hunkmegs matching pkts of info to server..ect ect..i think really is that 80% of gamers i meen serious gamers no what its all about with how it all works ect..the rest are just ppl who download a free game and push keyboard letters and roll a mouse about the best they can with what they have ,,and then with no idea on whats making them ping bad or lag or ask hey whats this plug out pic meen
complain how bad a server is .The whole cake you prob agree that most gaming servers run straight off the telstra pipe
i know all isp or companys that sell bandwidth do and with the speed of the up and down will be no prob hosting 30 clients
on a et game

This is why its a client ishue....

cheers Riff

 

[the whole cake]

:) :) :) Yeap. Very very rarely is it a server issue. Racoon keeps a tidy shop.

 

[CHRONIC]

The problem with the OZ server may not be the server lagging, but its defiently something server side.

eg. hitboxes, they are bad
You dont hit things when you should, thus ppl complaing of lag

 

[the whole cake]

Yah. Like the ISP mebbe

 

[Antagonist]

bet it would run like a dream on ETpro or Jaymod/nq (the one with the same hitboxes and feel as etpro)
ETpub on every server has always been a laggy nightmare.

 

[Lestat]

well im shocked...The whole Cake i applude you you no what its all about....with latency hunkmegs matching pkts of info to server..ect ect..i think really is that 80% of gamers i meen serious gamers no what its all about with how it all works ect..the rest are just ppl who download a free game and push keyboard letters and roll a mouse about the best they can with what they have ,,and then with no idea on whats making them ping bad or lag or ask hey whats this plug out pic meen
complain how bad a server is .The whole cake you prob agree that most gaming servers run straight off the telstra pipe
i know all isp or companys that sell bandwidth do and with the speed of the up and down will be no prob hosting 30 clients
on a et game

This is why its a client ishue....

cheers Riff

latency has NOTHING to do with "hunkmegs" (a memory allocation setting) nor does it have anything to do with matching packets the two are not remotely connected.One has to do with system and the other network,(system,(Available resources) the other internet upstream.downstream) people say "i lag" yup so may you! but what type there are "two" Bandwidth lag.(connection interrupted) and FPS lag fps lag consists of you freeze momentary, or u may not be able to aim as well ... a slide show effect happens... this is fps .. not bandwidth.You must distinguish between the two before you can fix it.And i am sure if its either a: get better Net, B: get a better Video card, and if your not located around the data center...and do not have a good isp .. then bad luck on the bandwidth ISSUE

P.S. Riff... i am 37 and your what 40+ please learn to spell or use correcting software... it aint that hard eh.

 

[the whole cake]

Wow see that!!!! Lestat went beserk for no reason.
Hello Lestat: You'll notice we didnt akshually say hunkmegs were teh key here. Yes ur right about the FPS versus connectivity lag. Although it seems ur anger level was pretty high for such a trivial thing. Cake thinks teh thread was specifically focused on connectivity, hence cakes noob guide to connections.

its ok, we all make mistakes. just like when u wake up with fat lady in ur bed, u have to admit ur mistakes even if it means u get bitten. cos if u dont, then it gets more and more itchy and u have to go see the doctar anyways.

im hungry.

 

[Antagonist]

"and those wars on your dick aint ganna go away, Unless u start using tropical cream everydayyyyyyyyyyyy" - song from baseketball, you feel me

 

[Inglourious Basterd]

Wow see that!!!! Lestat went beserk for no reason.
Hello Lestat: You'll notice we didnt akshually say hunkmegs were teh key here. Yes ur right about the FPS versus connectivity lag. Although it seems ur anger level was pretty high for such a trivial thing. Cake thinks teh thread was specifically focused on connectivity, hence cakes noob guide to connections.

its ok, we all make mistakes. just like when u wake up with fat lady in ur bed, u have to admit ur mistakes even if it means u get bitten. cos if u dont, then it gets more and more itchy and u have to go see the doctar anyways.

im hungry.

AAHAAAHAAAHAAAHAAAA :lol: