Path: utzoo!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!helios.ee.lbl.gov!pasteur!ucbvax!VAX.FTP.COM!jbvb
From: jbvb@VAX.FTP.COM (James Van Bokkelen)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: IP options
Message-ID: <9005291334.AA01385@vax.ftp.com>
Date: 29 May 90 13:34:17 GMT
Article-I.D.: vax.9005291334.AA01385
References: <9005271931.aa06596@louie.udel.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 15
X-Local-Date: 29 May 90 06:34:17 PDT

IP options are fairly widely used, but certain very comnmon TCP/IP
implementations (4.2 bsd in particular) don't handle them well.  From
my site, there are some paths/destination hosts where Record Route
works fine, some where a response is received without the option,
some where the packet just disappears, and some where some node on
the path crashes when the option is seen.  Meanwhile, some routers
put their addresses in the option, and some don't.  Psigh.

I would recommend an expanding search scheme - ping your local router
with Record Route, then some hosts on the next net, then the next net's
router, etc.  Keep your ears open for the harsh cries of administrators
whose hosts crash, and quote RFC 1122 at them when they hunt you down.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901