*BSD News Article 96813


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!vbcnet-west!knews.uk0.vbc.net!vbcnet-gb!azure.xara.net!xara.net!news.maxwell.syr.edu!news.mathworks.com!rill.news.pipex.net!pipex!hose.news.pipex.net!pipex!warm.news.pipex.net!pipex!tank.news.pipex.net!pipex!news.utell.co.uk!usenet
From: brian@shift.utell.net (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Automatic PPP connection (usermode PPP, 2.2)
Date: 3 Jun 1997 09:41:20 GMT
Organization: Awfulhak Ltd.
Lines: 55
Message-ID: <5n0os0$5bl@ui-gate.utell.co.uk>
References: <5mv92j$k9@news.gvsu.edu>
Reply-To: brian@awfulhak.org, brian@utell.co.uk
NNTP-Posting-Host: shift.utell.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42134

In article <5mv92j$k9@news.gvsu.edu>,
	behrensm@river.it.gvsu.edu (Matt Behrens) writes:
> 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

Change the add line to "add 0 0 204.177.184.53".  Sorry - I screwed
up the example in 2.2.2 :(

> 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.

If ppp dials imediately, try "set debug TCP/IP" and find out what's
triggering it.  Good candidates are routed, named and rwhod.  You
can create some filters to ignore them.

> I'm totally lost, folks.  (BTW, I put those 204..blah blah addresses in
> because network 10 is already used on site here.)

If the addresses aren't allocated, use the address ranges suggested
in /etc/hosts.

> Thanks for any help!
> 
> --
>   Matt Behrens
>   Zigg Computer Services
>   zigg@iserv.net
>   http://www.iserv.net/~zigg/

-- 
Brian <brian@awfulhak.org> <brian@freebsd.org>
      <http://www.awfulhak.org>
Don't _EVER_ lose your sense of humour !