Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Lag on SourceOP
#11

well that don't help much, i'm trying help the laggers on COD4 not lag anymore
Reply
#12

sorry... most people use google.

Go to command prompt and type in the following:

tracert anywebaddress.com or ip

There are also a few extra things that you can add to the string but for the most part you wont need them. (ie, max number of hops, timeout wait limit etc.)
Reply
#13

ok thaks i found the trace route, no how do you find packet loss?
Reply
#14

packet loss is generally reported using the ping command...

ping anywebaddress.com or ip

The results should show up generally along these lines:

Code:
Pinging [url]www.apple.com[/url] [17.254.0.91] with 32 bytes of data:

Reply from 17.254.0.91: Bytes=32 time=37ms TTL=46
Packet loss is reported in the results as a percentage. So if/when I ping I generally ping with 25 packets just to get a decent percentage.

As before, there are additional options on the ping command.

ping http://www.google.com -t would continually ping google until you interrupt the process.

ping http://www.google.com -n 7 would ping google 7 times.

ping http://www.google.com -l 1024 would ping google with packets 1024 bytes in size. Default is 32 if I remember right and 8192 is the max.

enjoy.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)