From owner-freebsd-net Sun Nov 3 4:29: 5 2002 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 2526537B438 for ; Sun, 3 Nov 2002 04:29:01 -0800 (PST) Received: from terror.org.pl (terror.icm.edu.pl [193.219.28.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C4FD43F6B for ; Sun, 3 Nov 2002 04:28:34 -0800 (PST) (envelope-from ofca@terror.org.pl) Received: from ofca (helo=localhost) by terror.org.pl with local-esmtp id 188JrT-000175-00; Sun, 03 Nov 2002 13:28:15 +0100 Date: Sun, 3 Nov 2002 13:28:14 +0100 (CET) From: Pawel Tyll X-X-Sender: ofca@terror.org.pl To: Julian Elischer Cc: brian@awfulhak.org, Subject: Re: PPPoEd Bug. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 2 Nov 2002, Julian Elischer wrote: > The code for doing non complient pppoe was written to be used as a > client. I'm amazed it works as a server too.. (and I wrote it). Well, it worked allright for me (and it would be a nice feature too, short of this bug ;) ) > Am I right in understanding that you accidentally had a non-compliant > client, and therefore discoverd that FreeBSD as a server could cope with > that, but that once it did, it couldn't go back? I wasn't at first aware that it was this client at fault (I didn't know it was patched back then). But generally you're right :) > I'll have a look. Thank You Best regards, Pawel 'ofca' Tyll. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message