Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!imci3!newsfeed.internetmci.com!howland.reston.ans.net!hole.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: Tue, 11 Jun 1996 20:51:36 +0100 Organization: UnipalmPIPEX server (post doesn't reflect views of UnipalmPIPEX) Lines: 53 Message-ID: <31BDCDE8.41C67EA6@dial.pipex.com> References: <31BBC0E9.41C67EA6@dial.pipex.com> <31BC273E.73CC@www.play-hookey.com> <4phqnb$4n0@uriah.heep.sax.de> NNTP-Posting-Host: aj042.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) J Wunsch wrote: > > You cannot autodial on this however. This is quite clear if you think > about how autodialing works -- it must detect an outgoing packet > destined for a particular address before, in order to know that it has > to dial just for this packet now. > Jorg, Your point certainly makes sense, hence my experiments with a "false real" address /all bits variable; as mentioned, it worked that way. In /etc/ppp/ppp.conf : set ifaddr 0 x.y.z.t/0 add 0 0 x.y.z.t In /etc/ppp/ppp.linkup : MYADDR: delete ALL add 0 0 HISADDR In /etc/rc.local ppp -auto pipex The first 'add' (in ppp.conf) fools the kernel into believing x.y.z.t is the proper end of the link; the 'delete ALL' get read of this fake when the link comes up, and the second 'add' establishes the proper end. I suspect x.y.z.t could be any address (like one picked from the "non-connected" network address space) -- I just used the address of one of the pads I connected to, but I ended up with enough different ones to prove this worked. There is however a slight problem : the 'delete ALL' does not seem to get rid of the routing entry between the OLD local address and 127.0.01, which means the routing table fills in with junk entries after a number of connect/disconnect. In fact, what we need is a ppp.linkdown, so that we could delete these junk entries automatically when the connection goes down. I must point out (me being a newbie, that should be obvious) that I did not try any of these with gated. I dread to think what's gonna happen if I ever do ! Salutations Distinguees, Pierre Y.