From owner-freebsd-current Tue Jul 4 16:58:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id BFE8137BA82 for ; Tue, 4 Jul 2000 16:58:25 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id QAA06372; Tue, 4 Jul 2000 16:57:44 -0700 (PDT) From: Archie Cobbs Message-Id: <200007042357.QAA06372@bubba.whistle.com> Subject: Re: PPPoE not working In-Reply-To: <200007031725.SAA87581@hak.lan.Awfulhak.org> from Brian Somers at "Jul 3, 2000 06:25:34 pm" To: brian@Awfulhak.org (Brian Somers) Date: Tue, 4 Jul 2000 16:57:44 -0700 (PDT) Cc: dberlin@cygnus.com (Daniel Berlin), archie@whistle.com (Archie Cobbs), dan@cgsoftware.com (Daniel Berlin), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers writes: > Archie, it seems people are having problems using PPPoE since your > ng_ether changes. Any suggestions ? Unfortunately I have limited email contact righ tnow.. but a couple of things come to mind.. - Is is possible to get a tcpdump of before and after? One thing I could imagine is that the new ng_ether may behave differently than the old code with respect to overwriting the source Ethernet address (the new code shouldn't unless the driver does). But I don't think there should be any difference. 'tcpdump not ip' should tell. - Regarding the libnetgraph change, this supposedly fixed a bug, so possibly the code in ppp(8) is relying on broken behavior? Where is this code anyway, I don't see a pppoe.c in usr.sbin/ppp.. I can take a look. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message