From owner-freebsd-current Sun Sep 21 21:35:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA10191 for current-outgoing; Sun, 21 Sep 1997 21:35:37 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA10186 for ; Sun, 21 Sep 1997 21:35:33 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id XAA01111; Sun, 21 Sep 1997 23:35:20 -0500 (CDT) Message-ID: <19970921233450.07729@my.domain> Date: Sun, 21 Sep 1997 23:34:50 -0500 From: Tom Jackson To: Brian Somers Cc: current@FreeBSD.ORG Subject: Re: Problems with -current ppp References: <19970921164855.48382@my.domain> <199709220052.BAA05100@awfulhak.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709220052.BAA05100@awfulhak.demon.co.uk>; from Brian Somers on Mon, Sep 22, 1997 at 01:52:08AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Sep 22, 1997 at 01:52:08AM +0100, Brian Somers wrote: > > I've been having this *exact* same problem of carrier being dropped > > and thought it was my ISP's fault. Will someone please elaborate. > > Due to more than one problem, ppp was failing to hang up on loss of > carrier. It also used to have a problem negotiating CCP with a peer > that wanted a different sort of CCP. > > These problems are now fixed. A current version of ppp is available > on http://www.freebsd.org/~brian. > > > Tom > > -- > Brian , , > > Don't _EVER_ lose your sense of humour.... > > Well thanks for the effort Brian. Unfortunately, it had no effect on the problem. The reliable way for me to reproduce this is to call my shell account at the university and try to send a 69k msg, drops every time, here lately. I've always got a 'unknown protocol 0x803f' and show hdlc gives proto:1 but the connection has worked much better in the past. This is into a NT4.0 ISP if that makes a difference. btw, is this version of ppp different than the current version on 3.0? Maybe it is my ISP Tom