From owner-freebsd-hackers  Mon Dec  2 18:38:17 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA01154
          for hackers-outgoing; Mon, 2 Dec 1996 18:38:17 -0800 (PST)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA01144
          for <hackers@FreeBSD.org>; Mon, 2 Dec 1996 18:38:14 -0800 (PST)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.3/8.6.9) with ESMTP id SAA14039; Mon, 2 Dec 1996 18:37:36 -0800 (PST)
To: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
cc: Bill Fenner <fenner@parc.xerox.com>, hackers@FreeBSD.org
Subject: Re: Bizarro bug in 2.1.6 that's had me stumped for ages... 
In-reply-to: Your message of "Tue, 03 Dec 1996 13:13:00 +1100."
             <Pine.BSF.3.91.961203130617.1605r-100000@panda.hilink.com.au> 
Date: Mon, 02 Dec 1996 18:37:36 -0800
Message-ID: <14016.849580656@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> Look at freefall's routing tables and messages files, not just your own.
> I experience exactly the same symptoms as you, and it is at the remote 
> end that I see the errors in the log file. Look for arpresolve errors.

Not a peep in freefall's message log.  Ah well, good theory, anyway. :)

					Jordan