From owner-freebsd-stable@FreeBSD.ORG Mon Nov 24 08:30:52 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC5A016A4CE for ; Mon, 24 Nov 2003 08:30:52 -0800 (PST) Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0142E43FE5 for ; Mon, 24 Nov 2003 08:30:51 -0800 (PST) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smtp3.sentex.ca (8.12.9p2/8.12.9) with ESMTP id hAOGUkm5010962; Mon, 24 Nov 2003 11:30:46 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9p2/8.12.9) with ESMTP id hAOGUlUr044993; Mon, 24 Nov 2003 11:30:48 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.0.1.1.0.20031124112952.05c286d8@209.112.4.2> X-Sender: mdtpop@209.112.4.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1 Date: Mon, 24 Nov 2003 11:35:58 -0500 To: Michael Nottebrock , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <200311241725.19516.michaelnottebrock@gmx.net> References: <3D98E439.1010400@pydo.org> <200311241659.49594.michaelnottebrock@gmx.net> <6.0.1.1.0.20031124110621.0698a788@209.112.4.2> <200311241725.19516.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new Subject: Re: ppp(8) v. 3.1 : PPPoE lqr problem. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2003 16:30:52 -0000 At 11:25 AM 24/11/2003, Michael Nottebrock wrote: > > And for > > sure its an ERX on the other end ? > >Actually it's an NRP - it seems Cisco does a better job with their PPPoE >implementation. OK, thanks. The problem I see is only against an ERX. So either misconfigured ERX or something about Juniper's implementation. As the original poster was connecting against Frace Telecom and I to Bell Canada and given that VJ Header compression also does not play well with FreeBSD's I am leaning to the ERX. Back to the original question of how best to work around this. I will be deploying close to 100 boxes, most of which will talk to an ERX. It would be nice if I could avoid having to manually patch the boxes each time I do an update. If I work with my programmers here to come up with a patch, is there even a chance that someone would commit it to HEAD and then MFC it back to RELENG_4? Who is looking after PPP these days anyways ? ---Mike