From owner-freebsd-net@FreeBSD.ORG Thu Jul 12 01:43:05 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 07C2216A468 for ; Thu, 12 Jul 2007 01:43:05 +0000 (UTC) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [66.119.58.2]) by mx1.freebsd.org (Postfix) with ESMTP id 7C7DE13C469 for ; Thu, 12 Jul 2007 01:43:04 +0000 (UTC) (envelope-from brett@lariat.net) Received: from anne-o1dpaayth1.lariat.org (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2]) by lariat.net (8.9.3/8.9.3) with ESMTP id TAA28481; Wed, 11 Jul 2007 19:14:08 -0600 (MDT) Message-Id: <200707120114.TAA28481@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 11 Jul 2007 19:14:03 -0600 To: Mike Tancsa From: Brett Glass In-Reply-To: References: <200707110014.SAA02181@lariat.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: freebsd-net@freebsd.org Subject: Re: Bug in userland PPP LQR? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jul 2007 01:43:05 -0000 At 06:23 PM 7/11/2007, Mike Tancsa wrote: >Did you try and use just LCP echo mode instead ? I have come across a >number of devices (especially GPRS/EVDO cards) that seem to say yes to >supporting LQR, but do not. Try instead lcp echo I will try it. (To be more specific, I am going to try disable lqr allow lqr enable echo echoperiod 12 so that the peer can get LQR if it requests it.) But since this would just be working around the bug I think might be there, it would also be a good idea to look at how the LQR counter is managed. From what I can see, the problem is that the counter either is cumulative or counts irrevocably up to 5 after one LQR packet is missed. The reason why I'd like to see more eyes than my own on this is that it's difficult to see how and where the LQR routines are invoked and how they react to a pattern of missed and un-missed packets. --Brett