From owner-freebsd-hackers  Sun Sep 21 20:07:23 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA05283
          for hackers-outgoing; Sun, 21 Sep 1997 20:07:23 -0700 (PDT)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA05275;
          Sun, 21 Sep 1997 20:07:12 -0700 (PDT)
Received: from gate.lan.awfulhak.org (localhost [127.0.0.1])
	by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id EAA07211;
	Mon, 22 Sep 1997 04:05:54 +0100 (BST)
Message-Id: <199709220305.EAA07211@awfulhak.demon.co.uk>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Brian Somers <brian@awfulhak.org>
cc: Eivind Eklund <perhaps@yes.no>, Brian Somers <brian@FreeBSD.ORG>,
        hackers@FreeBSD.ORG
Subject: Re: cvs commit: src/usr.sbin/ppp lcp.c 
In-reply-to: Your message of "Mon, 22 Sep 1997 02:09:08 BST."
             <199709220109.CAA05366@awfulhak.demon.co.uk> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 22 Sep 1997 04:05:54 +0100
From: Brian Somers <brian@awfulhak.org>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Hmm, looks like the incremental backout may be a better idea.

It now waits for .8 of a second after receiving a dup magic number.  
The second dup will cause a wait of 1.2 seconds and things increment 
thereafter by .4 of a second.

The real problem here is that if the client side decides on a new 
magic number, it also NAKs the received Req.  It then receives the 
NAK and changes magic again, sending another Req..... which bounces 
due to ECHO etc etc etc.

If we send more than two Reqs, by the time the other side starts, 
it's got a huge stream of magic changes waiting in the tty queue and 
gets hopelessly confused.  This normally means a fast exit by the 
server.


-- 
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <bri@OpenBSD.org>
      <http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour....