Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!ORVILLE.NAS.NASA.GOV!lekash
From: lekash@ORVILLE.NAS.NASA.GOV (John Lekashman)
Newsgroups: comp.sys.proteon
Subject: FAL 1.2/BTI/Proteon problem
Message-ID: <8812151859.AA01509@orville.nas.nasa.gov>
Date: 15 Dec 88 18:59:09 GMT
References: <8812151224.AA09302@dainichi.tn.cornell.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 10

We had a somewhat similar problem, (but not exactly the same)
where an amdahl running UTS could not complete the arp transaction.
It turned out to be a bug in the driver, where it would clobber 
the incoming arp packet with a retransmit of the arp request.
Someone was being frugal with buffers, and it did not work if 
the timing was wrong.

We used the workaround of having a couple of vaxes supply the 
arp response for the broken machine, until we got the driver
fixed.
					john