From owner-freebsd-current Fri Jul 28 07:14:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id HAA10334 for current-outgoing; Fri, 28 Jul 1995 07:14:36 -0700 Received: from asstdc.scgt.oz.au (asstdc.scgt.oz.au [202.14.234.65]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id HAA10325 for ; Fri, 28 Jul 1995 07:14:28 -0700 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id AAA09923; Sat, 29 Jul 1995 00:12:56 +1000 From: michael butler Message-Id: <199507281412.AAA09923@asstdc.scgt.oz.au> Subject: Re: ijppp experiencing problems in -current? To: kmitch@nando.net (kmitch) Date: Sat, 29 Jul 1995 00:12:55 +1000 (EST) Cc: current@freebsd.org In-Reply-To: <9507281238.AA04974@nando.net.nando.net> from "kmitch" at Jul 28, 95 08:38:37 am X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1001 Sender: current-owner@freebsd.org Precedence: bulk kmitch@nando.net writes: > > 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. > I've seen something similar, but I can't narrow it down enough to see if it is > my internet provider or ppp. What I am seeing is ppp will stay up fairly > reliable until I start a web browser (Netscape or Mosaic), and then the > connection dies. I am running a tree from around the 18th. I don't think > it sig 10s though when it does this, so this may be completely different. I noted this when running on a 14k4 link prior to replacing it with ISDN. If the link was saturated, LQR echos were lost in sufficient quantity to cause PPP to think the link was down. If LQR is disabled or denied, an excess of missed LCP echos ends up causing the same thing. Things improved marginally by dropping MTU to 576. I never noted any exceptions, michael