From owner-freebsd-hackers Mon Dec 2 18:46:33 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01589 for hackers-outgoing; Mon, 2 Dec 1996 18:46:33 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA01576 for ; Mon, 2 Dec 1996 18:46:24 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id NAA18384; Tue, 3 Dec 1996 13:46:48 +1100 (EST) Date: Tue, 3 Dec 1996 13:46:48 +1100 (EST) From: "Daniel O'Callaghan" To: "Jordan K. Hubbard" cc: Bill Fenner , hackers@FreeBSD.org Subject: Re: Bizarro bug in 2.1.6 that's had me stumped for ages... In-Reply-To: <14016.849580656@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 2 Dec 1996, Jordan K. Hubbard wrote: > > 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. :) *sigh* Rats. I want this solved, too, but evidence of what is going on is really hard to come by.. My arpresovle errors could be caused *by* the problem, rather than at the heart of it. Danny