From owner-freebsd-current  Sat Jul 29 04:01:53 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id EAA06994
          for current-outgoing; Sat, 29 Jul 1995 04:01:53 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id EAA06977
          for <current@freefall.cdrom.com>; Sat, 29 Jul 1995 04:01:50 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id DAA02036; Sat, 29 Jul 1995 03:59:13 -0700
Date: Sat, 29 Jul 1995 03:59:13 -0700
Message-Id: <199507291059.DAA02036@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: current@freefall.cdrom.com
In-reply-to: <199507280820.BAA06732@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: ijppp experiencing problems in -current?
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: current-owner@FreeBSD.org
Precedence: bulk

 * This is weird, but after almost a year of flawless operation, ijppp
 * has gone south on me.  It stays up for about 10-15 minutes at a time,
 * max, and then sig 10's on me..  This started occurring only recently.
 * 
 * Have we done something recently in -current to kill it?
 * 
 * Anyone else seeing this?

Yes.  I noticed this right after some big changes went in to ppp (in
July 8).  I had been using ijppp fine (for about three days ;) prior
to the make world that included that change.  It started dying
frequently with sig 10's, although it wasn't as bad as "max 10-15
minutes".

I also did a measurement (time rcp bigfile.gz, ping somehost) and
found that slip is 20-30% better both in throughput and latency.  So I
gave up on ijppp and haven't tried it since.

Satoshi