Date: Wed, 18 Mar 1998 22:44:51 +0000 From: Brian Somers <brian@Awfulhak.org> To: "Nate Williams" <nate@sneezy.sri.com> Cc: Brian Somers <brian@Awfulhak.org>, "Daniel O'Connor" <doconnor@gsoft.com.au>, stable@FreeBSD.ORG Subject: Re: On-demand dynamic PPP not doing default route correctly Message-ID: <199803182244.WAA10511@awfulhak.org> In-Reply-To: Your message of "Wed, 18 Mar 1998 03:04:07 MST." <199803181004.DAA00780@nomad.mt.sri.com>
index | next in thread | previous in thread | raw e-mail
> > > In short, I think this is it. (Sorry Brian, but it appears that LQR is
> > > still broken from my experience, at least in the version in -stable as
> > > of late last week.)
> > >
> > > In summary, it appears that all of my problems are solved. :)
> >
> > The fixes went in on the 12th (lqr.c 1.2[34]). Is your version
> > before or after that ?
>
> * $Id: lqr.c,v 1.7.2.9 1998/01/26 20:04:55 brian Exp $
>
> (Don't have a CVS tree to look at to see if that's really old enough.)
Looks like you've got the older (broken) lqr code. It should be:
* $Id: lqr.c,v 1.7.2.10 1998/03/13 00:58:09 brian Exp $
You're probably better off disabling lqr 'till you get the update.
>From your other mail, you'll see that "PeerInLQRs" is set to zero.
The other side never bothers sending an LQR response :-( Ppp gives
up on the 6th LQR and dies.
The new code will only increase the "PeerOutLQRs" field if the peer
has responded to the last LQR. If it hasn't, the same PeerOutLQR
value is sent and ppp remembers that it's resent. Five resends and
you're out.
I suspect that some LQR implementations don't bother sending LQRs
when the link is busy. The RFC says that they don't have to if
they have their own LQR timer and they haven't seen a packet with the
same number of PeerOutLQRs before. Because the new code is sending
the next LQR without increasing PeerOutLQRs, the peer MUST respond
according to the rfc.
The problem is that I can't prove this because my ISP refuses to
negotiate LQRs and I haven't got any other ppp implementations handy.
Anyway, the figures you posted are otherwise useless. They only show
that we haven't received any LQRs from the peer :-( FWIW, you could
enable `async' logging to see all async data being passed back and
forth. This would show if ppp is actually receiving any (even bogus)
data.
> Nate
--
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
<http://www.Awfulhak.org>;
Don't _EVER_ lose your sense of humour....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803182244.WAA10511>