From owner-freebsd-questions  Sun Sep 17 13:23:19 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA24815
          for questions-outgoing; Sun, 17 Sep 1995 13:23:19 -0700
Received: from virgo.ai.net (root@virgo.ai.net [198.69.44.2])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA24807
          for <questions@freebsd.org>; Sun, 17 Sep 1995 13:23:14 -0700
Received: from aries.ai.net (aries.ai.net [198.69.44.1]) by virgo.ai.net (8.6.11/8.6.12) with ESMTP id QAA28192; Sun, 17 Sep 1995 16:06:35 -0400
Received: (from nc@localhost) by aries.ai.net (8.6.11/8.6.12) id QAA17429; Sun, 17 Sep 1995 16:06:29 -0400
Date: Sun, 17 Sep 1995 16:06:28 -0400 (EDT)
From: Network Coordinator <nc@ai.net>
To: Gary Palmer <gary@palmer.demon.co.uk>
cc: Rob Simons <rob@simplex.nl>, questions@freebsd.org
Subject: Re: pppd acting up 
In-Reply-To: <29448.811363618@palmer.demon.co.uk>
Message-ID: <Pine.BSF.3.91.950917160606.17397A-100000@aries.ai.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
Precedence: bulk

> My guess is that is your problem. Unfortunately, I don't have time at
> the minute to track it down, but I've heard similar complaints from
> others about this, and I think that the proxyarp stuff is involved.

Well pppd doesn't die for us, and we aren't usign proxyarp.

TIA,

-Jerry.