traceroute to a cisco

Article View: comp.dcom.sys.cisco

Article #165

Back to comp.dcom.sys.cisco Previous Next

#165

From: Barry Margolin
Date: Wed, 15 Apr 1992 23:05

28 lines
1276 bytes

When I trace the route to a cisco router, it apparently ignores every other
probe packet.  In the example below, Rome and Avignon are two ciscos that
are on the same subnet (131.239.20).  This isn't critical, but I'm curious
whether there's an obvious explanation or it's just a bug.

Rome#trace
Protocol [ip]: 
Target IP address: avignon
Translating "AVIGNON"...domain server (131.239.2.1) [OK]

Source address: 
Numeric display [n]: 
Timeout in seconds [3]: 
Probe count [3]: 10
Minimum Time to Live [1]: 
Maximum Time to Live [30]: 
Port Number [33434]: 
Loose, Strict, Record, Timestamp, Verbose[none]: 
Type escape sequence to abort.
Tracing the route to AVIGNON.THINK.COM (131.239.20.249)

  1 AVIGNON.THINK.COM (131.239.20.249) 4 msec *  4 msec *  0 msec *  0 msec *  4 msec * 
Rome#
-- 
Barry Margolin
System Manager, Thinking Machines Corp.

barmar@think.com          {uunet,harvard}!think!barmar

Technical Details

Message-ID: <kupdlmINNesb@early-bird.think.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!barmar

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.dcom.sys.cisco
Subject: traceroute to a cisco
Date: 15 Apr 1992 23:05:26 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 28
Message-ID: <kupdlmINNesb@early-bird.think.com>
NNTP-Posting-Host: telecaster.think.com