From owner-freebsd-net Thu Nov 5 05:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11037 for freebsd-net-outgoing; Thu, 5 Nov 1998 05:27:18 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from inner.net (avarice.inner.net [199.33.248.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11025 for ; Thu, 5 Nov 1998 05:27:16 -0800 (PST) (envelope-from cmetz@inner.net) Received: from inner.net (cmetz.cstone.net [205.197.102.217]) by inner.net (8.9.1/8.9.1) with ESMTP id NAA21643; Thu, 5 Nov 1998 13:12:10 GMT Message-Id: <199811051312.NAA21643@inner.net> To: enkhyl@hayseed.net cc: "Jordan K. Hubbard" , freebsd-net@FreeBSD.ORG Subject: Re: ipsec (VPN) for -current ? (Re: VPN through encrypted IP tunnel for FreeBSD? ) In-reply-to: Your message of "Thu, 05 Nov 1998 01:21:00 PST." X-Copyright: Copyright 1998, Craig Metz, All Rights Reserved. X-Reposting: With explicit permission only Date: Thu, 05 Nov 1998 03:26:37 -0500 From: Craig Metz Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , you wr ite: >IPsec is still an evolving standard, so I don't think there is a single >implementation that's "finished", per se. The next release of NRL's IPv6+IPsec (due in order days) also supports FreeBSD 3.0. All the implementations I know of have their strengths and their weaknesses. -Craig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message