"Hughes, B." <omn### [at] charternet> wrote in message
news:3fa207fb@news.povray.org...
> I've had some trouble using tracert recently. After not using that for a
> long time, I decided to see some timings by pinging and it just timed out
> all the time. I did a tracert and all I ever get is a "destination net
> unreachable" at the same location. Apparently it's a new route the
Internet
> traffic takes from a nearby town to the outskirts of this State's largest
> city. My ISP has been making changes, upgrading the hardware locally for
the
> past year or more.
>

a significant portion of the network now bitbuckets icmp echo
responses/requests -

so MS tracert and the old Van Jacobson udp based traceroute tools fail a lot

proper traceroute tools use different methods (ports, fin/syn packets,
etc....)

try lft ( http://www.mainnerve.com/lft/ ) , it gets around firewalls and
uses intelligent tcp port
switching - e.g.; (there are binaries avail for Win (cygwin) and Linux as
well as source code
for Unix systems)

sexus:[/home/user] # lft -ENATS www.povray.org

TTL  LFT trace to povray.org (204.213.191.228):80/tcp
**   [firewall] the next gateway may statefully inspect packets
 1   [AS11908] [IANA-CBLK1] rm356.npqr.net (192.168.1.254) 4.6/12.7ms
 2   [AS209] [QWEST-SYIX-NET1] tcr-01.syix.com (205.171.72.11)
136.3/235.8/*/*/*ms
 3   * [AS209] [QWEST-SYIX-NET1] t1400.syix.com (205.171.72.1) 215.6/*/*/*ms
 4   [AS209] [NET-QWEST-BLKS-4] 65.119.8.125 153.8/226.2/*/*/*ms
 5   [AS209] [CSN-BLOCK-7] bur-core-01.inet.qwest.net (205.171.13.29)
158.3/196.9/*/*/*ms
 6   [AS209] [CSN-BLOCK-7] bur-brdr-01.inet.qwest.net (205.171.13.10)
152.0/200.6/*/*/*ms
 7   [AS1239] [SPRINT-INNET9] sl-bb22-ana-6-2.sprintlink.net (144.232.9.237)
159.0/159.4/*ms
 8   [AS1239] [SPRINT-INNET9] sl-bb22-fw-10-1.sprintlink.net (144.232.9.250)
181.3/193.6/290.1ms
 9   [AS1239] [SPRINT-INNET9] sl-bb22-chi-11-0.sprintlink.net
(144.232.18.121) 211.1/220.9ms
10   [AS1239] [SPRINT-INNET9] sl-bb24-chi-8-0.sprintlink.net
(144.232.26.109) 220.2/218.6ms
11   [AS1239] [SPRINT-INNET9] sl-bb25-nyc-5-0.sprintlink.net (144.232.9.157)
222.1/221.9ms
12   [AS1239] [SPRINT-INNET9] sl-bb24-nyc-10-0.sprintlink.net
(144.232.13.181) 224.0/229.6ms
13   [AS1239] [SPRINT-INNET9] sl-gw27-nyc-15-0.sprintlink.net (144.232.7.26)
233.6/222.0ms
14   [AS1239] [SPRINT-INNET] sl-netplex-6-0.sprintlink.net (144.223.36.246)
288.1/233.7ms
15   [AS6062] [SPRINT-CCD5BF] office1.atm.ntplx.net (204.213.183.1)
231.6/238.4ms
16   [AS6062] [SPRINT-CCD5BF] colo-router.ether.ntplx.net (204.213.183.26)
252.1/233.3ms
17   [AS6062] [SPRINT-CCD5BF] [target] povray.org (204.213.191.228):80
229.3/251.5ms

LFT's trace took 10.21 seconds.  Resolution required 66.50 seconds.

of course there are switches to turn off the name lookup resolution that ate
up most of
that 66 seconds ...

Post a reply to this message