From: "Dotan Cohen" <dotancohen@xxxxxxxxx>
On 03/07/06, Roger Taranto <roger@xxxxxxxxxxxx> wrote:
...
But, I'd suggest following Joanne's advice (jdow) on using ping. She
writes device drivers and probably knows what she's talking about. :)
-Roger
Thanks, Roger. I so did, and got an interesting result. You can see
that as I work my way out, the ping time gets slowly longer, but on
the last one, it jumps from ~13 ms to ~88 ms. Does that seem unusual,
or is because it's going across a large way? I did ping a .co.il (my
country's domain extension) address, but that does not necessarily
mean that the site is hosted here.
traceroute: Warning: google.co.il has multiple addresses; using 216.239.37.99
traceroute to google.co.il (216.239.37.99), 30 hops max, 40 byte packets
1 192.168.123.254 (192.168.123.254) 0.656 ms 0.727 ms 0.443 ms
2 c1.actcom.co.il (192.114.47.218) 11.318 ms 10.208 ms 9.154 ms
3 rtr76.actcom.co.il (192.114.47.250) 10.096 ms 17.469 ms 8.018 ms
4 nv-act.ser.netvision.net.il (199.203.173.126) 14.279 ms 12.589
ms 11.864 ms
5 gi1-0.core1.hfa.nv.net.il (212.143.8.1) 15.324 ms 15.684 ms *
6 pos2-10.brdr1.lnd.nv.net.il (212.143.12.122) 88.808 ms 87.282 ms
$ ping -c 8 192.114.47.218
That seems to indicate a normal enough delay. The site may be relatively
overloaded. There is also a possibility that the actual machine at that
address might simply be a fowarding address to a Google site in the
US. That's about a 6700 mile (10800 km) sort of delay time difference.
So far that shows no packet loss. I'd run the pings for a longer time,
say 100 pings or so, and look at the summary. If there are zero dropped
packets then Google should seem normally responsive to you.
{^_^}
