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

Lag on SourceOP
#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


Messages In This Thread
Lag on SourceOP - by speedily - Mar 21, 2008, 05:03 AM
Lag on SourceOP - by clem - Mar 21, 2008, 10:10 AM
Lag on SourceOP - by Drunken F00l - Mar 21, 2008, 07:22 PM
Lag on SourceOP - by speedily - Mar 27, 2008, 08:05 PM
Lag on SourceOP - by avy - Mar 28, 2008, 09:40 AM
Lag on SourceOP - by Drunken F00l - Mar 31, 2008, 06:23 PM
Lag on SourceOP - by speedily - Apr 02, 2008, 08:50 PM
Lag on SourceOP - by Drunken F00l - Apr 02, 2008, 10:05 PM
Lag on SourceOP - by Retribution - Apr 03, 2008, 03:22 AM
Lag on SourceOP - by avy - Apr 03, 2008, 09:45 AM
Lag on SourceOP - by Retribution - Apr 03, 2008, 11:24 AM
Lag on SourceOP - by avy - Apr 03, 2008, 12:07 PM
Lag on SourceOP - by Retribution - Apr 03, 2008, 12:28 PM
Lag on SourceOP - by avy - Apr 03, 2008, 01:07 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)