From owner-freebsd-net@FreeBSD.ORG  Mon Jul 12 21:32:19 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 C258A16A4DC
	for <freebsd-net@freebsd.org>; Mon, 12 Jul 2004 21:32:19 +0000 (GMT)
Received: from fever.boogie.com (cpe-66-87-52-132.co.sprintbbd.net
	[66.87.52.132])	by mx1.FreeBSD.org (Postfix) with ESMTP id 5365C43D2D
	for <freebsd-net@freebsd.org>; Mon, 12 Jul 2004 21:32:19 +0000 (GMT)
	(envelope-from durian@boogie.com)
Received: from man.boogie.com (man.boogie.com [192.168.1.3])
	by fever.boogie.com (8.12.11/8.12.11) with ESMTP id i6CLWIeG000847
	for <freebsd-net@freebsd.org>; Mon, 12 Jul 2004 15:32:18 -0600 (MDT)
	(envelope-from durian@boogie.com)
From: Mike Durian <durian@boogie.com>
To: freebsd-net@freebsd.org
Date: Mon, 12 Jul 2004 15:32:18 -0600
User-Agent: KMail/1.6.2
References: <200406091423.31355.durian@boogie.com>
In-Reply-To: <200406091423.31355.durian@boogie.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200407121532.18503.durian@boogie.com>
Subject: Re: Racoon breakage with recent kernel
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jul 2004 21:32:19 -0000

On Wednesday 09 June 2004 02:23 pm, Mike Durian wrote:
> Sometime between Feb 9 and June 9 something changed in the kernel
> that causes racoon to fail.  I'm afraid I don't have a verbatim
> error message handy, but my notes (from running racoon with debugging
> enabled, in the foreground) say the error was in pk_sendupdate
> and the errno was, ENOBUFS.
>
> I believe this message is reporting the same problem I'm seeing:
>
> http://groups.google.com/groups?q=racoon+%22No+buffer+space+available%22&hl
>=en&lr=&ie=UTF-8&selm=20040606025301.GB41345%40mehnert.org&rnum=1
>
> Does anybody know what is going on?

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.

Thanks,
mike