"ping XXX.XXX.XXX.XXX" in run command
Pinging www.some-domain.com [XXX.XXX.XXX.XXX] with 32 bytes of
Reply from XXX.XXX.XXX.XXX: bytes=32 time=564ms TTL=237
Reply from XXX.XXX.XXX.XXX: bytes=32 time=555ms TTL=237
Reply from XXX.XXX.XXX.XXX: bytes=32 time=554ms TTL=237
Reply from XXX.XXX.XXX.XXX: bytes=32 time=548ms TTL=237
Ping statistics for XXX.XXX.XXX.XXX:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 548ms, Maximum = 564ms, Average = 555ms
TTL?
Every IP packet that gets sent out has a TTL field which is set to a relatively high number (in the case of ping a TTL of 255). As the packet traverses the network, the TTL field gets decreased by one by each router it goes through; when the TTL drops to 0, the packet is discarded by the router. The IP spec says that the TTL should be set to 60 (though it's 255 for ping packets). The main purpose of this is so that a packet doesn't live forever on the network and will eventually die when it is deemed "lost." But for ping purposes, it provides additional information. The TTL can be used to determine approximately how many router hops the packet has gone through. If the TTL field varies in successive pings, it could indicate that the successive reply packets are going via different routes, which isn't a great thing.
'ping time'?
"Ping time" refers to the amount of time it takes for a small "packet" of data to travel over the internet from one computer to another computer and back to the first computer. It is usually reported in milliseconds (ms).
(Referred in blogs)
