Hi,
Even better, try traceroute
This reports the time for each leg of the route taken by the icmp packets.
This verifies there is (or is not) a problem in your setup.
Derek.
==============================================
On Sun, 21 Sep 2008, Ross Drummond wrote:
On Sun, 21 Sep 2008, Nick Rout wrote:
On Sat, Sep 20, 2008 at 10:09 PM, Wesley Parish
<[EMAIL PROTECTED]> wrote:
64 bytes from 203.96.152.127: icmp_seq=1458 ttl=55 time=4608 ms
64 bytes from 203.96.152.127: icmp_seq=1459 ttl=55 time=3615 ms
64 bytes from 203.96.152.127: icmp_seq=1460 ttl=55 time=2623 ms
64 bytes from 203.96.152.127: icmp_seq=1461 ttl=55 time=1644 ms
--------------------------------------
Wesley try this;
ping -c 1 -R paradise.net.nz
-R Record route. Includes the RECORD_ROUTE option in the
ECHO_REQUEST packet and displays the route buffer on returned
packets. Note that the IP header is only large enough for nine
such routes. Many hosts ignore or discard this option.
If your ISP supports this you can see the hop's taken to reach paradise,then
you can test each hop with a ping to check latency.
Cheers Ross Drummond
--
Derek Smithies Ph.D.
IndraNet Technologies Ltd.
Email: [EMAIL PROTECTED]
ph +64 3 365 6485
Web: http://www.indranet-technologies.com/
