[vox-tech] Why I'll Never Be a Network Admin Guy

[Danny Webster]

    What Pete describes is how I understand TTL to mean also.  I see that
pinging that site from my location in Redding, CA shows 11 hops.  If I were
in China or Germany, there is a chance that site would be unavailable to me
because as the ping shows, TTL is set to 53:
PING jenipurr.com (216.92.165.105) from 64.163.109.75 : 56(84) bytes of
data.
64 bytes from 216.92.165.105: icmp_seq=0 ttl=53 time=106.1 ms
64 bytes from 216.92.165.105: icmp_seq=1 ttl=53 time=105.0 ms
64 bytes from 216.92.165.105: icmp_seq=2 ttl=53 time=108.1 ms
64 bytes from 216.92.165.105: icmp_seq=3 ttl=53 time=105.5 ms
--- jenipurr.com ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 105.0/106.1/108.1 ms

 1  adsl-64-163-109-73.dsl.chic01.pacbell.net (64.163.109.73)  13.124 ms
19.715 ms  13.544 ms
 2  dist1-vlan50.chic01.pbi.net (216.102.186.214)  13.103 ms  15.172 ms
13.445 ms
 3  bb1-g1-0.chic01.pbi.net (63.200.183.3)  18.244 ms  15.066 ms  26.460 ms
 4  sl-gw23-ana-0-2.sprintlink.net (160.81.103.53)  51.436 ms  33.780 ms
71.026 ms
 5  sl-bb20-ana-3-3.sprintlink.net (144.232.1.45)  162.738 ms  62.071 ms
39.884 ms
 6  sl-bb24-sj-10-0.sprintlink.net (144.232.20.101)  157.835 ms  84.814 ms
40.272 ms
 7  sl-bb21-rly-14-1.sprintlink.net (144.232.20.22)  270.446 ms  195.940 ms
97.942 ms
 8  sl-bb22-rly-13-0.sprintlink.net (144.232.7.254)  120.892 ms  156.169 ms
106.463 ms
 9  sl-gw33-rly-8-0.sprintlink.net (144.232.14.86)  210.706 ms  96.411 ms
95.738 ms
 10  208.30.208.42 (208.30.208.42)  112.249 ms  179.246 ms  101.647 ms
 11  jenipurr.com (216.92.165.105)  103.428 ms  135.343 ms  128.766 ms

Danny
----- Original Message -----
From: "Richard Crawford" <rscrawford@mossroot.com>
To: <vox-tech@lists.lugod.org>
Sent: Tuesday, October 22, 2002 12:22 PM
Subject: [vox-tech] Why I'll Never Be a Network Admin Guy


> My wife's domain, jenipurr.com, is having odd issues today.  Of course,
> the first thing I did was ping the domain to see if I could do any
> trouble shooting.  This is what I got:
>
..