From owner-freebsd-current  Sun Sep 21 06:10:03 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA00221
          for current-outgoing; Sun, 21 Sep 1997 06:10:03 -0700 (PDT)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA00174
          for <current@FreeBSD.ORG>; Sun, 21 Sep 1997 06:09:55 -0700 (PDT)
Received: from gate.lan.awfulhak.org (localhost [127.0.0.1])
	by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id NAA27388;
	Sun, 21 Sep 1997 13:57:27 +0100 (BST)
Message-Id: <199709211257.NAA27388@awfulhak.demon.co.uk>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Alex <garbanzo@hooked.net>
cc: Brian Somers <brian@awfulhak.org>, current@FreeBSD.ORG
Subject: Re: Problems with -current ppp 
In-reply-to: Your message of "Sat, 20 Sep 1997 22:11:00 PDT."
             <Pine.BSF.3.96.970920220934.349B-100000@zippy.dyn.ml.org> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 21 Sep 1997 13:57:27 +0100
From: Brian Somers <brian@awfulhak.org>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> 
> On Sat, 20 Sep 1997, Brian Somers wrote:
> 
> > > In your ppp.secret create a line like this
> > > hostname	password
> > > once you telnet into port 3000 type passwd password, and you'll get access
> > > to everything.  Once I got past that, I've still had a lot of problem with
> > > ppp -ddial.
> > 
> > What sort of problems ?
> 
> A while back after all this password (and other I guess) stuff was
> commited, I would be getting unable to open port 3000 messages, and now
> with the same script that I use, I must wait for ppp to dial my isp then
> hit ctrl c to "kill" it, it will then be able to connect.  If I don't it
> the remote modem drops carrier after a while, and ppp hangs.

I don't think I follow this.  I assume ppp is being run interactively.  
Are you saying you have to "dial", then ^C, then dial again ?

You may have been suffering from a Predictor1 bug that was recently 
fixed.  This would cause the line to "hang" very soon after 
connection.  The latest copy on http://www.freebsd.org/~brian has
this fixed.

> - alex
> 

-- 
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <bri@OpenBSD.org>
      <http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour....