Date: Tue, 17 Mar 1998 02:43:25 -0700 (MST) From: Nate Williams <nate@nomad.mt.sri.com> To: Brian Somers <brian@Awfulhak.org> Cc: "Nate Williams" <nate@sneezy.sri.com>, Stephen Wynne <stevemw@northwest.com>, stable@FreeBSD.ORG Subject: Re: On-demand dynamic PPP not doing default route correctly Message-ID: <199803170943.CAA00552@nomad.mt.sri.com> In-Reply-To: <199803170032.AAA12927@awfulhak.org> References: <199803161302.GAA01357@nomad.mt.sri.com> <199803170032.AAA12927@awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. The ``add default HISADDR'' will do this. Ppp > doesn't cache these ``add'' and ``delete'' commands and re-apply them > when the interface addresses change (which I believe pppd does with > the ``defaultroute'' config option). Therefore, the ppp.linkup file > must have them. IMHO, routing shouldn't be necessary in ppp.linkup. What previously only required editing one file now requires editing two, thus increasing the complexity (un-necessarily). > > Thanks alot for the routing information. It's certainly made life > > easier for me! > > As far as the link jamming is concerned, lqr and ECHO lqr now works > properly (well, for me anyway). While re-organising it in the MP > branch, I discovered what the problem has been all these years :-) > > You may want to > > enable lqr > set log +lqm OK. What am I looking for? > or if you're in interactive mode (or on a diagnostic socket) > > set log local +lqm > > You should see if the other side is silently drifting into oblivion. > It's also worth doing the occasional ``show hdlc'' to see if you're > getting FCS errors - lots of them may mean you've got a login: prompt > at the other end :-( The link shouldn't ever work if I'm seeing a login prompt. My problem is that it works for 15-60 messages (using fetchmail) then jams. However, this morning it jammed doing downloads, so I can now say that it appears to jam with about anything, but randomly. (It jammped 3 times in the 4 minutes I took to answer this.) Nate 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?199803170943.CAA00552>