Date: Tue, 17 Mar 1998 11:49:24 +0100 From: Eivind Eklund <eivind@yes.no> To: Nate Williams <nate@sneezy.sri.com>, Brian Somers <brian@Awfulhak.org> Cc: Stephen Wynne <stevemw@northwest.com>, stable@FreeBSD.ORG Subject: Re: On-demand dynamic PPP not doing default route correctly Message-ID: <19980317114924.43713@follo.net> In-Reply-To: <199803170943.CAA00552@nomad.mt.sri.com>; from Nate Williams on Tue, Mar 17, 1998 at 02:43:25AM -0700 References: <199803161302.GAA01357@nomad.mt.sri.com> <199803170032.AAA12927@awfulhak.org> <199803170943.CAA00552@nomad.mt.sri.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 17, 1998 at 02:43:25AM -0700, Nate Williams wrote: > > > Hmm, that seemed to do the 'routing' trick for sure. *MUCH* better than > > > having to futz with the routing. However, I don't know what's happening > > > with the link getting all balled up, since I'm not sure whose fault it > > > is. > > > > The rationale behind the ppp.linkup bit is that ppp doesn't know > > where your default route should point 'till it negotiates an IP with > > the other side. > > So why doesn't it wait to se the default route until after it knows the > other side? It seems silly to set something that you know ahead of time > is bous. Cause otherwise it won't get the packets to start it dialling, and it doesn't get any new default route. Catch 22. I like to use an interface route for the dial-on-demand case, but that only work satisfactory when you are not doing FTP or other address-encoding protocols locally from that box, and you _are_ using aliasing. I can go into the details for the above if there is interest; I've already described my code to Brian (and offered him a copy of the code, IIRC). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980317114924.43713>