Consider: ... 64 bytes from 192.168.251.7: icmp_req=458 ttl=64 time=0.189 ms 64 bytes from 192.168.251.7: icmp_req=459 ttl=64 time=0.123 ms 64 bytes from 192.168.251.7: icmp_req=460 ttl=64 time=0.120 ms 64 bytes from 192.168.251.7: icmp_req=461 ttl=64 time=0.126 ms ... The blank line indicates where there was a delay of a couple of seconds between ping responses. However there were no missed responses (icmp_req goes from 459 to 460) and the time is shown as only 0.120ms. So why was there a delay of a couple of seconds at this point? Mark -- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) 21 Drakes Mews, Milton Keynes, MK8 0ER
On Fri, 02 Nov 2012 14:45:41 +0000, mark@quarella.co.uk said:
The blank line indicates where there was a delay of a couple of seconds between ping responses.
Why do you think that? -- We're looking for smart Linux people: http://www.tiger-computing.co.uk/jobs
You are assuming that an echo packet was sent, then there was a delay, then the echo reply was receive,d and finally the screen was updated. How do you know that before sending echo packet 460 your computer wasn't momentarily busy, a background process fired up, something was writing to the hard disk etc, so the traceroute program paused momentarily perhaps? James.
participants (3)
-
James Bensley -
Keith Edmunds -
Mark Rogers