*BSD News Article 70629


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!asstdc.scgt.oz.au!nsw.news.telstra.net!act.news.telstra.net!vic.news.telstra.net!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!tank.news.pipex.net!pipex!lade.news.pipex.net!pipex!tube.news.pipex.net!pipex!dish.news.pipex.net!pipex!soap.news.pipex.net!pipex!usenet
From: "Pierre Y. Dampure" <pdampure@dial.pipex.com>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: 'iijppp -auto' and Dynamic IP Address Allocation
Date: Mon, 10 Jun 1996 18:46:57 +0100
Organization: UnipalmPIPEX server (post doesn't reflect views of UnipalmPIPEX)
Lines: 46
Message-ID: <31BC5F32.41C67EA6@dial.pipex.com>
References: <31BBC0E9.41C67EA6@dial.pipex.com> <31BC273E.73CC@www.play-hookey.com>
NNTP-Posting-Host: ao158.du.pipex.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0b4Gold (X11; I; FreeBSD 2.2-960501-SNAP i386)

Ken Bigelow wrote:
> 
> Pierre Y. Dampure wrote:
> >
> > How can one set up iijppp to get dial on demand when one's ISP
> > allocates from either a class B or class C network ? seems Pipex
> > allocates its dialup IP clients either in net 128.43 or in net
> > 193.130.250, which makes it rather difficult for iijppp to deal with !
> >
> > I probably miss something, but has anyone successfully implemented
> > iijppp dial on demand with this ISP ?
> > Check the handbook on user PPP, and also look through all of the sample
> ppp.--- files in /etc/ppp. It is quite possible to have iijppp accept
> either or both IP addresses from the peer.
> 
> The basic procedure is to allocate an IP address of 0.0.0.0/0, and let
> the negotiations take place normally. This technique is included in the
> sample files.
> 
> I hope this helps!
> 
> Ken

I'm afraid this will not work straight out of the box, Ken. I did a bit
of digging around your tip, however, and found a somewhat acceptable
solution :

	set ifaddr 0 158.43.128.1/0

Indeed, your straight

	set ifaddr 0 0

causes ijppp to come up with a 'must specify dtsaddr in auto mode'
message and to abort -- I guess it must find itself in some kind of
chicken and egg situation.

The downside of the above cheat is, I now need to ping the dummy dstaddr
once to get the ball rolling -- I mean, the proper route installed --
easily done in rc.local, but I'd rather do without.

Is this where diald starts looking like a reasonable alternative ?



Pierre Y.