From owner-freebsd-security  Sun Feb 18 20:13:45 2001
Delivered-To: freebsd-security@freebsd.org
Received: from mine.kame.net (kame195.kame.net [203.178.141.195])
	by hub.freebsd.org (Postfix) with ESMTP id 6BB9537B4EC
	for <freebsd-security@freebsd.org>; Sun, 18 Feb 2001 20:13:41 -0800 (PST)
Received: from localhost ([202.249.11.124])
	by mine.kame.net (8.9.3/3.7W) with ESMTP id NAA51837;
	Mon, 19 Feb 2001 13:26:01 +0900 (JST)
To: tsoi@xocah.dhs.org
Cc: freebsd-security@freebsd.org
Subject: Re: Racoon startup at boot problem
In-Reply-To: Your message of "Wed, 14 Feb 2001 17:29:29 +0900"
	<20010214172929.A76809@xocah.holywar.net>
References: <20010214172929.A76809@xocah.holywar.net>
X-Mailer: Cue version 0.6 (010125-0306/sakane)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20010219131622Q.sakane@ydc.co.jp>
Date: Mon, 19 Feb 2001 13:16:22 +0900
From: "Shoichi 'Ne' Sakane" <sakane@ydc.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 9
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> When one server is rebooted and re-initialized racoon, 
> they do not communicate at all, (in my opinion) because of mis-match of 
> SPI on each server's SAD entries. 

Does the problem happen by using the latest racoon ?

We know that there are some problem such a SPI mismatch when
the system using automated SA negotiation reboots.  
The problem when the initiator rebooted was solved the latest racoon.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message