From owner-freebsd-current@FreeBSD.ORG Thu May 13 01:31:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2643B16A4CE for ; Thu, 13 May 2004 01:31:54 -0700 (PDT) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 241A243D39 for ; Thu, 13 May 2004 01:31:53 -0700 (PDT) (envelope-from glebius@cell.sick.ru) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.9/8.12.8) with ESMTP id i4D8Vovw031337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 May 2004 12:31:50 +0400 (MSD) (envelope-from glebius@cell.sick.ru) Received: (from glebius@localhost) by cell.sick.ru (8.12.9/8.12.6/Submit) id i4D8VnnS031336; Thu, 13 May 2004 12:31:49 +0400 (MSD) Date: Thu, 13 May 2004 12:31:49 +0400 From: Gleb Smirnoff To: Michael Ortmann Message-ID: <20040513083149.GC31159@cell.sick.ru> References: <1059881061@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1059881061@web.de> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: mpd caused a panic after padi-packet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 08:31:54 -0000 On Thu, May 13, 2004 at 08:58:15AM +0200, Michael Ortmann wrote: M> a friend of mine tried to setup mpd (ppp daemon) for interactive dialin. M> but the system repeadable crashes when the first padi packet arrives. M> this packet is for discovering things such as service-name, dhcp, ... M> M> this panic occurs on 2 systems, an duron 1200 and an pentium mmx M> M> the crash is at least reproduceable unter fbsd 5.2 and 5.2.1 and 2 different systems, one with a duron 1200 and one with a pentium mmx Currently, mpd is not able to work as a PPPoE access concentrator under CURRENT. Hope this will be fixed sometime later. Now you should use STABLE for PPPoE AC. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE