From owner-freebsd-net@FreeBSD.ORG Sun Aug 8 17:00:53 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B915916A4CE for ; Sun, 8 Aug 2004 17:00:53 +0000 (GMT) Received: from smtp3b.sentex.ca (smtp3b.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59AEE43D3F for ; Sun, 8 Aug 2004 17:00:53 +0000 (GMT) (envelope-from mike@sentex.net) Received: from BLUELAPIS.sentex.ca (cage.simianscience.com [64.7.134.1]) by smtp3b.sentex.ca (8.12.11/8.12.11) with SMTP id i78H0bPW001929; Sun, 8 Aug 2004 13:00:37 -0400 (EDT) (envelope-from mike@sentex.net) From: Mike Tancsa To: Julian Elischer Date: Sun, 08 Aug 2004 13:01:00 -0400 Message-ID: <2vmch0phgtf3028ie4447h2hruq7vdi7ac@4ax.com> References: <200407240247.i6O2lQfJ007370@dungeon.home> <200407250144.i6P1iCPx005756@dungeon.home> <41032C09.506@elischer.org> <0pfbg01araih3qekvbse5afdshf2tjf2qr@4ax.com> <4105D6A9.5020600@elischer.org> In-Reply-To: <4105D6A9.5020600@elischer.org> X-Mailer: Forte Agent 1.93/32.576 English (American) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable cc: freebsd-net@freebsd.org Subject: Re: PPPoE problem: "Too many LQR packets lost" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Aug 2004 17:00:53 -0000 On Mon, 26 Jul 2004 21:14:33 -0700, in sentex.lists.freebsd.net you wrote: >Mike Tancsa wrote: > >>On Sat, 24 Jul 2004 20:42:01 -0700, in sentex.lists.freebsd.net you >>wrote: >> =20 >> >>>>>Seriously though, mine was a very ugly hack to >>>>>get things working again for me. Most of the DSL aggregators here >>>>>are Juniper ERXes which do not play nice with FreeBSD's PPPoE. >>>>> >>>>> =20 >>>>> >>>any thoughts as to why? >>> >>>FreeBSD's pppoe is going through a little development at the moment.. >>>Now would be a good time to get it fixed.. >>Hi, >>Simple LCP echos work just fine, but when using LQR things "break". >>There are debug logs posted in the archives when I first figured out >>what was broken. If you need another copy I am happy to post again. >> > >certainly it would be useful. rather than taking potsots at the archive=20 >hoping to catch it.. > >pppoe is tricky because the responsibility for errors os split between=20 >the pppoe module > and the ppp module.. Just to followup for the archives sake, the latest LQR changes do not fix the ppp/PPPoE problem with respect to the issue below. I have a full TCPDUMP as well as ppp debug logs that illustrate the problem for anyone interested.=20 ---Mike