Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!THINK.COM!bruce
From: bruce@THINK.COM
Newsgroups: comp.protocols.tcp-ip
Subject: IP record route
Message-ID: <8905042139.AA01559@mozart.think.com>
Date: 4 May 89 21:39:23 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 17

I was just debugging some routes from our Nearnet gw with the Cisco ping
command, which allows one to turn on IP options like "record route".  

I began just pinging a friendly Sun4 at NRL (on 128.60) without any IP
options on, and the machine was responding fine.  But when I tried it with
record-route on, it stopped responding to any pings for quite a while, even
subsequent ones without record on.  Since I can't seem to reach any
machines on that net after the experiment, I assume the target machine
didn't crash, but it seems as if I might be crashing a gateway along the
way with record-route!

I did this twice with the same results.  I can reach that net again after
about 10 minutes.  If anyone had a couple of unexpected gateway crashes
today, the last about 5pm, this could explain it.

--Bruce Walker (Nemnich), Thinking Machines Corporation, Cambridge, MA
  bruce@think.com, think!bruce, bjn@mitvma.bitnet; +1 617 876 1111