From owner-freebsd-security Mon Feb 19 2: 9:17 2001 Delivered-To: freebsd-security@freebsd.org Received: from xocah.holywar.net (xocah.holywar.net [211.232.152.22]) by hub.freebsd.org (Postfix) with SMTP id 3337637B491 for ; Mon, 19 Feb 2001 02:09:14 -0800 (PST) Received: (qmail 6810 invoked by uid 101); 19 Feb 2001 10:09:11 -0000 Date: Mon, 19 Feb 2001 19:09:11 +0900 From: "ho-sang, yoon" To: Shoichi 'Ne' Sakane Cc: freebsd-security@FreeBSD.ORG Subject: Re: Racoon startup at boot problem Message-ID: <20010219190910.A4429@xocah.holywar.net> Reply-To: Tsoi Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010219131622Q.sakane@ydc.co.jp>; from sakane@ydc.co.jp on Mon, Feb 19, 2001 at 01:16:22PM +0900 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What version do you mean? I have tried 'racoon-20010215a' from ftp.kame.net, but it didn't work. Maybe it's because of my fault. But, I don't know. Anyway, I have get backed to the strict SPI definition way not using racoon at all.(Direct SAD entry input by setkey) But, anyway, thanks for your information. xocah Thus spake Shoichi 'Ne' Sakane (sakane@ydc.co.jp) ::::: : > 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. -- no signature To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message