From owner-freebsd-current@FreeBSD.ORG Thu Jul 29 15:10:14 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 5598E16A4CF; Thu, 29 Jul 2004 15:10:14 +0000 (GMT) Received: from bittern.mail.pas.earthlink.net (bittern.mail.pas.earthlink.net [207.217.120.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 164BC43D55; Thu, 29 Jul 2004 15:10:14 +0000 (GMT) (envelope-from durian@boogie.com) Received: from cpe-66-87-52-132.co.sprintbbd.net ([66.87.52.132] helo=mailhost.boogie.com) by bittern.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 1BqCXd-0003Qy-00; Thu, 29 Jul 2004 08:09:57 -0700 Received: from man.boogie.com (man.boogie.com [192.168.1.3]) by mailhost.boogie.com (8.12.11/8.12.11) with ESMTP id i6TF9u6K048603; Thu, 29 Jul 2004 09:09:56 -0600 (MDT) (envelope-from durian@boogie.com) From: Mike Durian To: freebsd-current@freebsd.org Date: Thu, 29 Jul 2004 09:09:56 -0600 User-Agent: KMail/1.6.2 References: <20040729033814.GA56115@freefall.freebsd.org> In-Reply-To: <20040729033814.GA56115@freefall.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407290909.56415.durian@boogie.com> cc: Michael Lestinsky cc: Bosko Milekic Subject: Re: ipsec/racoon broken 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, 29 Jul 2004 15:10:14 -0000 On Wednesday 28 July 2004 09:38 pm, Bosko Milekic wrote: > Someone sent me a bug report about this and I'll look > into it. I'll post with results when I get around to > it (by this weekend I hope). > > For now, you can set MSIZE=512 in your kernel config to > work around it. I have also suffered from the racoon breakage. Hannes Mehnert suggested I set MSIZE to 320, which fixed the racoon problem, but has led to a system panic (sorry no back-trace, I haven't had a chance to dig in, but I believe it was a page-not-present type of fault). Actually, I don't know if the MSIZE change caused the panic, or if it is due to some other change since my last good working kernel of Feb. 29. mike