From owner-freebsd-hackers Mon Dec 2 17:07:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26077 for hackers-outgoing; Mon, 2 Dec 1996 17:07:46 -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 RAA26070 for ; Mon, 2 Dec 1996 17:07:39 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id MAA18017; Tue, 3 Dec 1996 12:07:54 +1100 (EST) Date: Tue, 3 Dec 1996 12:07:54 +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: <1887.849572986@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: > > What's your routing table look like when this happens? > > > > Bill > > Pretty much normal - my default route is there along with the usual > host routes for the machines on my physical ethernet. When I > completely flush the table and add back the default route, there is > also no change in behavior. One thing I found last night which worked > was to kill slattach and restart the link - then my sl0 behaved > normally again. I don't need to completely reboot, simply reset the > connection. What is at the other end of the link? Is it also a FreeBSD box? Danny