Date: Thu, 9 Sep 2004 22:01:42 +0200 From: Hannes Mehnert <hannes@mehnert.org> To: Brian Somers <brian@Awfulhak.org> Cc: freebsd-net@freebsd.org Subject: Re: Racoon breakage with recent kernel - what NOT to do Message-ID: <20040909200142.GD1128@mehnert.org> In-Reply-To: <20040909202955.438a4327@dev.lan.Awfulhak.org> References: <200406091423.31355.durian@boogie.com> <200407121532.18503.durian@boogie.com> <20040714185248.GC70193@mehnert.org> <20040909202955.438a4327@dev.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Thu, Sep 09, 2004 at 08:29:55PM +0100, Brian Somers wrote: > On Wed, 14 Jul 2004 20:52:48 +0200, Hannes Mehnert <hannes@mehnert.org> wrote: > > On Mon, Jul 12, 2004 at 03:32:18PM -0600, Mike Durian wrote: > > > This is just a follow-up to say the problem still exists in a -current > > > system I built from source yesterday (7/11/04). Does anyone know > > > what's going on? > > > > > > And to clarify, the URL listed above does show the same problem I'm > > > seeing. > > > > A workaround is setting MSIZE to 320 in your kernel config: > > options MSIZE=320 > > Well, I applied this tweak to my kernel config file (some time ago!) and > it fixed the racoon issue.... **BUT** doing this badly breaks dtom() - all > sorts of issues turn up when a data pointer can't be turned back into its > owning mbuf pointer. I'm currently using MSIZE=512 and get no panic. Best Regards, Hannes Mehnert -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBQLajRcuNlziBjRwRAgCuAJ9ajZ3Ha5k6nLp596rI1CgjDQku5ACgwEEa bSyjt6gknTfLznRBgqEhCkk= =WPaf -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040909200142.GD1128>