*BSD News Article 96903


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!howland.erols.net!newsfeed.internetmci.com!uuneo.neosoft.com!not-for-mail
From: conrads@neosoft.com (Conrad Sabatier)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Automatic PPP connection (usermode PPP, 2.2)
Date: Tue, 3 Jun 1997 17:44:20 -0500
Organization: NeoSoft, Inc.  
Lines: 52
Message-ID: <4o62n5.3d5.ln@dolphin.neosoft.com>
References: <5mv92j$k9@news.gvsu.edu>
Reply-To: conrads@neosoft.com (Conrad Sabatier)
NNTP-Posting-Host: as5200-port-254.no.neosoft.com
X-Newsreader: trn 4.0-test58 (13 May 97)
Originator: conrads@neosoft.com (Conrad Sabatier)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42222

In article <5mv92j$k9@news.gvsu.edu>,
Matt Behrens <behrensm@river.it.gvsu.edu> wrote:
>Hi all,
>
>I'm going crazy with automatic PPP on 2.2.2-rELEASE.  I have it working
>great in every more except for auto.  (BTW, the background mode is VERY
>nice -- that command line was getting on my nerves in 2.1) :)
>
>Here's what I've got for my pmdemand (the ppp.conf.sample said pmdemend, I
>assume that was a typo):
>
>pmdemand:
> set phone 555-5555
> set login "TIMEOUT 15 name: user word: password PPP \"\""
> set timeout 120
> set ifaddr 204.177.185.116/0 204.177.184.53/0
> delete ALL
> add 0 0 HISADDR
> set openmode active
>
>I also put the pmdemand entry from ppp.linkup.sample into my ppp.linkup,
>no change, except for the script line where I started my own script.
>
>Here's what happens when I type ppp -auto pmdemand:
>
>ppp puts itself into the background.
>ppp dials immediately.  (I checked, nothing s trying to access the 'net at
>this time.)
>My ISP times out and ppp dies.

Don't use "delete ALL; add 0 0 HISADDR" in ppp.conf.  These statements
belong in ppp.linkup.  I'm no expert at this stuff, either, but I think
this is what's causing ppp to dial out immediately (you're telling it to
use routing information that it doesn't have yet, so it needs to connect
to your ISP to get it).

Try using this instead:

 add 204.177.185.116 255.255.255.0 204.177.184.53

to establish a default route until you've connected and gotten the true IP
information from your ISP (I assume you're doing dynamic IP).

And "timeout 120" is awfully short, too (only two minutes).  I use 360
myself, and have my mailer poll for mail every five minutes to keep the
connection alive.

Anyway, this works for me.  YMMV.  :-)
-- 
Conrad Sabatier
http://www.neosoft.com/~conrads