From owner-freebsd-questions Sun Sep 21 22:14:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA13184 for questions-outgoing; Sun, 21 Sep 1997 22:14:34 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA13173 for ; Sun, 21 Sep 1997 22:14:30 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id OAA14250; Mon, 22 Sep 1997 14:44:22 +0930 (CST) Message-ID: <19970922144422.06946@lemis.com> Date: Mon, 22 Sep 1997 14:44:22 +0930 From: Greg Lehey To: Doug White Cc: Keith Spencer , freebsd-questions@FreeBSD.ORG Subject: Re: PPP...won't dial out! Driving me nuts References: <199709200649.QAA18296@smmcroute.smmc.qld.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Doug White on Sun, Sep 21, 1997 at 09:28:25PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, Sep 21, 1997 at 09:28:25PM -0700, Doug White wrote: > On Sat, 20 Sep 1997, Keith Spencer wrote: > >> Hi all, >> I have set what PPP&SLIP chap 13 in docs said to do (I believe) >> But I have set my ppp.conf as per below. (thanks Greg Lahey) >> But hey...not a blip out of the modem (I now it works OK) >> Maybe I have the setups trying com1 instead of com2? >> I have done the PPP & SLIP setups according to ch13 as user ppp >> >> I notice that ifconfig -a >> reports...=flags8010 mtn 1500 >> shouldn't it say RUNNING > > No. Mine doesn't. > >> here is ppp.conf >> default: >> set device /dev/cuaa1 >> set speed 57600 > > Are these correct for your modem? > > What happens if you type `term' to drop to terminal mode then try to dial > manually (atdt 727424)? > >> set authname xxxxx >> set authkey yyyyyyy > > Hope what was there was blanked out, or else you'd better change your > password. (I blanked it case.) The real problem was that I gave him a corrupted dial string. He repeated it in one of his messages, and nobody noticed :-( It's working now after fixing the dial string. Greg