From owner-freebsd-net@FreeBSD.ORG Wed Mar 22 15:53:34 2006 Return-Path: X-Original-To: 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 8371E16A400 for ; Wed, 22 Mar 2006 15:53:34 +0000 (UTC) (envelope-from vanhu@zeninc.net) Received: from leia.fdn.fr (ns0.fdn.org [80.67.169.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 048E543D46 for ; Wed, 22 Mar 2006 15:53:33 +0000 (GMT) (envelope-from vanhu@zeninc.net) Received: from smtp.zeninc.net (reverse-25.fdn.fr [80.67.176.25]) by leia.fdn.fr (8.13.3/8.13.3/FDN) with ESMTP id k2MFrVns022226 for ; Wed, 22 Mar 2006 16:53:31 +0100 Received: by smtp.zeninc.net (smtpd, from userid 1000) id 0B87B3F17; Wed, 22 Mar 2006 16:53:26 +0100 (CET) Date: Wed, 22 Mar 2006 16:53:26 +0100 From: VANHULLEBUS Yvan To: freebsd-net@freebsd.org Message-ID: <20060322155325.GA24077@zen.inc> References: <44217266.4000906@vineyard.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44217266.4000906@vineyard.net> User-Agent: All mail clients suck. This one just sucks less. Subject: Re: racoon config trouble X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Mar 2006 15:53:34 -0000 On Wed, Mar 22, 2006 at 10:51:02AM -0500, Eric W. Bates wrote: > I'm trying to link a FreeBSD 5.3 machine with a Juniper appliance and > I'm failing during the phase one negotiation. > > Without spamming the list with copious output, can anyone help me > decipher the racoon error: > > Mar 22 08:18:06 fw racoon: ERROR: ignore information > because ISAKMP-SA has not been established yet. > > With log set to 'debug2', there is a lot of information; but this is the > first line in the log which is expresses any level of warning or error. Hi. ipsec-tools-devel(/user) ML is probably really more appropriate for such a question, I just didn't have time to answer your mail on it for now :-) The short answer is "this error is probably NOT related to your problem", and i'll do the long answer on ipsec-tools-devel "asap" Yvan. -- NETASQ - Secure Internet Connectivity http://www.netasq.com