From owner-freebsd-net@FreeBSD.ORG Sun May 9 12:18:08 2004 Return-Path: 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 BB00416A4CE for ; Sun, 9 May 2004 12:18:08 -0700 (PDT) Received: from mta05-svc.ntlworld.com (mta05-svc.ntlworld.com [62.253.162.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31AF443D1F for ; Sun, 9 May 2004 12:18:08 -0700 (PDT) (envelope-from jon@witchspace.com) Received: from witchspace.com ([81.110.67.239]) by mta11-svc.ntlworld.com (InterMail vM.4.01.03.37 201-229-121-137-20020806) with SMTP id <20040509142408.XZUA2033.mta11-svc.ntlworld.com@witchspace.com> for ; Sun, 9 May 2004 15:24:08 +0100 Received: (qmail 9058 invoked from network); 9 May 2004 14:24:07 -0000 Received: from unknown (HELO webmail.local) (127.0.0.1) by localhost.witchspace.com with SMTP; 9 May 2004 14:24:07 -0000 Received: from 192.168.0.1 (SquirrelMail authenticated user jon) by webmail.local with HTTP; Sun, 9 May 2004 15:24:07 +0100 (BST) Message-ID: <3511.192.168.0.1.1084112647.squirrel@webmail.local> In-Reply-To: <3099.192.168.0.1.1084111337.squirrel@webmail.local> References: <3099.192.168.0.1.1084111337.squirrel@webmail.local> Date: Sun, 9 May 2004 15:24:07 +0100 (BST) From: "Jonathan Belson" To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal Subject: Re: Outstanding issues with ipsec under 5.2.1? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2004 19:18:08 -0000 Hiya > I've just spent a few hours trying to set up a working ipsec tunnel > between a wireless laptop and my server. I found an e-mail from someone who was having a similar problem with 5.2-RELEASE http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2858147+0+/usr/local/www/db/text/2004/freebsd-current/20040208.freebsd-current so it looks like the problem still exists. I've worked around it in the meantime by replacing 'require' with 'use'. Is the FAST_IPSEC option only for machines with crypto-hardware? Cheers, -- Jon