From owner-freebsd-security Mon Nov 13 22:14:30 2000 Delivered-To: freebsd-security@freebsd.org Received: from lynx.aba.net.au (lynx.esec.com.au [203.21.84.1]) by hub.freebsd.org (Postfix) with SMTP id 4D8B837B479 for ; Mon, 13 Nov 2000 22:14:27 -0800 (PST) Received: (qmail 31550 invoked from network); 14 Nov 2000 06:14:24 -0000 Received: from swun.esec.com.au (HELO eSec.com.au) (203.21.85.207) by lynx.esec.com.au with SMTP; 14 Nov 2000 06:14:24 -0000 Message-ID: <3A10DB41.926EA1A@eSec.com.au> Date: Tue, 14 Nov 2000 17:27:13 +1100 From: Sam Wun Organization: eSec X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: security@FreeBSD.ORG Subject: Re: racoon -> isakmpd References: <657B20E93E93D4118F9700D0B73CE3EA02427F@goofy.epylon.lan> Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can we use isakmpd in FreeBSD instead? If we can use isakmpd in FreeBSD, both ends will be talking to the same protocol. Sam. Jason DiCioccio wrote: > I would be interested in this too if anyone knows > > ------- > Jason DiCioccio > Unix BOFH > > mailto:jasond@epylon.com > > 415-593-2761 Direct & Fax > 415-593-2900 Main > > Epylon Corporation > 645 Harrison Street, Suite 200 > San Francisco, CA 94107 > www.epylon.com > > OK, so you're a Ph.D. Just don't touch anything. > > -----Original Message----- > From: Sam Wun [mailto:swun@eSec.com.au] > Sent: Monday, November 13, 2000 6:36 PM > Cc: security@FreeBSD.ORG > Subject: racoon -> isakmpd > > Hi! > > Does anyone got a FreeBSD box with racoon working together with a > OpenBSD box with isakmpd as a VPN? > > Our headoffice uses OpenBSD on their firewall and uses isakmpd for VPN, > I want to use FreeBSD with racoon but with no sucess. > > Any working configs out there? > > Thanks > Sam. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message