From owner-freebsd-hackers  Mon Dec  2 16:29:52 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA24073
          for hackers-outgoing; Mon, 2 Dec 1996 16:29:52 -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 QAA24068
          for <hackers@freebsd.org>; Mon, 2 Dec 1996 16:29:51 -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 QAA01891; Mon, 2 Dec 1996 16:29:46 -0800 (PST)
To: Bill Fenner <fenner@parc.xerox.com>
cc: hackers@freebsd.org
Subject: Re: Bizarro bug in 2.1.6 that's had me stumped for ages... 
In-reply-to: Your message of "Mon, 02 Dec 1996 11:32:02 PST."
             <96Dec2.113208pst.177711@crevenia.parc.xerox.com> 
Date: Mon, 02 Dec 1996 16:29:46 -0800
Message-ID: <1887.849572986@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 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.

					Jordan