From owner-freebsd-net@FreeBSD.ORG Tue Jul 27 04:14:37 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 96BF016A4CE for ; Tue, 27 Jul 2004 04:14:37 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06EB143D1F for ; Tue, 27 Jul 2004 04:14:37 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (adsl-68-121-219-69.dsl.snfc21.pacbell.net [68.121.219.69])i6R4EYlM234862; Tue, 27 Jul 2004 00:14:35 -0400 Message-ID: <4105D6A9.5020600@elischer.org> Date: Mon, 26 Jul 2004 21:14:33 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030524 X-Accept-Language: en, hu MIME-Version: 1.0 To: Mike Tancsa References: <200407240247.i6O2lQfJ007370@dungeon.home> <200407250144.i6P1iCPx005756@dungeon.home> <41032C09.506@elischer.org> <0pfbg01araih3qekvbse5afdshf2tjf2qr@4ax.com> In-Reply-To: <0pfbg01araih3qekvbse5afdshf2tjf2qr@4ax.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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: Tue, 27 Jul 2004 04:14:37 -0000 Mike Tancsa wrote: >On Sat, 24 Jul 2004 20:42:01 -0700, in sentex.lists.freebsd.net you >wrote: > > >>>>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. >>>> >>>> >>>> >>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 hoping to catch it.. pppoe is tricky because the responsibility for errors os split between the pppoe module and the ppp module.. > > ---Mike > > >