Racoon breakage with recent kernel - what NOT to do

[Brian Somers]

On Thu, 9 Sep 2004 22:01:42 +0200, Hannes Mehnert <hannes at mehnert.org> wrote:
> -----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 at 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.

Yes, MSIZE=512 works as it contains only one set bit.  MSIZE=320 doesn't
because there are two bits set.  I've posted my other message to -net
with a better description.

Cheers.

-- 
Brian <brian at Awfulhak.org>                        <brian@[uk.]FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !