Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!ucbcad!ucbvax!LANL.GOV!cpw%sneezy
From: cpw%sneezy@LANL.GOV (C. Philip Wood)
Newsgroups: comp.protocols.tcp-ip
Subject: Suns, Symbolics, Celerities and Reverse ARP
Message-ID: <8708261808.AA16444@sneezy.lanl.gov>
Date: Wed, 26-Aug-87 14:08:16 EDT
Article-I.D.: sneezy.8708261808.AA16444
Posted: Wed Aug 26 14:08:16 1987
Date-Received: Fri, 28-Aug-87 06:17:59 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18

Excuse if you already know about this problem.  But,
a recent release of software for the Celerity OS caused
a big headache here at LANL.  The symptom was Suns and
Symbolics machines could not boot or communicate because
they could not find out their internet addresses via RARP.
Or, rather, they found out a wrong address, namely 0.0.0.0.
This tidbit of information was provided by the Celerity RARP
handler.

I give credit to Celerity for finding out about the problem and
fixing it.  However, it took some sluthing with etherfind to figure
out who the culprit was on our part.  And, then finding the offending
piece of hardware, and then finding someone who would take responsibility
for it, and then calling up Celerity support.  Once we got that far
the fix was easy.  Run ifconfig with the -arp option, and wait for
the patch tapes in the mail.  The came the next day.

Phil Wood (cpw@lanl.gov)