From owner-freebsd-hackers  Tue Aug  8 21:23:13 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id VAA15320
          for hackers-outgoing; Tue, 8 Aug 1995 21:23:13 -0700
Received: from palmer.demon.co.uk (palmer.demon.co.uk [158.152.50.150])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id VAA15309
          for <freebsd-hackers@freebsd.org>; Tue, 8 Aug 1995 21:23:10 -0700
Received: from localhost (localhost [127.0.0.1])
	  by palmer.demon.co.uk (8.6.11/8.6.11) with SMTP id FAA00440
	  ; Wed, 9 Aug 1995 05:14:18 +0100
To: Bruce Evans <bde@zeta.org.au>
cc: cshenton@apollo.hq.nasa.gov, jc@irbs.com, freebsd-hackers@freebsd.org
Subject: Re: client & server ppp 
In-reply-to: Your message of "Wed, 09 Aug 1995 14:00:39 +1000."
             <199508090400.OAA03763@godzilla.zeta.org.au> 
Date: Wed, 09 Aug 1995 05:14:17 +0100
Message-ID: <438.807941657@palmer.demon.co.uk>
From: Gary Palmer <gary@palmer.demon.co.uk>
Sender: hackers-owner@freebsd.org
Precedence: bulk

In message <199508090400.OAA03763@godzilla.zeta.org.au>, Bruce Evans writes:
>>again from home. FBSD pppd also consumes all CPU available: on a
>>system with two pppds, they both run at 50%. W.R.T. die-on-hangup and

>I've never seen an overhead problem in pppd.

I belive it's related to the problem with the non-working proxyarp
option. I've certainly seen this in post 2.0 system, and a friend was
griping at me for ages to fix it (not running pppd locally made it
difficult :-( ).

I thought I saw a patch for the proxyarp problem floating around, and
it may have gone into the source tree, although a quick look through
usr.sbin/pppd/*.c's log messages doesn't show anything obvious.

Gary